Paolo Bonzini wrote: > > The browser is another story. The model-dispatcher system is incredibly > complicated and I never really unravelled it. Even the Namespace > browser was mostly done by cut'n'paste'n'hope-it-works, I'm not very > pleased to say...
I think the model-dispatcher system is quite elegant, but I couldn't apply it easily to widgets like the GtkTextBuffer/View, where a lot of the state is held outside of the image (unless you want to do a lot of duplication). > It will have less flexibility for the toolkit user though. It can be > really useful to have wrappers that convert a Smalltalk model to a GTK+ > model, or something like that. In fact you *have* to have some kind of proxy system if you want to be able to restart the image. That doesn't *have* to be a set of wrappers (for example, it could be a text representation of the interface like glade or XUL), but having wrappers is the most obvious way. Mike _______________________________________________ help-smalltalk mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-smalltalk
