Parent concept page describes how we should reorganize the widgetset to make it configurable and open for extension. This page highlights the concrete implementation choices (e.g. naming, packaging) that are made to fulfill the concept.
Configuration
New config nodes
Node name | Value |
---|---|
modules | |
ui-admincentral | |
config | |
widgetset | |
name | info.magnolia.ui.vaadin.gwt.MagnoliaWidgetSet |
theme | |
name | admincentral |
New definitions
- info.magnolia.ui.api.vaadin
WidgetsetDefinition
ThemeDefinition
ConfiguredWidgetsetDefinition
ConfiguredThemeDefinition
New class
- info.magnolia.ui.admincentral
AdmincentralUIProvider
Widgetset structure
git repo | groupId | artifactId | Widgetset name (.gwt.xml) | gwt:compiled | comments | |
---|---|---|---|---|---|---|
EE | ee-bundle | info.magnolia.enterprise | magnolia-enterprise-bundle-widgetset | info.magnolia.enterprise.MagnoliaEnterpriseBundleWidgetSet | check for 5.1 EE | |
enterprise / content-dependencies | info.magnolia.dependencies | magnolia-content-dependencies-widgetset | info.magnolia.dependencies.ContentDependenciesWidgetSet | just here as a ee module example | ||
CE | ce-bundle | info.magnolia | magnolia-bundle-widgetset | info.magnolia.MagnoliaBundleWidgetSet | replaces MagnoliaWidgetSet (5.0) - integration and compiler options | |
modules / dam | info.magnolia.dam | magnolia-dam-widgetset | info.magnolia.dam.DamWidgetSet | just here as a ce module example | ||
magnolia_ui / pages | info.magnolia.pages | magnolia-pages-widgetset | info.magnolia.pages.PagesWidgetSet | replaces PageEditorWidgetSet (5.0) | ||
UI | magnolia_ui | info.magnolia.ui | magnolia-ui-widgetset | info.magnolia.ui.MagnoliaUiWidgetSet | replaces CommonWidgetSet (5.0) | |
magnolia_ui / magnolia-ui-widgetset | info.magnolia.ui.vaadin | magnolia-ui-vaadin-table | info.magnolia.ui.vaadin.TableWidgetSet | extracted from CommonWidgetSet (5.0) | ||
magnolia_ui / magnolia-ui-widgetset | info.magnolia.ui.vaadin | magnolia-ui-vaadin-contextmenu | info.magnolia.ui.vaadin.ContextMenuWidgetSet | extracted from CommonWidgetSet (5.0) | ||
magnolia_ui / magnolia-ui-actionbar | info.magnolia.ui.actionbar | magnolia-ui-actionbar-widgetset | info.magnolia.ui.actionbar.ActionBarWidgetSet | just here as examples for further ui modularization | ||
magnolia_ui / magnolia-ui-mediaeditor | info.magnolia.ui.mediaeditor | magnolia-ui-mediaeditor-widgetset | info.magnolia.ui.mediaeditor.MediaEditorWidgetSet | |||
RAW | magnolia-vaadin-widgetset | info.magnolia.vaadin.widgetset | magnolia-vaadin-widgetset | info.magnolia.vaadin.MagnoliaWidgetSet | M5-agnostic vaadin components - not for now |
Theme structure
-
Implementation details
- Changing widgetset/theme config currently requires a server restart
- Is configuration really where we want widgetset config to be?
- Since developers should now use their widgetset extending ours
- Currently they would startup, change widgetset name in config, then restart
- e.g. magnolia / project.properties, module descriptors?
- ee-bundle might need to configure default widgetset differently too