"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."
AFAIK the idea behind MVC is a GUI system that is divided into 3 elements each element represented by a class. Model, View , Controller. Model is where the data is resides and as a class it has methods to process the data. View is the graphical element itself that is displayed on the screen . Controller is responsible for the interaction of the View with mainly handling keyboard and mouse events. >From my observations I see that the pitfall of Morphic is that it mixes View with the Controller, since Morph handles also its own events. I fail to see however how Morphic forces you to also mix in your Model to the View. I fail to see how a Morph would force me to put my data inside it . I am really interested in understanding this as it will help me not only like Spec but also prepare myself for any problem I experience with Morphic because even if continue to use Spec I will stiil have to rely on Morphic since custom GUIs is really important for me. "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." But I think I have been crystal clear about this my main issues were 2 1) Spec was forcing to define an array and then also initialise using classes for each spec element. This is where I was wrong. I am very happy I was wrong. 2) I have to return each spec element which makes sense to me but what annoys me is that I have to do it verbosely by returning each variable separately in its own method. Instead inside a single method and pass it as an array which would reduce the amount of methods used dramatically. 3) I did not like the name "defaultSpec" again I was wrong, since as I was notified I can use whatever name I want as long as I use the pragma Braking down to smaller methods is something Pharo is doing everwhere. Its pretty rare to find methods 20 lines long like you were proposing if I united all these methods. Yes some example of Spec do that . The example with really long method is the dynamic spec example which in that case it makes sense for the method to be long as it acts this way to illustrate the dynamic nature of spec. On Sat, Dec 20, 2014 at 3:18 AM, Johan Fabry <jfa...@dcc.uchile.cl> wrote: > > > 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 > > >
