2009/10/26 Marcus Denker
<denker@acm.org>
However, it would be a good idea to put all the interesting eToy stuff in an external package so that those who want to load that stuff, are able to do it.
�
Because, make an external package of it needs a big work...
Etoy is more complex than you think. It would be (nearly) impossible.
Grrr� Sorry,� so, I may be a dreamer :(�� Of course I know very little about Morphic, so I totally believe you.
�
You just need to create the package. And then, instead of removing code, you move it to that package. What can be a lot of work is to keep that package up to date and working, but that's not Pharo responsibility.
�
Nope. Etoy is programed in a way that makes things like this *a lot* of work.
I was just asking as one of the Pharo goals is to be "clean". Is even that complicated to do it in little steps? For example, consider this particular case Jannik� said as a step.
Again, I know nothing about Morphic :(
�
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project