Hi Torsten, Thanks for the feedback.
On Thu, Oct 16, 2014 at 11:22 AM, Torsten Bergmann <[email protected]> wrote: > While I like that GTTools are in Pharo 4 now (thanks!!!) and allow all > kind of neat > things I basically ask myself if we forgot to remember usability on a few > places: > > 1. the world menu item "Workspace" opens a window "Playground" including > also > a tab with the same name "Playground". > => CONFUSING > > I would suggest that we rename the window "Workspace" and keep > "Playground" > for the initial tab. This is easy to fix and would also fulfill the > expectation > when a beginner grabbed an existing Smalltalk or Pharo book. > Indeed. This was a discussion I wanted to spawn as well. I would prefer to change the name from Workspace to Playground in the World Menu. The reason is that the Playground is such a distinct departure from the Workspace that it deserves a different name. > 2. While in all UI interfaces (Windows, Linux, Mac) the order in the > context menu > is "Cut", "Copy", "Paste" the playground menu uses a different order > "Copy", "Cut" "Paste". > => CONFUSING again > > I would suggest to use the well known order "Cut","Copy","Paste". > Thanks for noticing. This will be fixed. > 3. When one uses "Inspect it" from the context menu it means > - to run the code > - and the resulting object is then "inspectable" in a new window > > On the other side "Do it and go" from the context menu means > - to run the code > - and the resulting object is then "inspectable" in a new pane > (but same window) > > > The intention of both menu items and also the result is the same, but > the naming > is different ("go" vs. "inspect"). But the only notable difference is > that in one case the > inspectable object is opening right to the existing pane in the other > case a new > window is opened. > > => CONFUSING and inconsistent > This is harder to solve. Possible solutions are: > > 3a. We keep the "inspect" concept and name the menu items "Do > and Inspect it" and "Inspect in new window" > > 3b. We keep "Do it" as before to run the code, also "Inspect > it" which opens the new pane to the > left in the same window. If someone wants to open a new > inspector window he should keep SHIFT key pressed > while running "Inspect it". This is a concept known from > web browsers and other tools today, clicking on > a link while pressing SHIFT opens a new window. > Indeed, we had a debate about the name. I proposed the solution 3b you mention, but it was decided that it would be too confusing to change the Cmd+i action at this time, and we chose "Go" to be the name of the action that is mapped on Cmd+g. I proposed "gInspect it", but that is perhaps less fortunate :). You say that the intention is the same, but is is not. Having it opened to the right has the intention of keeping track of the path of inspection (we call it the inspection session). That is different from spawning an unrelated window. What other proposal would you have? > 4. The icons in the context menu of Playground are not the same as the > ones in the Pharo browsers. > > => CONFUSING and inconsistent > > They are just black and if one switches to the Pharo dark theme they > stay black and therefore > looking ugly and make nearly no sense on the dark grey menu background. > > For now we should use the known icons that we already have. Maybe > currently they are hardcoded and may > conflict with Moose vs. Pharo icons - but this could be solved with > the Icon Theming. > This is a known issue and we will look at it soon. > (In the long term I would like to see scalable icons in Pharo menues > (instead of bitmaps) similar to > "Fontawesome" in web browsers (two colors) or SVG based ones (more > colors) as currently the icon does > not scale when changing the menue font size). > Me too! > Sorry if it sound like a rant - but the intention of this mail is that we > discuss > (and hopefully fix) in order to improve. > It's not a rant at all. > Maybe it is written too early after the initial integration, but I think > the mentioned > points should be easy to address. Unfortunately I'm additionally confused > with the changed > contribution process that has exceptions for specific packages like GT to > fix it > myself with the usualy bugs/slice cycle. > At the moment, GT is an external project and the contributions should happen directly in its repository. Cheers, Doru > Thanks > T. > > > -- www.tudorgirba.com "Every thing has its own flow"
