Le 25/04/2016 13:58, Peter Uhnák a écrit : > Some comments > >> Font size is ridiculous! Make it at minimum 12 for the permanent > visual elements > > This is subjective… I am even considering making the size smaller for > myself (after all, in Pharo 4 it was size 9).
I think it is more a question of usability based on the average wished font size. So all in all the choice of font size can be done objectively although font size wish is subjective. Some people will want 9, other 14 or 16. The average is likely in between. > >> Line numbers: where is it used, not in the system browser > > This is disabled by default, so it shouldn't be a problem. UI noise, but not a big deal. > >> "Format as you read" -> what is tooltips good for? > > This is autoformatting without the need to reformat the code yourself, > very useful if you are reading some old/unformatted codebase. > > For example open Morph>>acceptDroppingMorph:event: and click on the > button — it will reformat the code without changing the code itself. => Tooltips needed. >> AST navigation: what is it? I don't understand its description. What > nodes? > > Do we really need a block of text of description for everything? If you > know what AST is then it is pretty self-explanatory. If you don't know > what AST is then the option has no value for you, because the navigation > would be random. > >> Nautilis: where is the local senders tools? > > You need to scope your view (top left corner button "Scoped") Oh great to know what does "Scoped". The tooltips of the "Scoped" button is therefore not helping as there is no useful information: "Browse scoped the selected packages" One can check at Dr. Geo what useful tips mean: Most of its tools come with 3 or even 4 lines tips (see screenshot example) When people add UI element, great care is need in the description. I guess professional software company have people to review it all. >> Spotter > Why Ctrl+[->]? my intuition tells me [->] as indicated by the blue icon > arrow, please fix it! > > Because -> and <- is already taken. Pretty much any shortcut in the > system has ctrl/alt/command in it, so I don't see why this only thing in > the entire system should be different. You can also hover over the > button to see the shortcut. Indeed <- and -> is used to edit the text search but keyboard focus can open the use of <- -> for navigation. Not being able to use -> is counter intuitive. > Not to mention that you have two different right arrows (ctrl+right, > ctrl+shift+right), so just because you immediately see one use case > doesn't mean that it's the only one/best one. There was A LOT of > discussion on the mailing list regarding Spotter's usability and shortcuts. It is inconsistent: why no need of Ctrl for up and down, but a need for it for left and right. > >> Playground > Why Ctrl+shift+g to open a pane, looks like Ctrl+g is working. > Nevertheless Ctrl+g is not very handy short cut, it hurts the fingers! > Can it be changed? > > Because it's not the same. do-it-all-and-go (ctrl+shift+g) executes all > the code and inspects it in the next pane, while ctrl+g (do-it-and-go) > just the selected block/current line. ok. But Ctrl+g is really really not fingers friendly for a short cut you will use very often. See screenshot, there is so much tension in the three fingers when doing it. It is torture and I can tell you my hands are large celtic ones. I guess you need two hands to use comfortably this shortcut. Hilaire -- Dr. Geo http://drgeo.eu
