Dorothea, This is a good question, and it's a bit open as too what the best practice is in my opinion. I think it is okay for themes to have dependencies to other themes as long as that dependency is document and enforced (preferably through maven).
One concept that we've been using is to have 'super' or main themes each with sub elements. Thus for A&M we have the main TAMU theme that actually consists of several themes. The directory structure is: TAMU/ TAMU/sitemap.xmap TAMU/lib/ TAMU/style/ The top level theme is called "TAMU" (Texas A&M University) which has sub directories containing shared resources ( lib/ for javascript, style/ for css). Then inside this super theme exist several 'sub themes' TAMU/main/ (the main A&M theme) TAMU/geofolios/ (a collection specific theme) TAMU/???/ (other themes are possible) Each of the sub themes have sitemaps.xmaps just like normal but they will reference the shared resources one directory up the tree as well as those below. So when you install these themes in the xmlui.xconf you'll use the theme path of "TAMU/main/" or "TAMU/geofolios/". As a nice trick you could also just install the "TAMU" theme because the top-level sitemap.xmap just forwards to the "main" theme. Does that make sense? Scott-- On Dec 27, 2007, at 12:22 PM, Dorothea Salo wrote: > This is possibly a very stupid question, but is it possible/advisable > for one Manakin theme to pull in XSLT from another theme? > > Use case: I'm zeroing in on being done with my first theme, and it's > got some utility templates that will be useful to *all* themes. (For > example: clickable authors and subjects, "current" class on the navbar > link for the current page, moving community/collection logos into > headers... and if anybody wants code for any of that, it's all here: > <http://cavlec.yarinareth.net/archives/category/librariana/dspace/manakin/ > >, > or email me and I'll shoot you the actual stylesheet if you promise > not to laugh.) > > For easier maintainability and future functionality expansion, I'd > like to pop those templates into their own stylesheet which all (or at > least most) themes would then inherit. I suppose what I'm asking is > what the best way is to set that up. > > Dorothea > > -- > Dorothea Salo [EMAIL PROTECTED] > Digital Repository Librarian AIM: mindsatuw > University of Wisconsin > Rm 218, Memorial Library > (608) 262-5493 > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
