Smalltalk › Pharo › Pharo Smalltalk Developers

are we going to remove MethodFinder and MessagesNames for Pharo 1.2?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

8 messages Options

Mariano Martinez Peck

are we going to remove MethodFinder and MessagesNames for Pharo 1.2?

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

Guillermo Polito

Re: are we going to remove MethodFinder and MessagesNames for Pharo 1.2?

Maybe that can be a preference...

On Tue, Dec 28, 2010 at 8:51 AM, Mariano Martinez Peck <[hidden email]> 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

Stéphane Ducasse

Re: are we going to remove MethodFinder and MessagesNames for Pharo 1.2?

No preference plague.
Now we will keep the tool in 1.2 and remove them in 1.3.
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 <[hidden email]> 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
>

Mariano Martinez Peck

Re: are we going to remove MethodFinder and MessagesNames for Pharo 1.2?

On Wed, Dec 29, 2010 at 10:18 AM, Stéphane Ducasse <[hidden email]> 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 <[hidden email]> 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
>

Stéphane Ducasse

Re: are we going to remove MethodFinder and MessagesNames for Pharo 1.2?

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 <[hidden email]> 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 <[hidden email]> 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
> >
>
>
>

laurent laffont

Re: are we going to remove MethodFinder and MessagesNames for Pharo 1.2?

In reply to this post by Mariano Martinez Peck

On Wed, Dec 29, 2010 at 10:41 AM, Mariano Martinez Peck <[hidden email]> wrote:

On Wed, Dec 29, 2010 at 10:18 AM, Stéphane Ducasse <[hidden email]> 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.

+1 to hide them.

Laurent.

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 <[hidden email]> 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
>

Mariano Martinez Peck

Re: are we going to remove MethodFinder and MessagesNames for Pharo 1.2?

Ok...thanks. We are in sync :)
So, I opened http://code.google.com/p/pharo/issues/detail?id=3492
and I will upload a fix,

cheers

mariano

On Wed, Dec 29, 2010 at 10:56 AM, laurent laffont <[hidden email]> wrote:

On Wed, Dec 29, 2010 at 10:41 AM, Mariano Martinez Peck <[hidden email]> wrote:

On Wed, Dec 29, 2010 at 10:18 AM, Stéphane Ducasse <[hidden email]> 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.

+1 to hide them.

Laurent.

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 <[hidden email]> 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
>

csrabak

Re: are we going to remove MethodFinder and MessagesNames for Pharo 1.2?

In reply to this post by Mariano Martinez Peck

Em 29/12/2010 07:41, Mariano Martinez Peck < [hidden email] > escreveu:

> > On Wed, Dec 29, 2010 at 10:18 AM, Stéphane Ducasse
> > <[hidden email]> 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.

I agree the menu is starting to be long, but see below.

> 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.

Removing from the menu is a kind of 'selection' of a winner, so if we
can agree which has to stay in the menu, let's agree also:

1) Code which is only accessible by 'connoisseurs' is better put in
packages and those users could easily install them back if it is their
wish;

2) People that prefer other tools and know how to put back in the menu
should know how to install a package as well.

Now, about the information about the differences or recommendations on
what to use, I suggest be put in the Welcome workspace in a specific
section/paragraph.

>
> > And we should bug fixes the new tool on the way.

Yes this is essential.

my 0.019999....

--
Cesar Rabak