On Feb 4, 2008, at 5:05 PM, Conal Tuohy wrote: > On Mon, 2008-02-04 at 17:59 -0600, Dorothea Salo wrote: >> On Feb 4, 2008 4:23 PM, Conal Tuohy <[EMAIL PROTECTED]> wrote: >>> Recently there was a discussion here about programming Manakin >>> aspects >>> in XSLT. I thought I'd post here a small example of something I >>> did here >>> to show how it can be done. >> >> Why would one program XSLT into an Aspect rather than a Theme? >> > I wrote the breadcrumb example as an Aspect because it's intended to > apply independently of Theme. > > In general I think pretty much anything which could be done in an > Aspect > probably should be, and Themes should be reserved for purely > presentational ... ah ... aspects. It's a question of Separation of > Concerns. > http://en.wikipedia.org/wiki/Separation_of_concerns
Conal, I originally brought up the idea, I thought it would be easy once I got got an example configured in a sitemap, "but not that easy!". I have to say well done and I think this fits precisely the intention I spoke of. I agree on the separation of concerns, adding content to the page should be a different task than changing its "look and feel". > In our case (at Victoria University of Wellington) we only have one > theme where the breadcrumbs appear, so the additional breadcrumb could > have been added within the theme. But it would have been a hack. By > adding the breadcrumb in an Aspect, we can later change our Theme and > not have to revise the breadcrumb addition at all. Or we can revise > our > breadcrumb structure without having to change the Theme at all. > > I'm making more changes to the content of the dri:options (the > navigation menu), which I'm also doing as an Aspect. This is entirely > independent of how we want to render that menu in HTML form. This may be the way we go for our customizations here at MIT. Our initial pass at embedding DWell into Manakin is theme driven (and being implemented by Sands Fish). However, this separation of concerns will allow us to not have to replicate the inclusion of structure/configuration of DWell in each theme and instead focus on keeping themes there for layout and style only. Cheers, Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
