On Wed, 2002-03-13 at 02:57, Ben Peter wrote: > All, > > after weeks of trying to implement HMVC with struts, I have now had a look at > turbine (which I find more flexible and 'clean' from a first look), of which > the documentation says that HMVC can be implemented, even if the straight road > does not lead you there. > > Has anyone used turbine for that and can provide examples or a rough outline?
All things view related in Turbine are dealt with in templates, usually velocity templates? So are you looking for a hierarchical structure for visual attributes? So if you have a tree for your site and a particular attribute isn't specified you want a mechanism to walk back up the tree to find that attribute? That would be easy relatively easy to do. But if you mean programmatic components then I'm not quite sure what you have in mind. > I have found that HMVC (Hierarchical Model-View-Controller) is the only way to > cleanly develop true 'components' which can be separately tested and very > easily reused. Still, I have not found a framework which has easy support for > this, so that I had to have my own implementations / extensions, which I do not > trust ;-) - for struts, they rely on doing subrequests, which is both costly > and unelegant... > > Any help, suggestions, and comments are appreciated. We are definitely interested in reuse. Can you give an example of a small component that you would like to applied in a hierarchical way? > Cheers, > Ben > > -- > Benjamin Peter +49-69-96244395 > Application Engineer Moerfelder Landstr. 55 > (zentropy:partners) 60598 Frankfurt, Germany > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
