> > However, reflecting all of this in the name, ComposableModel, makes it > unclear what it is for. >
>From "Seamless Composition and Reuse of Customizable User Interfaces with Spec" ( http://rmod.lille.inria.fr/archives/papers/Ryse13a-SCICO-Spec.pdf ) UI Element: an interactive graphical element displayed as part of the Graphical User Interface. UI Model: an object that contains the state and behavior of one or several UI elements. Widget: the union of a UI Element and its UI model. My understanding was that Element is Morphic, Model is Spec and Widget is an adapter? -- But in the end once you start using it you know what to look for (= 10 minutes after reading tutorial) does it really make that much difference? It is just a subclass. >From my point having clean and well organized protocols is more important, because you will end up interacting with those order of magnitude more, and if there is method in unexpected protocol... well then I might as well use --show all protocols--. Also whenXYChanged methods are not so nice (those have been mentioned previously).
