Yes, Marcus is right.
But are there some behaviors that we want to keep and integrate in
Core ?
For example, the Rotate functionality in the halo.
Cheers,
Jannik
On Oct 26, 2009, at 16:22 , Marcus Denker wrote:
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...
I don't think so.
Etoy is more complex than you think. It would be (nearly) impossible.
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.
Marcus
_______________________________________________
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
