Ben
On Apr 24, 2013, at 12:47 PM, Camillo Bruni <camillobr...@gmail.com> wrote: > > On 2013-04-24, at 10:10, stephane ducasse <stephane.duca...@free.fr> wrote: >> What would be good is that when we get the sender/implementor is to get >> - the name of the entity as first entry in the menu >> - get the entity selected in the text. >> >> blockClosureValue: aBlockClosure message: aMessage >> |newMessage| >> newMessage := Message selector: #valueWithArguments: arguments: (Array >> with: aMessage arguments). >> ^self blockClosureValueWithArguments: aBlockClosure message: newMessage >> >> >> when I'm on selector: it works I get selector:arguments: > > yes please ;), like a real context menu! > >> What would be cool is to have a way to select the enclosing expression but >> you know it:) > > just create enough sub-menus (we could even put the old menu as a submenu for > now :P so nobody can complain about removed "functionality"...) > > In the end, for most pro users, and by that I rely on my experience with very > complex 3D software, menus are mostly there to learn the shortcuts. That > means they do not have to be super navigable (e.g. one big list) but > logically structured (e.g. submenus). > >> When can we push that into 3.0 > > => push it as early as possible > => improve it gradually +10 :) Ben
