On 03.12.2008, at 15:33, Torsten Bergmann wrote:
It's not a question of compatibility, the question is where will
Polymorph be continued - in SqS/Pharo or SqS/UIEnhancements or both?
I didnt notice (until now) that the integrated plymorph packages are
now also
in the SqS/Pharo repository.
A new branch or just a move? Same question applies for other packages
integrated later.
The problem is that removing etoys is not a clean thing. We have first
methods
that are needed to be changed for both removing etoys *and* polymorph.
So that's
why the packages need to be in the pharo repository.
In general, if you think about code quality or modularity in the
context of Squeak:
Think about the worst you can think of, then multiply it by a factor
of 100. Then
you get to what the current state is in Squeak. It's a mess of epic
proportions...
Bye
Torsten
BTW: Will I have to open an issue when I just put something into the
inbox
(like a new ScriptLoader from today that fixes Seaside
loading)?
Yes. The bug-tracker is like a TODO list.
Marcus
--
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
