On 8 October 2010 19:06, Walker, David <[email protected]> wrote:
> > breaking up the xslt into separate files for each page
> > actually defeats the design goals of the XMLUI theming tier.
> > I.E. having one file within which all customizations reside to
> > manage your theme.
>
> I think there are advantages and disadvantages to both approaches.
>
I agree there are pros and cons to both approaches. And yes, if we focus on
some specific areas of the implementation, there may be too much
presentation being encoded in the DRI.
But in general, I would agree with Mark. The design of Cocoon / Manakin is
based around pipeline processing of the model, and for you to be able to
chain in components/aspects, you neither want to do it after a page based
transformation (and have to put in multiple special cases for each of the
pages), or have page based transformations after the aspect (requiring that
you modify each of those pages as well, and not just add the new component).
But the thrust of my argument here is that we should have *templates* that
> correspond to pages. Whether each of those templates lives in it own file,
> or whether they all live together in one big file, is a minor detail, as far
> as I'm concerned.
>
I definitely agree with your point that the approach taken by Cocoon /
Manakin is a learning curve for some people, and that a number of people
would benefit from having page based templates. But if you are going to do
that, then you might as well set Cocoon aside - there isn't any point in
taking the added dependencies, xml serialization and transformation, if you
can't make [effective] use of the transformation pipeline.
Imho, if you want to use a page based approach, then you are better off
using Spring WebMVC, and writing the templates in Freemarker [disclaimer: I
did start implementing such a framework, but it doesn't have any functional
components as yet].
G
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
