[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:
relation
is related to MGNLUI-1992 Develop field adapter for a workbench. Closed
is related to MGNLUI-1993 Remove choose-dialog related hacks ou... Closed
is related to MGNLUI-1996 Streamline dialog definitions, packag... Closed
is related to MGNLUI-1997 Create registry and definition manage... Closed
is related to MGNLUI-1998 Improve ChooseDialogPresenter and Cho... Closed
is related to MGNLUI-2001 Adapt changes made to dialog API to t... Closed
is related to MGNLUI-2006 Design special app descriptor for con... Closed
is related to MGNLUI-2020 Provide default choose dialog configu... Closed
is related to MGNLUI-2027 Improve signature of openChooseDialog... Closed
is related to MGNLUI-2052 Create migration tasks necessary for ... Closed
is related to MGNLUI-2071 Make sure new dialog concept works wi... 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)
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

  • review naming of the classes
  • review javadoc
  • document the structure and it's use in architecture documents & diagrams
  • provide parallels or examples of where how this structure is used and what is intended use
  • restructure the code to minimize duplication and simplify creation of such dialogs

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")
Currently there is only one chooseDialog per app. Better per subApp?


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