[MGNLUI-5026] Consider a bridge between m5 and m6 dialog/editor definitions Created: 18/Feb/19  Updated: 11/Mar/21  Resolved: 25/Oct/19

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

Type: Task Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: 0.75d Remaining Estimate: 1h
Σ Time Spent: 6.25h Time Spent: 2h 46m
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
documentation
to be documented by MGNLUI-5420 DOC: Field definition converters Closed
duplicate
duplicates MGNLUI-4670 Dialogs created in M5 work as-is in M6 Closed
relation
is related to MGNLUI-5421 Jcr based data providers ignores the ... Closed
is related to MGNLUI-5478 Issue with null representation in Tex... Closed
is related to MGNLUI-5430 Create field definition converters fo... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLUI-5408 Create RichTextFieldDefinition converter Sub-task Closed Šimon Demočko  
MGNLUI-5409 Create CheckboxFieldDefinition converter Sub-task Closed Adam Siska  
MGNLUI-5410 Create CodeFieldDefinition converter Sub-task Closed Adam Siska  
MGNLUI-5411 Create converters for definition base... Sub-task Closed Milan Divilek  
MGNLUI-5414 Create LinkFieldDefinition converter Sub-task Closed Milan Divilek  
MGNLUI-5425 Create BasicUploadFieldDefinition con... Sub-task Closed Adam Siska  
MGNLUI-5429 Convert field validators and converte... Sub-task Closed Milan Divilek  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Documentation update required:
Yes
Epic Link: UI framework: forms, dialogs, content editing
Sprint: UI Framework 8, UI framework 9, UI Framework 10, UI Framework 11, UI Framework 12
Story Points: 13

 Description   

The update variation of editor configuration encourages separation of the model definition from the layout. The m5 version mixes them together.

In order to provide a smooth transition, I believe we could implement a proxy definition (or even a dialog/sub-app) that would take a definition in a form that resembles the m5 structure and relay/transform it into model/[tab]layout variation on the fly and delegate to the updated implementation.


Generated at Mon Feb 12 09:22:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.