HAhah, thanks :). Anyway, my idea is not to remove those packages. I want to put them in separate monticello packages, so we don't need have it in the core if we don't use it.
So, I download Seaside, Moose, and what else? 2010/7/19 Mariano Martinez Peck <marianop...@gmail.com> > Guille: one thing you can do before removing the code, is to prepare an DEV > image with Seaside, Moose and all those big projects. So that when you > search senders/references you can do it also there. I don't mean that we > shouldn't remove them if they are used in those projects, but just to be > aware. > > but for "coding" and commiting, yes, use latest PharoCore, not dev. > > And yes, if you don't receive feedback, go ahead! > > Cheers > > Mariano > > 2010/7/19 Guillermo Polito <guillermopol...@gmail.com> > >> Ok, I opened an Issue for this... >> >> http://code.google.com/p/pharo/issues/detail?id=2696 >> >> >> On Thu, Jul 15, 2010 at 8:18 PM, Guillermo Polito < >> guillermopol...@gmail.com> wrote: >> >>> Hi! >>> >>> Does anyone know what the Ballon category and its related morphs are >>> for? Someone uses it? Is it useful in the Core of pharo? >>> >>> Did Someone try previously to remove it and failed? why? >>> >>> thanks in advance :) >>> Guille >>> >> >> >> _______________________________________________ >> 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 >
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
