Thanks. As indicated in my previous emails the removal currently consists of an MC package that provides "blank" methods for those to be removed and modified versions for disintegration (!)...
Will have to check against existing Pharo removals for the latter. At present the methods are marked 'gvc' as the author... guess that needs to change given the policy for Pharo. Regards, Gary. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Alain > Plantec > Sent: 27 June 2008 4:50 PM > To: [email protected] > Subject: Re: [Pharo-project] EToys removal > > > On Friday 27 June 2008 16:46:52 Gary Chambers wrote: > > Just to say that my investigation is almost complete. Having > completed most > > of our work on the various Pinesoft Sprints I should have a bit > more time > > for it... > > > > Obviously there is some overlap with MVC/Nebraska/ScriptLoader > removal (and > > a bit of UI Enhancements modifications) though. > > > > Just a concern, forgiving a quote from Alain's email, "Stephane seems to > > prefer that I work on Etoy removing". > > > > I'm wondering the best way forward with this now. > maybe you can just send here what you've done. > I will make a try and help in order to make a slice package if needed. > alain > > > > Regards, Gary. > > > > > > _______________________________________________ > > Pharo-project mailing list > > [email protected] > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
