Colin Putney wrote:
> The purpose of SystemEditor is to provide a way to atomically apply 
> changes to the system, using an interface identical to the reflective 
> interface already in use. The proxies provide protocol compatibility, 
> while recording the changes, that need to be made. 

But why do you need proxying and protocol compatibility? The only reason 
I've ever found was to make sure existing tools (browser etc) can work 
with those proxies. Is this what you're after, e.g., have a browser with 
a "commit" button which then does all the changes atomically? If not, 
I'm not sure what you need the proxying / protocol compatibility for.

> I hear you though. If you think ClassEditor is evil, look at 
> MetaclassEditor. ;-)

Heh. I knew what I was in for when ClassEditor class>>new said something 
along the lines of "MetaclassEditor new new" ;-)

Cheers,
   - Andreas