Right, either you use a Scanner and duplicate part of Parser's job... Or you use a Parser. For findSelector, I vote for first solution because I want to have a possibility to browse imperfect selection (like not spanning on exact sub-expression boundaries). Said differently, I want a special FaultTolerantParser. Shout has some functionalities of such FaultTolerantParser. For example it does already a good job hiliting unimplemented multi-keyword selectors... I didn't dig if it was enough for cmd+click though... Nicolas 2012/5/16 Camillo Bruni <camillobruni@gmail.com>:
you're partly right igor :)
that's why I added the cmd-click and cmd-shift-click to the code panels for browsing implementors / senders of without choosing a menu.
the one problem that remains is that shout only gives you back the tokens with limited semantic annotations. hence you don't know if something belongs to a multi-keyword selector or not.
=> that will change once we have full AST nodes around
On 2012-05-16, at 02:46, Igor Stasenko wrote:
i don't understand one thing: we have shout, and it parses the source code to highlight it correctly, which means that it knows where each keyword selector starts, where it ends.. still we cannot navigate the code just by clicking on selector part or to variable name. the most annoying is when you have nested sends.. and sender/implementors often fail to work..
On 16 May 2012 01:55, Chris Muller <asqueaker@gmail.com> wrote:
In Nautilus, unlike old Browser it now works for multiple keywords, so things are improving.
Mm, I think it was Dan Ingalls who made browsing senders/implementors of multi-argument keyword messages in the code pane working since the 1990's.
It works with even gross effort -- in the attached picture I made a sloppy selection of #objectWithOid:ifFound:ifAbsent and press Command+M to get implementors in spite of all of the intermediate code it knows what I wanted.
The main drawback from usability point of view: it is an implicit feature, invisible to newbie and other out of the context.
I was using Squeak for more than 5 years when someone told me about it -- Once discovered, it's great, productivity has been a bit higher ever since. Â People should know about it if they don't already..
Though in term of number of actions necessary to reach information, I'm not sure it's a clear win. There's a balance between simplicity and efficiency. Isn't it also a step backward in promotion of keyboard navigation over mouse navigation?
Nicolas
Open an entry to be sure it's not lost in the mailing list, and as soon as I can, I will see to add a setting for this :) (right now I am more in a "bugs fix" phase that "add new features" one ^^)
Ben
On May 12, 2012, at 11:47 AM, Hilaire Fernandes wrote:
Tried from Nautilus:
Why when asking 'implementors of ' in the method menu, I only got the implementor of this method.
Am I doing something wrong?
Look like the browser need a lot of love.
Hilaire
-- Dr. Geo -- http://www.drgeo.eu
-- Best regards, Igor Stasenko.