Hi lukas, sorry for your frustration, that I can easily understand I do not remember. There are some changes that when deprecated get in our way. I still think that we need a refactoring deprecate methods because just doing all of them by hand is not possible. I believe that we need to have the RBEngine all the time available and that the notion of core should vanish but I made no progress on the idea of using metacello to manage pharo-dev in a way that we could refactor all the packages at the same time.
Stef > I wonder why the old editor functionality was removed instead of being > deprecated until the next release like this is normally done? > > It is extremely difficult to get any GUI related stuff ported, because > the packages cannot simply be loaded. One has to fix part of the > package in the old image, and part of the package in the new image. > One wrong method, and everything blows up irreversibly. > > I spent the whole afternoon trying to get OB, Shout and eCompletion > working. OB and Shout kind of work (thanks to the preparations in the > PharoTaskForces), but they are still subtly broken. eCompletion is > very hard to get working. The idea of making completion part of the > ToolSet doesn't help at all, the patch now just moved from Morphic to > the StandardToolSet class. > > I am frustrated and give up, I revert back to Pharo 1.1. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >
