> > 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. >
Yes, that's why it is configurable. > > Some people will want 9, other 14 or 16. The average is likely in between. > It was 9 since at least Pharo 3, so I am not sure what's the complaint about, considering people were ok with the size for several years (so I am inferring 9/10 should be good for everyone). > > > > > >> 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. > Considering the L+ and W are literally the smallest elements in the UI I'd hardly call it noise; but this is subjective. > > >> 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) > > I guess professional software company have people to review it all. > A company that cares about first-time users. Once you know what it does, the current tooltip is often completely obvious. And since we don't really have much first-time users that would be willing to share (as often they are overwhelmed by so much different stuff) it can be quite difficult to improve. So if you can propose better tooltips (since you are a pair of fresh eyes), then it would be valuable for new users. > > > >> 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. > Because horizontal navigation in such a way is the same everywhere. But with control you are taking different action. But point above about new/accustomed users holds here as well. > > > > >> 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. > Interesting, I press the control with my thumb. As a proper touch-type user I should actually use the opposite shift than the key is on (so right shfit for G, left shift for H, etc.)… I don't know why I type it with one hand. The default meta key on linux is ctrl, so such hand-braking shortcuts are not so uncommon (ctrl+shift+Debug, ctrl+shift+Format). Peter
