Details
-
New Feature
-
Resolution: Done
-
Major
-
3.4.7
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
DevX 5, DevX 6
-
8
Description
Blossom currently relies on the UI Framework compatibility layer with no option to move to the 6 UI Framework. As a result, new definition features are not directly accessible to Blossom users, and the auto-conversion for custom fields is an additional step in the way.
Checklists
Attachments
Issue Links
- is depended upon by
-
BLOSSOM-279 Validator configuration is not working when using validators in Blossom dialogs
-
- Open
-
- relates to
-
BLOSSOM-288 Validator is always executed
-
- Closed
-
-
BLOSSOM-295 Allow injection of Spring managed components in Dialog/TabFactories
-
- Closed
-
-
MGNLUI-7100 Re-introduce definition builders
-
- Closed
-
-
BLOSSOM-291 Migrate magnolia-blossom-sample-module to UI 6 framework
-
- Selected
-
- to be documented by
-
BLOSSOM-296 DOC: Mgnl 6.2.18 - Support for UI 6 definitions in Blossom's @DialogFactories and @TabFactories
-
- Closed
-