[MGNLUI-192] As a developer I can implement a custom choose dialog which is independent of the workbench so that I can provide access to items as needed. Created: 21/Nov/12 Updated: 17/Sep/13 Resolved: 14/Sep/13 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | forms, framework |
| Affects Version/s: | None |
| Fix Version/s: | 5.1 |
| Type: | Story | Priority: | Critical |
| Reporter: | Jan Haderka | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | content-app, dialog, framework | ||
| Remaining Estimate: | 5d | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | 5d | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| 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)
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | RC 1, 5.1 Beta1- Frontend, 5.1 - RC1 | ||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
WAS: "Review, Document and Improve Choose Dialog" The ChooseDialog structure and related code has grown over time naturally. In order to make this structure, it's purpose and use easy to understand to other developers writing their own apps we need to
Idea: Instead of getting the app from the appController and then creating the presenter and opening it manually, this should be abstracted by the appController: appController.openChooseDialog("app name") |