Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: ui-rewrite
-
Component/s: Web Interface
-
Labels:None
-
Number of attachments :
Description
replace struts2 with a new web framework (plain js/html application)
I'd prefer that rather than a "big bang" change, we implement this as having an alternative that is not default, and work to pull the logic out of the struts actions / xmlrpc where needed to be in a single place.
When we feel the new UI is "complete enough" we can switch over - but I guess there'll have to be a call about some features we want to drop.
Would you agree?