Robert Rawlins said: > > The first element that confuses me is this use of âviewsâ and > how I should be applying them to me project. Should I be creating a > view for every page in my application, or is the idea that each view > forms a âwidgetâ and then pages can be assembled from several > views?
You can do both. > For instance, in my application I have a short list of > âlatest newsâ type features, which I want to display on several > different pages around the site. Do I need to replicate this code > every time for each view, or do in include it with <cfinclude> ,or > can I have the framework assemble it for me into the pages? You can define an event with multiple views with the same name and just have the latter views set the append parameter to true. Or you can give all views a different name and construct a page from them in a separate result. > Next I wanted to quickly cover the process of retrieving query data > into my view. On occasion I find myself needing un-manipulated query > data in my views, is it âproperâ of me to have my controller > speak directly to the ORM and collect that? Or should I always > request it through my model? I would recommend putting an object in your model that returns queries. > Another quick point with regards to controllers, how do you guys > deal with separating your controllers? Should I be building them per > task? So one controller for my Shopping Cart, one for my Reporting > and another for User Information and so forth? That is pretty much what we do. Jochem ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & Flex 2. Free Trial http://www.adobe.com/products/coldfusion/flex2/ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:271854 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
