Hi, That can be argued either way - Cocoon has a significant overhead both in processing time and resource usage. Without finding a way to address that, we can't use it for our situation.
The currenty JSP interface is badly implemented. A well-written JSP 2 - or Freemarker, Velocity, etc. - with full use of CSS, would remove or reduce many of the pain points that currently exist with the JSP interface. Right now, there is no one single UI that can be all things to all users within the community. There probably never will be. So a "there can be only one" approach is unlikely to work. In some ways, I would say it is more important to support people developing UIs rather than to support a particular UI. Although if there are multiple UIs under development, one will inevitably be the 'primary' interface - which should be led by the community's needs. Right now, that judgement may be a little skewed given existing bad experiences of a poor implementation. How does Cocoon fare in the general case? Is it easy enough for newcomers? Can people with advanced customisation requirements get to grips with and work efficiently with it's architecture? Will it's quality be maintained, improved or degrade over time? These types of questions can only be answered with experience. Would a fresh JSP 2 or template based implementation change opinions or scratch an itch that may occur in the future? As it stands, there are enough people that either need or are interested in such a development for it to happen. G George Hamilton wrote: > Hi Christophe > > Having been developing extensions for two DSpace repositories for a > short time in JSP and now Cocoon I must say I would be dismayed if the > DSpace community decided to drop Cocoon. Cocoon is extremely powerful > and perfect for what I have been doing. There may be a learning curve > with Cocoon but that goes for any new technology. Having recently > upgraded DSpace 1.5.0 to 1.5.1, I was very pleased not to have to go > through every locally modified JSP (and Java) file and manually merge > them with the new version, as was the case the JSP version. > > George > > > Christophe Dupriez wrote: >> Hi Robin, >> >> I would like to strongly support your proposal. >> >> But there is one question: will the DSpace community continue to >> support two UI ? >> Personally, I prefer JSP to Cocoon but I think that supporting two >> interfaces on the long term will be unmanageable... >> How people really using Manakin now evaluate this issue? Are they >> satisfied? Do they think JSP are easier, simpler, faster? Or they >> enjoy new useful features with Manakin and are happy with the overall >> organisation it imposes? >> >> Personally, I still belief "cleaned-up" JSP with a good API to access >> DSpace objects (designed from Manakin experience), some new JSTL tags, >> some EL functions would be easier to learn and use than Cocoon. >> But I did not made the transition (still deriving my work form DSPace >> 1.4.1): I may be completely wrong!! >> >> Have a nice week-end, >> >> Christophe >> >> Robin Taylor a écrit : >>> Hi Mark, >>> >>> I recall a short while ago you commenting on the fact that there had >>> been no clamour from the community for a JSP 2.n based UI, well I >>> would like to start a small scale clamour. Is there any reason why we >>> couldn't include the necessary jar(s) in the daddy pom.xml and the >>> appropriate entries in the web.xml, that would allow those who wished >>> to take advantage of 2.0 features ? I have been making changes to >>> some pages recently and it does my head in having to resort to >>> scripting within the pages. >>> >>> Cheers, Robin. >>> >>> >>> >>> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK& win great prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Dspace-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/dspace-devel >> > > This e-mail is confidential and should not be used by anyone who is not the original intended recipient. BioMed Central Limited does not accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of BioMed Central Limited. No contracts may be concluded on behalf of BioMed Central Limited by means of e-mail communication. BioMed Central Limited Registered in England and Wales with registered number 3680030 Registered Office Middlesex House, 34-42 Cleveland Street, London W1T 4LB This email has been scanned by Postini. For more information please visit http://www.postini.com ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
