Difference between revisions of "ESciDoc Admin Tool"
Jump to navigation
Jump to search
m (→Requirements) |
m (→XForms) |
||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 25: | Line 25: | ||
*todo: evaluation of FWs | *todo: evaluation of FWs | ||
==Review/Evaluation of appropriate web-frameworks== | |||
see also [http://colab.mpdl.mpg.de/mediawiki/Java_Web_Framework a previous evaluation]. | |||
===Apache Wicket=== | |||
http://wicket.apache.org/ | |||
* Not very lightweight in my opinion | |||
* Swing-like implementation in Java | |||
* Pro: Pure HTML on view side | |||
===Grails=== | |||
http://www.grails.org | |||
* language: Groovy (runs in JVM) | |||
* Java libraries can easily be used | |||
* First glance: Fast development of easy use-cases with db-sources. | |||
* Provides some UI widgets | |||
* JQuery can be used as "Plugin" | |||
* growing community | |||
===Apache Cocoon=== | |||
http://cocoon.apache.org/ | |||
===XForms=== | |||
* W3C recommendation | |||
* Specification is not supported by most webbrowsers (needs special plugins) | |||
* Some solutions try to bypass this problem by transforming XForms into Javascript on server side (e.g. http://chibaxforms.org/) | |||
* Anyway, Chiba and other demos do not work with my Firefox 3.5 browser. | |||
* Not a suitable solution | |||
[[Category:ESciDoc|Admin Tool]] | |||
Latest revision as of 09:37, 7 January 2011
eSciDoc Admin Tool[edit]
The Admin Tool shall support administrative tasks for eSciDoc infrastructure and solutions. Information on initial implementation available at ESciDoc Admin Tool initial implementation
Requirements[edit]
- functions
- administrate core and solutions
- create/alter roles
- control re-cache/re-index
- implementation
- GUI
- Style should be easily changeable and be based current solutions. --Haarlaender 15:12, 19 October 2009 (UTC)
- CLI (?)
- I don't think this is necessary as an additional abstraction layer. There is still the SOAP and REST interface --Haarlaender 15:12, 19 October 2009 (UTC)
- plugin interface to extend support for solutions
- Maybe like a set of managers (one for managing users, one for contexts etc.) with user interfaces that can be "pre-configured". Means certain values are preset by the current solution. --Haarlaender 15:12, 19 October 2009 (UTC)
- GUI
- check on more light-weight technology esp. for the GUI
- 1&1 GUI widgets
- Groovy, Grails
- GWT - javascript too cryptic, widgets compared to what other FW provide
- javaScript based
- portal/portlets
- todo: evaluation of FWs
Review/Evaluation of appropriate web-frameworks[edit]
see also a previous evaluation.
Apache Wicket[edit]
- Not very lightweight in my opinion
- Swing-like implementation in Java
- Pro: Pure HTML on view side
Grails[edit]
- language: Groovy (runs in JVM)
- Java libraries can easily be used
- First glance: Fast development of easy use-cases with db-sources.
- Provides some UI widgets
- JQuery can be used as "Plugin"
- growing community
Apache Cocoon[edit]
XForms[edit]
- W3C recommendation
- Specification is not supported by most webbrowsers (needs special plugins)
- Some solutions try to bypass this problem by transforming XForms into Javascript on server side (e.g. http://chibaxforms.org/)
- Anyway, Chiba and other demos do not work with my Firefox 3.5 browser.
- Not a suitable solution