[Pharo-dev] Does "browse" make sense?

Luc Fabresse luc.fabresse at gmail.com
Thu Nov 7 15:51:15 EST 2013


Hi Mariano,

 I would prefer to keep browse for everything.
 If it is a selector, it opens a browser on the only one implementation or
the implementors windows.
 If it is a class name, it browses it.
 etc.
 my idea would be to have one keybinding and context disambiguation.

Cheers,

Luc


#Luc


2013/11/8 Mariano Martinez Peck <marianopeck at gmail.com>

> Hi guys,
>
> Currently (it was not like that before), if we search implementors and
> there is only one implementation, it will open a normal browser with that
> method. If there are more, it will open the classic implementors windows.
> "Browse" (for example in the FinderUI), does exactly the same as
> implementors: if 1 result, browse, if more than 1 result, implementors
> windows.
> So....do we need to keep having "browse" if it has the same behavior as
> "implementors"?
> I am missing something?
>
> Thanks,
>
> --
> Mariano
> http://marianopeck.wordpress.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131108/5a01f4f1/attachment-0002.html>


More information about the Pharo-dev mailing list