i've done stuff with my own informal model, view and controller separation. i've done things with pureMVC and now i've done a couple of things with robotlegs. i much prefer robotlegs, it's made me think of a lot of things differently, has reduced the size of my classes and i think enforces a better separation of the different tasks in your application which helps with code re-use.
On 26 February 2012 18:20, John McCormack <j...@easypeasy.co.uk> wrote: > Thanks Henrik, > > I guess things are much simpler if all parts know enough about the data > format to be able to do what they need to do. I think I was imagining > things more complicated than they need be. > > Thanks Ben, this was interesting... > http://www.slideshare.net/**RichardLord/application-** > frameworks-the-good-the-bad-**the-ugly<http://www.slideshare.net/RichardLord/application-frameworks-the-good-the-bad-the-ugly> > > Robotlegs has good press. I wonder what people on this list prefer? > > John > > > On 26/02/2012 14:07, Henrik Andersson wrote: > >> John McCormack skriver: >> >>> Kevin mentions... >>> "...need to transform the format to fit the view, you would do that in >>> the controller" >>> >>> Henrik mentions... >>> "The data changing should be done in an adapter that the controller puts >>> in between the model and the view." >>> >>> So the problems arise because the data that isn't quite what the model >>> stores, or isn't quite what the views use. >>> >>> At the same time the controller shouldn't know about requirements of the >>> model and views, but in this world of isolation and 'not knowing' about >>> other things we need adapters that do know the details of other parties. >>> >>> Do all systems need adapters that convert data into the appropriate >>> format? >>> >>> It is fine for the controller to know the identity of the formats >> involved. But understanding them is probably overkill. >> >> A well designed system will often have situations where the view and >> model use the same format, meaning that there is no need for any adapter. >> >> ______________________________**_________________ >> Flashcoders mailing list >> Flashcoders@chattyfig.figleaf.**com <Flashcoders@chattyfig.figleaf.com> >> http://chattyfig.figleaf.com/**mailman/listinfo/flashcoders<http://chattyfig.figleaf.com/mailman/listinfo/flashcoders> >> >> >> >> >> > > ______________________________**_________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.**com <Flashcoders@chattyfig.figleaf.com> > http://chattyfig.figleaf.com/**mailman/listinfo/flashcoders<http://chattyfig.figleaf.com/mailman/listinfo/flashcoders> > _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
