On Apr 4, 2011, at 1:44 09PM, Benjamin wrote: > > On Apr 1, 2011, at 8:29 PM, [email protected] wrote: > >> Em 31/03/2011 18:10, Benjamin <[email protected]> >> escreveu: >> >>> On Mar 31, 2011, at 8:08 PM, [email protected] wrote: >>> >>>> Benjamin, >>>> Testing the understanding of the diagram of yours: >>>> Model, Pluggable TextMorph, Pluggable CodeMorph, Browser, Browser >>>> Model, Debugger and Debugger Model all inherit from Object? >>>> the representation of "based on" means that it changes states in >>>> the model counterpart, and "use" means that has some similarity >>>> but not enough to inherit from the other classes? >>> >>> based on means, that the view (on right) is based on the model (on >>> left) >> >> This still tautological: does "based on" means the structure is one-to-one >> correspondent? >> >> Or are we re-introducing the MVC paradigm and the "based on" means that the >> View has to know the inners of the Model in order to be built? > > Yes it's MVC, the problem is there is no proper controllers ... > > > Ben
"Problem" is a bit harsh of a word. Controllers are great for when you want modal behaviour for an object (like, a canvas in a drawing program responding to mouseclicks differently based on current brush). For typical widgets where behaviour is non--modal, they are mostly, if not entirely, an unnecessary level of indirection. My 2c at least :) Cheers, Henry
