Hi, Am Montag, 25. Februar 2008 schrieb Derick Rethans: > On Sat, 23 Feb 2008, Thomas Nunninger wrote: > > Am Samstag, 23. Februar 2008 schrieb James Pic: > > > Thomas Nunninger wrote: > > > > Don't know how other systems solve that. In eZ Publish those > > > > "zones" are just some templates that are included in > > > > page_layout.tpl. Things like tree menu or a box with latest > > > > news are build via template functions that fetch and represent > > > > the data. You can argue that this is a little bit against > > > > strict MVC as there is some logic inside the templates. But it > > > > is somehow intuitive. Also you do not need to touch the "core" > > > > of your application or change some configs if you want to add a > > > > new box/zone. > > > > > > That's exactly what i'm talking about. The other problem with > > > zones is that their business-logic is limited to what the > > > template is allowed to use. > > > > As you can create custom template functions, I see no limits. The > > only important thing is that you have enough information (in eZ > > Publish this are e.g. the currennt node/object, the user and some > > other). > > But pulling in content by functions reverses the way how content is > usually rendered. Then you give the templates logic again, instead of > letting the logic render its data through a template. I think such > practise should be avoided.
I know about this drawback. But I'm not sure about a good solution regarding the problems in my mail(s). What would you suggest? Would you prefer multiple controllers or protocoll-specific routers? Do you have some other ideas? Thanks and have a nice day Thomas -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
