On 11/8/05, Dave Howorth <[EMAIL PROTECTED]> wrote: > On Tue, 2005-11-08 at 10:37 +0000, David Baird wrote: > > > > In fact, there's very little code in Maypole that counts as V - that's > > all in TT and the templates, and most of the code in > > Maypole::View::Base and ::TT is about communicating with the View. > > Similarly for the model, but it's a bit more complex, because in a > > simple Maypole app, like BeerDB, the only model is the Maypole model. > > But in a complex app, the Maypole model becomes the ribbon that joins > > the Controller to the underlying model. > > An interface to the M. > > Most of this stuff is what I call the Presentation. I'm a fan of Martin > Fowler and got that term from his patterns. There are many pages on his > site, which is a bit disorganized, and I still haven't completely > figured out my take, but see for example > http://www.martinfowler.com/eaaDev/OrganizingPresentations.ht > http://www.martinfowler.com/eaaDev/PresentationModel.html
Yep, that seems to describe what we've got pretty clearly. The browser is a thin client, and we get synchronization for free (in each HTTP request event). The Maypole model receives events (the Exported method in the URL) from the view. It does some processing and changes values of certain variables. Then the view (Maypole::View::Base) is responsible for picking up these new values (via the vars() method) and displaying them in the templates. I'll add 'Presentation Model' and these links to the terminology chapter, I think they're very useful. d. ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Maypole-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/maypole-devel
