[
https://jira.nuxeo.org/browse/NXP-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anahide Tchertchian updated NXP-4801:
-------------------------------------
Description:
Widgets can already be registered independently from layouts. This makes it pos-
sible to reuse a defined widget in several layouts.
The global registry of widgets could behave as a registry of widget templates,
so
that a given widget could be used :
- as is, with same style, mandatory settings, but mapping a different field
- as is, with same field mapping, style, etc... but (not) being mandatory
Designing a widget merge mechanism for this would make it even more easy to
define specific widgets, inside or outside of layouts.
Mechanisms to render a widget independently from a layout already exist: the tag
"nxl:widgetType" does render a widget, but needs the whole widget configuration
as attributes, and the tag "nxl:widget" performs rendering of a given widget in
-
stance, that has been already computed by the parent layout.
A new tag could be defined to take only the name of a global widget, a mode, the
object to map, and query the layout service to get the configuration. That kind
of
tag could be used in every page, inside or outside a form. As a reminder,
layouts
and widgets do not require a document model: any kind of object will do, using
the
object attribute name (getter/setters need to be available) as field names.
+ see NXP-4412: widget mode cannot be switched when used within a layout
was:
TODO:
- explain needed features
+ see NXP-4412: widget mode cannot be switched when used within a layout
> Display a standalone widget in a given mode
> -------------------------------------------
>
> Key: NXP-4801
> URL: https://jira.nuxeo.org/browse/NXP-4801
> Project: Nuxeo Enterprise Platform
> Issue Type: Sub-task
> Reporter: Anahide Tchertchian
>
> Widgets can already be registered independently from layouts. This makes it
> pos-
> sible to reuse a defined widget in several layouts.
> The global registry of widgets could behave as a registry of widget
> templates, so
> that a given widget could be used :
> - as is, with same style, mandatory settings, but mapping a different field
> - as is, with same field mapping, style, etc... but (not) being mandatory
> Designing a widget merge mechanism for this would make it even more easy to
> define specific widgets, inside or outside of layouts.
> Mechanisms to render a widget independently from a layout already exist: the
> tag
> "nxl:widgetType" does render a widget, but needs the whole widget
> configuration
> as attributes, and the tag "nxl:widget" performs rendering of a given widget
> in -
> stance, that has been already computed by the parent layout.
> A new tag could be defined to take only the name of a global widget, a mode,
> the
> object to map, and query the layout service to get the configuration. That
> kind of
> tag could be used in every page, inside or outside a form. As a reminder,
> layouts
> and widgets do not require a document model: any kind of object will do,
> using the
> object attribute name (getter/setters need to be available) as field names.
> + see NXP-4412: widget mode cannot be switched when used within a layout
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
