On Mar 31, 2011, at 8:08 PM, csrabak@bol.com.br 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) use means that the View use/is composed with the other view. By example, Browser is based on BrowserModel, and Browser (as a Morph by example) contains a PluggableCodeMorph Is it better like that ? (I'm sorry, but I'm not sure to be able to do a good UML ^^) Ben
Could you elaborate this with a more complete UML diagram?
Thanks for giving thoughts on this subject.
Regards,
-- Cesar Rabak
Em 31/03/2011 10:29, Benjamin < benjamin.vanryseghem.pharo@gmail.com > escreveu:
On Mar 31, 2011, at 2:14 PM, Fernando Olivero wrote:
In CUIS the intent is to provide specialization on the model, And then each model holds the responsibility of creating the appropriate view (SystemWindow), by creating a composition of widgets. This is a subset of the model hierarchy,
Model TextModel Workspace PluggableTextModel TextProvider CodeProvider Browser HierarchyBrowser Debugger Inspector
For me, this hierarchy is bad. Workspace is not a model, it's a view basically. So why it inherits from Model ? The same for Browser, HierarchyBrowser, Debugger, Inspector and so on...
Maybe it's better to have something like