> On Dec 19, 2014, at 21:54, kilon alios <kilon.al...@gmail.com> wrote: > > "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." > > "To define a user interface, it is sufficient to define the model of the user > interface. […] since all UIs are constructed through composition of other > UI's, and it is sufficient to define the model to define the UI, the root > class of all UIs is named ComposableModel.So, to define a new user interface, > a subclass of ComposableModel needs to be created.”" > > I dont understand this for me a GUI is a UI with graphics I dont see it as > two separate entities. I dont see what the model is in my case and why I > should inform Spec about it. I just wanted to create some buttons I dont see > how those method returning the names of the buttons as instance variables > helps me in any way. Whats the benefit ?
This is an explanation of how the whole is composed of the different parts and how different responsibilities of the UI are split up amongst different classes. In Morphic these are joined and that’s a reason why many persons are unhappy with it. > "Just wondering, did you see an example with the double instantiation of > models or with the needles splitting up in methods? If so tell us where it is > so we can fix it." > > Double initiation may have been just me not understanding documentation or > probably I saw an example that confused me. Splitting up methods is probably > the first thing I learned using Squeak and Pharo. Also The system browser > turns red if you make long methods . I focused on you splitting up into methods because that was a complaint of yours and you said you were following Spec examples when doing that. ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile
