Hi Sue, maybe you know it, but good news for you is that you don't have to switch to XMLUI in one day. You can run JSPUI and XMLUI in parallel on the same DSpace instance at the same time and you can abandon JSPUI only when you feel it's ready and tested.
> Question I: Your understanding is correct AFAICT. Specifically, to make changes to XMLUI themes, you don't even need to do the quick build if you're careful. You can work in the [dspace]/webapps/xmlui/themes directory instead of [dspace-src]/webapps/xmlui/themes when you're developing your theme. The only precaution you need to take is to remember to copy your changes from [dspace]/webapps/xmlui/themes to [dspace-src]/webapps/xmlui/themes before you rebuild DSpace, which is usually when you're doing an upgrade or deploying a new webapp. So developing XSLT is really quick because to see the changes you can usually just reload the page in your browser (barring occassional caching issues when you need to stop tomcat, clear cocoon cache and restart tomcat). Same goes for Messages.properties and messages.xml. I _think_ the same should work for JSP files but I never worked with JSPUI. What I recommend you here may not be the procedure from the manual but I use it successfully all the time. Another advantage of developing a XMLUI theme is that when you need to make changes, you can make a copy of your production theme on the production server and develop it without endangering the production theme. The procedure is, e.g.: 1) cd [dspace]/webapps/xmlui/themes/ 2) cp -r Mirage Mirage-new 3) mv Mirage-new/Mirage.xsl Mirage-new/Mirage-new.xsl 4) edit Mirage-new/sitemap.xmap and change theme-path and theme-name to Mirage-new 5) view any page using the new theme: http://example.com/?themepath=Mirage-new/ I repeat, don't forget to copy your changes from [dspace] to [dspace-src] before you do the next mvn package/ant update. (Well, ant update makes backup of everything including the webapps directory, so it's hard to screw up even if you forget) > Question II: > 1. Implement Manakin with one of the default themes (Classic, > Reference, Kubrick) so we can use Discovery This is no harder than deploying the default JSPUI application for the first itme. Just follow the manual and try it out in testing environment. As I said, you can run JSPUI and XMLUI in parallel on the production server. So you can have JSPUI at http://example.com/ and XMLUI at http://example.com/xmlui/ and only switch XMLUI to http://example.com/ when you feel it's ready and tested. > 2. Add expanding and collapsing interface to community-list hierarchy This is also easy because it's just a bit of Javascript, so basically it's applicable to both JSPUI and XMLUI. No need to redeploy when experimenting with this. > 3. Possibly create/implement our own theme You can start with the default Mirage theme with Discovery and the simple changes like expand/collapse community list and put it in production. Then you can make a copy of the theme and add features gradually. I hope these tips will be helpful to you. Let me know if you need any more details. Regards, ~~helix84 ------------------------------------------------------------------------------ RSA® Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
