> From: Rob Nagler [mailto:[EMAIL PROTECTED]] > Sent: 10 June 2002 20:41
> ... a Facade is the front face of the web site which includes colors, > text, URLs, etc. All the other MVC components talk to the currently > selected Facade when they need these values. > The controller calls Bivio::UI::Task->parse_uri, which strips the > "*<facade>" from the URL (if there) and sets the facade before parsing > the rest of the URL. The default Facade is www.bivio.biz, which is > why we don't need a rewrite. > The links are generated by the Facade component Bivio::UI::Task. Sounds interesting, can you briefly describe the MVCF parts, and what their responsibilities are? Have you split the View into View + Facade? What are the differences between your MVCF and the MVP pattern? > This allows the Facade to pick its own URLs. ... > URLs are part of your user interface, not your controller. I think I like this, though the w3 might not 8-) > We rarely change the controller except to add new function. > Query and form values are parsed by the Models after they are > translated to key/value format by the controller. I definitely like this - small number of relatively generic Controllers seems to me to be a desirable goal of an MVC arch. > abstracted the concept of paging and drill down in our ListModel and > Table classes. I find that the mix of business object e.g. Bank Account and presentation objects, e.g. Table can lead to confusion - are your Table objects just a way of organising data, or do they contain presentation style hints -e.g. dynamic width indication etc? Do you have something similar to a Bank Account object with some primary properties and containing a collection of current Transaction objects? Or do you focus on the presentation style objects - Tables, nested Tables, Lists etc? I looked over your site and code, compact and impressive - probably a stupid question, but are there any higher-level overviews of your approach / framework? TIA Jeff
