http://code.google.com/p/pharo/issues/list?updated=890 ready for inclusion Use SLICES described in my last comment Sorry I left some garbage in the PharoInbox, but it's quite unhandy to manage incremental dependency (when order of changes DOES matter). Wouldn't atomic loading be an easy solution for such problems? I usually don't complain, but here are my feelings: <rant> Monticello is quite a drag, and pharo feels globally unresponsive (even the core image). I still experiment some lost keystroke and menus are sometimes gooey. It's not rare I click on the wrong item. If 3GHz Intel core2 duo 64 bits really becomes a requirement, I will give Cuis a ride to get some fresh air ;) To me UI feel is mitigating all the good job made so far. </rant> Nicolas