Hi I got a flu last week. :) Now how to proceed: step by step :) Start little do it often. So what I suggest is that you go one fix at a time, you send it to the list, open a ticket, people get a chance to argue and we loop million of times. For example - I would like to understand if they are not things to be changed now that we have true bloclosure - for menu opening... like PluggableXXXX and fix that - I would like to have less subclass of StringHolder :) - Something good would be to check the fix Juan did in CUIS for the scrollbars and friends. Yes cleaning morphic is important.
I know morphic is one of the greatest issues Squeak and Pharo have. And I'm tired of the kilometric morph hierarchies with tons of methods that noone uses, and the impossible traceability of the morphic code...
And I'm sure that a lot of people tried it before... And this isn't the highest priority. But I think morphic cleansing should be done.
So, while i'm now in bed beacause of a flu, hehe, I want at least remove unused morph classes and unused methods... Or maybe we can separate some things from the core. Of course I will be "spamming" in the list asking for the changes I will do :P.
what do you think? Do I open a ticket?
Guille _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project