[
http://jira.magnolia-cms.com/browse/MGNLUI-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Grilli updated MGNLUI-38:
----------------------------------
Summary: Move separate widgets modules into
magnolia-ui-vaadin-common-widgets (was: Move separate widgets modules into
magnolia-ui-vaadin-widgetset)
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
was:
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
> Move separate widgets modules into magnolia-ui-vaadin-common-widgets
> --------------------------------------------------------------------
>
> Key: MGNLUI-38
> URL: http://jira.magnolia-cms.com/browse/MGNLUI-38
> Project: Magnolia UI
> Issue Type: Sub-task
> Security Level: Public
> Affects Versions: 5.0 Alpha1 S7
> Reporter: Federico Grilli
> Assignee: Federico Grilli
> Priority: Major
> Fix For: 5.0 Alpha1 S8
>
>
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
