Rob Spec deserves another pass. I see your point with showOn: now I do not see how you could avoid the presenter building. But may be I'm not enough into it. So I'm interested in your feedback.
Stef Stef On Tue, Sep 5, 2017 at 8:49 PM, Rob Rothwell <r.j.rothw...@gmail.com> wrote: > Hello, > > I was wondering what more experienced users than myself thought of the idea > of an explicit Spec "connection point" to a domain model object similar to > Dolphin's "showOn:" method, like: > > CounterApp showOn: counter. > > This would perhaps trigger something like Dolphin's Presenter>>model: > message (although I've always found the use of "model" confusing when there > are so many "models" involved.) after the widgets had been created: > > ComposableModel>>initializeBindings: anObject > > In many cases, if your domain model uses ValueHolders as well (like Spec > does), making a connection could just mean replacing the Spec ValueHolder > with your domain ValueHolder so changes to the domain model would > automatically propagate to the UI presentation without providing explicit > code in ComposableModel>>initializePresenter. > > However, since I am still trying to understand and learn Spec, it's quite > possible I am missing some key point and there are reasons not to explore > this line of thinking! > > Thank you, > > Rob >
