Yes we should remove them from the menus! Stef On Dec 29, 2010, at 10:41 AM, Mariano Martinez Peck wrote:
On Wed, Dec 29, 2010 at 10:18 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote: No preference plague. Now we will keep the tool in 1.2 and remove them in 1.3.
Ok, it is cool...but, as I said...image it is your first time you open pharo...you will have THREE tools which looks similar. You don't know its differences, nor which to use. And the menu is starting to be long.
Can we at least remove them from the menu as I suggested (not the code) ? Poeple that prefer MessagesSend / MethodFInder know how to put them back on the menu or open them by hand.
And we should bug fixes the new tool on the way.
Stef
On Dec 28, 2010, at 1:53 PM, Guillermo Polito wrote:
Maybe that can be a preference...
On Tue, Dec 28, 2010 at 8:51 AM, Mariano Martinez Peck <marianopeck@gmail.com> wrote: yes, yes, depreacting. But....it is confusing having THREE things for the same stuff.
So, since we now have "Finder" and we want to push that, what about removing MethodFinder and MessagesNames for Pharo 1.2?
At least, what about removing them from the menu so that not to confuse new comers. And then, those hacky guys that prefer MethodFinder or MessagesNames can add it to the menu or open it by hand. And then, in 1.3 we really remove not only form menu but the code itself.
Cheers
mariano