Project organization and health (MGNLUI-31)

[MGNLUI-38] Move separate widgets modules into magnolia-ui-vaadin-common-widgets Created: 16/Oct/12  Updated: 11/Feb/13  Resolved: 30/Oct/12

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

Type: Sub-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
Template:

 Description   

Rationale:

  • follow same pattern as GWT and Vaadin, that is providing a default set of widgets in one place and one single point of extension for custom or specialized widget set. Moreover our currently separated widgets, i.e. Dialog, are not going to be distributed or used as stand-alone add-ons.
  • do not spread GWT client code into several places
  • it is often difficult to determine what should go into a separate module/widget set and what in the Vaadin integration project.
  • Vaadin integration project will only contain server-side code
  • page editor will remain a separate module as it might be released independently of other widgets
  • m-u-vaadin-widgetset will only contain MagnoliaWidgetSet


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

After discussing this issue with Philipp we agreed that

1) page-editor should be again in a separate module, as it might be released independently. It is OK that all other widgets (i.e. actionbar, shell, dialogs etc) stay all in one module
2) we need a widgetset module only consisting of Magnolia widgetset.gwt.xml which aggregates our own widgets and custom ones
3) the widgets now part m-u-vaadin-widgets will move to a new m-u-widgets project with the exclusion of page-editor, as mentioned above

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