On 20 sept. 2010, at 20:33, Stéphane Ducasse wrote:
Benjamin
I would rename patterns into example-based Then when on selector I would propose classes if the guy type something that looks like a class or a part of a class name similarly on class I would propose selector if the guy started to type something like a selectors The idea is to help the user as much as possible. We did the same with the sender and implementor, you can browse a class if you type Point and press cmd-M instead of cmd-B
Yep, did you have a look the Mercury search bar in OB? It has a nifty syntax to look for: - ClassName (starts with uppercase, look up class definition) - #ClassName (look up class references) - method (starts with lowercase, look up implementors) - #method (look up senders) - 'string' (look up for string in methods (not the same as look up in method source, which is much slower)) I would rename 'select classes' into something else, 'scoping classes', because it is really about the scope. Actually, I would love to extend the Mercury syntax to be able to scope things.
Else did you try to remove the progress bar? because this looks strange.
Stef
I've fix some bug and discover how to script packages loading ^^
Now, just run
Gofer new squeaksource: 'PharoTaskForces'; package: 'ConfigurationOfFinder'; load
ConfigurationOfFinder loadDefault
Ben _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Simon