Finalize Forms and Dialogs API. (MGNLUI-1030)

[MGNLUI-1033] Resolve relationships between FormDialog and FormView. Created: 04/Apr/13  Updated: 19/Jun/13  Resolved: 19/Jun/13

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

Type: Sub-task Priority: Major
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: apiteam, beta1, dialog-form, form-refactoring
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLUI-918 Form Dialog Split: Make them more ind... Closed
Template:

 Description   
  • FormDialog class has to be refactored/removed: this class used to be a significant component that was combining the Form and the Dialog. Now it doesn't do anything
    except for forwarding the method calls to the internal FormView. This class has to be removed or should actually implement functionality of the FormView.
  • FormView interface, ItemFormView which implements it. Should be renamed as the implementation contains a Form in the Dialog chrome and now Form and Dialog are separate concepts.
    I propose it to become an EditorView (ItemEditorView). As mentioned above - these could be merged with FormDialog.

Generated at Mon Feb 12 08:42:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.