Lyncode's main target at the moment is to improve the user experience, taking into account our close relationship with many DSpace administrators.
What is SpringUI?
SpringUI names a new UI for DSpace. It follows the MVC pattern and uses Spring Framework under-need.
Why another UI?
- Cocoon2 is heavy, low performance
"Because of all the work Cocoon does in parsing XML, processing XML with style sheets and XMLSchema, and then generating output, it is a core performance bottleneck."
- XSL isn't a template mechanism
- JSP isn't a template mechanism
- MVC seems to be an excelent approach for webapps
- The new interface will be easy to modify, one just need to know HTML, CSS and javascript (the templating mechanism will be intuitive)
- The template mechanism will allow developers to include UI inside jars, that makes an addin easy to build and complete just by having everything inside the developed jar
Inovations
- HTML5
- Mobile ready
- Addin ready (explain)
- Improved user experience (Hugo proposal)
- Features built on top of the rest-api? (discussing - AA accessibility)
What template mechanism will it use?
A newly under development template twig based mechanism (http://twig.sensiolabs.org/). It will support themes, pre-compiled templates (much faster UI experience).
It will use Solr?
Yes. Our experience says that improving user experience also means speed up DSpace UI responses, also auto-complete, auto-suggestion features and so on. As so, it will use Solr, more properly, the (search) discovery module.
When it will be released?
After DSpace 3.0 (2013)
Developers
Lyncode @ DSpace - dspace@lyncode.com
Hugo Ribeiro - hribeiro@lyncode.com (UI expert)
Ricardo Silva - ricardo@lyncode.com (Mobile expert)
Miguel Pinto - mpinto@lyncode.com (Database expert)
Miguel Peixoto - miguel.peixoto@gmail.com (Designer)
NOTE: this is a draft
