I understand your frustration, but writing doc takes time. I have a more industry oriented example in polishing mode
Ben On 18 Jun 2014, at 11:40, Yuriy Tymchuk <yuriy.tymc...@me.com> wrote: > Hi guys, > > I was very frustrated, but as usually complaints are useless, I’ll try to be > constructive. Maybe the problem is not about Spec itself but all the UI > related tool-chain. > > I find UI very fragile part in software design. And by now I’ve seen only 2 > very nice documentations on how to develop UI (with MVC). One was for Ruby on > Rails, and another was for iOS applications. Documentation was > straightforward: 1) this is how your model, view and controller should look > like, 2) this is how they have to talk, 3) other useful cases. > > Now, there is description about how to do something with Spec, and it’s cool, > but for example I always get myself caught in initialisation stuff. Spec > intends that I provide some default solution if it’s not initialised with > proper data. And I even cannot initialise some variables, because > initialisation of superclass initialises widgets and they need default > behaviour. I can move to sort of lazy initialisation stuff, but maybe there > is some reason in making some calculator example tutorial that will show how > mvc apps should be developed in Pharo? > > Uko > >
