2008/11/9 Stéphane Ducasse <stephane.ducasse@inria.fr>:
I can tell you that removing etoy is really really boring/difficult/ even if you think that this is **just** removing some methods. I really hope that I will not break too much but really this is a so huge mess.
I'm appreciate your efforts. Keep going! Just one question. You seem planning to remove Project from system, as part of Etoys. I'm not really sure about it. A removal of Projects will lead to model, which having only a single World (a PasteUpMorph instance), what i fear of, because i want to make a plugin which supports multiple windows, and therefore each window can have own PasteUpMorph instance. And it seems like its least painful way to get multiple windows support. Of course, it would require rethinking the role of Display & World globals, because there will be more than a single window and this will require to do something with code, which assuming that there is always a Display/World where everyone can put his dirty hands on :) For instance, i have no idea, what to do with commonly used (and quite convenient, in fact) message , like #openInWorld. When you have multiple worlds, its a big question, where new morph should appear. Maybe, as solution, a World/Display globals can stay, but they will track the currently active window. In this way, all new morphs will appear in currently active window. The problem is, that its not really necessary for window to be associated with PasteUpMorph - it can be a window which only having a Form for drawing and nothing more, or window which may use different UI framework and therefore creating/keeping an instance of PasteUpMorph for it is not an option. -- Best regards, Igor Stasenko AKA sig.