Stef, I was thinking to put not only ProtocolCatcher but also all your stuff from ObjectAsMethodWrapper� in the same ObjectMetaTools.

That way we have a repository with cool stuff

what do you think ?

cheers

Mariano

On Sat, Mar 20, 2010 at 5:12 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:


On Sat, Mar 20, 2010 at 4:44 PM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
Thanks I will do that!
can you open a ticket because the list is starting to get long of the stuff to integrate after martin's changes.

http://code.google.com/p/pharo/issues/detail?id=2180
BTW did you check if the other class besides ProtocolCatcher are working?


No. No time yet.

Stef

On Mar 20, 2010, at 4:22 PM, Mariano Martinez Peck wrote:

> This package should be removed from core but it should still be loadable. Thus, when needed, they can be easily installed. On the other hand, it could �be in PharoDev image.
>
> - MetaObjectTools: �This package is moved to PharoDev. It doesnt have any users in PharoCore
>
> To fix, evaluate:
>
> (MCPackage named: 'ObjectMetaTools') unload.
>
> I created and put such code in http://www.squeaksource.com/ObjectMetaTools
>
> To load it again in a Pharo image:
>
> Gofer new
> � � squeaksource: 'ObjectMetaTools';
> � � package: 'ObjectMetaTools';
> � � load.
>
> During the week I will analyze the CUIS' ProtocolCatcher and see if it make sense to put it there too.
>
> Cheers
>
> Mariano
> _______________________________________________
> 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