[MGNLUI-47] Review the contents and deps of ui-model, ui-framework and ui-admincentral Created: 17/Oct/12  Updated: 20/Feb/13  Resolved: 14/Feb/13

Status: Closed
Project: Magnolia UI
Component/s: framework
Affects Version/s: 5.0
Fix Version/s: 5.0

Type: Task Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-42 Move JcrContainer related classes fro... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

We need to review what goes where and why as the lines have blurred recently. Also, there seems to be entire packages, inherited by the PoC, which are currently not used and could possibly be removed altogether, i.e. info.magnolia.ui.framework.editor.
Another example is ui-framework depending on Vaadin. Should't it be UI technology agnostic? Currently that dep is only needed by the interface info.magnolia.ui.framework.view.View.



 Comments   
Comment by Federico Grilli [ 25/Oct/12 ]

Postponing to next sprint

Comment by Tobias Mattsson [ 14/Feb/13 ]

The View interface is allowed to depend on Vaadin. Basically ui-framework is no longer UI technology agnostic.

Is this ticket complete now?

Generated at Mon Feb 12 08:33:04 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.