I wrote:
With the ability to drag-n-drop objects, cleaning up the mess you make is hardly a chore later on.
I meant "drag-n-drop slots" which allows you to effortlessly change object structure and inheritance tree.
About mirrors, they only handle a small part of the reflection problem, like the classes they replace. They only tell you about object structure, but you also need to be able to "hook into" the message passing mechanism, virtual memory, and so on.
BTW, a lot of people don't understand why an object can't handle its own reflection. The problem is that a circle object should "think" it is a circle, and not a bunch of bytes in memory or on disk. That is, its message interface (or protocol) should only include application level things. Adding a system level interface to every single object mixes up things that should be kept separate. So while speciall reflection objects aren't really needed, they are a very good style.
-- Jecel P.S. I am sending this from the local university, so it seems that my ISP is the problem with sending to this list.
squeak-dev@lists.squeakfoundation.org