[MGNLUI-4622] Vaadin 8 based Switchable field solution Created: 25/Apr/18  Updated: 26/Jun/19  Resolved: 04/Oct/18

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

Type: Task Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLUI-4672 Switchable form view creates empty no... Closed
relation
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Account:
Epic Link: UI framework: forms, dialogs, content editing
Sprint: Kromeriz 161, Kromeriz 162
Story Points: 8

 Description   

Naive idea would be to base that on the new composite field / sub-form. (like before)

As such, a switchable field would generate a sub-form consisting of:

  • a select/option-group field
  • plus an arbitrary field depending upon selection of the former

Meanwhile, we might seek for a more elegant/integrated solution.

 

Acceptance criteria for switchable field:

  • layout will contain radio or select field
  • definition will allow to set radio buttons layout to either vertical or horizontal
  • upon changing the radio/select button's value, defined sub-form will be displayed
  • upon changing the language, correct sub-form language variant will be displayed
  • upon saving the form, values will be written to the node in same format as in "old" switchable field


 Comments   
Comment by Saimir Gasa [ 12/Sep/18 ]

jsimak, could you please provide an Acceptance Criteria for this and when would you define this as done?

Comment by Roman Kovařík [ 09/Oct/18 ]

Closing with linked follow up ticket.

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