[MGNLUI-711] Make choose dialog part of app framework Created: 22/Feb/13  Updated: 15/Mar/13  Resolved: 14/Mar/13

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

Type: Bug Priority: Neutral
Reporter: Tobias Mattsson Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: apiteam
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLDAM-146 Update Assets app for changed choose ... Closed
dependency
is depended upon by MGNLUI-686 Move content app framework to its own... Closed
is depended upon by MGNLUI-687 Extract form and fields to a separate... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

We add a method openChooseDialog() on AppController and on App.



 Comments   
Comment by Espen Jervidalo [ 28/Feb/13 ]

At some point the idea was to have an app providing chooseDialogs to implement a dedicated interface. This way we wouldn't have an empty method openChooseDialog.
Any reason we dropped that idea?

Comment by Espen Jervidalo [ 28/Feb/13 ]

Instead of passing the path, we could pass an object array. The actual implementation of the openChooseDialog could be more independent and allow e.g. opening different views or whatever.

Comment by Tobias Mattsson [ 14/Mar/13 ]

Yes, but that is not the scope of the this ticket.

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