On Aug 9, 2011, at 6:29 PM, Nicolas Cellier wrote: > 2011/8/9 Stéphane Ducasse <[email protected]>: >> Hi >> >> I would like that we do an analysis of what should stay in implementors >> >> Here are the menus in 1.2 and 1.4 >> > > Note that the menu titles are misleading. > In previous implementation, 'Implementors of...(m)' did mean > implementor of this message or any message called by this method.
I did not pay attention to that because I always type the code but I see now. > In current implementation, 'Implementors of...(m)' does mean > implementor of this message and only this message. > Same for 'senders of ...(n)'. > > That's the main grief I got because this break the browsing chain. > If I want to see implementors/senders of a sub message, then I have to: > - select the message in text field, then click cmd+m or cmd+n this is what I do :) > - if the message is multiple keyword, then this won't work... We should fix that for any place in the system foo: #yyy to: does not find foo:to: :( > I have to open a finder, copy some text, paste in the finder then > click one of the matching methods... > That's many more clicks than previous implementation. Ok we will fix that. > > To define a "good" UI you must not only think in term of available > feature, other views matter: > - homogeneity of presentation / action > - number of clicks for accessing a feature > - auto-discovery of features rather than implicit knowledge Yes. >> Please comment so that we can add what is really used. >> As a general comment I would avoid to do everything with a single tool. >> > > Err. I think the contrary. > Every such view is a browser with a specific filter on displayed code. > The first function of a browser is browsing. > Removing browsing capabilities from these views make em become dead > ends (look and close). > To restore the navigation chain, user must pass thru textual copy/paste. > Ubiquitous browsing is a strength of Smalltalk IDE, no? Yes but do we need spawn subprotocol? and friends. All instances... So let us focus on the most 40% most important features and add them to the browsers. So there should be a reasonable amount of used functionality. So let us know what you use most of the time or less and this will be good. Stef
