CS would be better, just had to use a package due to being interleaved with
other work...
Note that with MC there is no mechanism for removing a method! Perhaps I
should have just done the changed methods along with an initialize that
would clean up other dependencies, after which an unload of EToys could be
done.
Regards, Gary.
----- Original Message -----
From: "Marcus Denker" <[EMAIL PROTECTED]>
To: "An open mailing list to discuss any topics related to an
open-sourceSmalltalk" <[email protected]>
Sent: Sunday, September 21, 2008 6:48 PM
Subject: Re: [Pharo-project] removing the DockingBar and
TheWorldMainDockingBar
On 21.09.2008, at 18:26, Stéphane Ducasse wrote:
Marcus and others
Do you think that the cs approach is good because after applying them we
will have to publish
new packages?
So could you harvest these ones for example and let me know what do you
think and if cs is better?
because I could produce also packages.
Packages are good, too. Just a removal package that re-classifies the
methods is not good.
Marcus
Stef
On Sep 20, 2008, at 10:29 PM, Stéphane Ducasse wrote:
Another one :)
Cleaning the inspector.
<EtoyRemoval-002-CleanInspector.2.cs>
Stef_______________________________________________
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
--
Marcus Denker -- [EMAIL PROTECTED]
http://www.iam.unibe.ch/~denker
_______________________________________________
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
