On 2012-09-19, at 19:48, Stephan Eggermont <[email protected]> wrote: > Camillo wrote: >> I did a quick nautilus improvement: >> >> https://code.google.com/p/pharo/issues/detail?id=6667 >> >> CAVEAT: One thing I did was not showing all methods when opening the browser >> on a class. >> >> For me this makes perfectly sense since I use the CMD-F + CMD-M shortcut >> for searching for a method. Or go over all the protocol using the >> arrow-keys on the selected protocol list. >> >> what do you think? > > It sounds like a perfect idea to get some traction for getting rid of method > categories. > > Why would anyone want not to look at all methods in a class by default? > In well refactored code, the number of methods is so limited that no > scrolling > should be needed. Not all code is like that, of course. > > Reading code is the most important activity of developing, and it is > essential to > limit the interaction needed to browse through code. > > Much better would be to show in the code pane which instance variables have > accessors > (r/w) and show all without accessors by default. > >> >> However I can see that a "classical" user might be disturbed. This cut's down >> the opening lag of a new browser from ~400ms to ~200ms on my machine, to me >> thats quite worth it :). > > If the problem is performance, focus on performance. Why can not showing 30 > items > in a list make a difference of 200 ms?
well yeah, that would be nice, but takes too much time for now: - PluggableListMorph does many stupid things to kill performance - TrueType has 3 levels of caches which make every operation on it super slow I know where the problems are on the lower levels, however they are not to be solved that quickly... so not showing 30 items for me is valid right now. adding an option so I can disable them on my machine is also valid. but then again, most people out there use the mouse... so that is one piece of time loss :D, and this time in the range of seconds, not milliseconds.
