[MGNLUI-4913] As a dev I would like to be able to implement a master-detail view/sub-app with the UI framework without huge effort Created: 07/Jun/18  Updated: 05/Mar/21

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

Type: Story Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: v8-wishlist
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Date of First Response:
Epic Link: Simplify YAML configuration
Sprint: later

 Description   

Idea is as follows:

  • take a tree/list view
  • take a form view
  • put them next to each other on one screen
  • let the form view display elaborate info of the item selected in the tree/list
  • use the new Ui framework techniques to achieve the result

As a result of the effort it would be nice to collect input re: smoothness of the process and dev experience with the improved framework.

User stories:

As an editor, I want to select an item and edit it immediately, so that I can make small edits quickly without having to jump from subapp to another. For example, rescheduling many events. Select, edit, save, select next...

As a developer, I don't have fire obscure ContentChangeEvents to refresh data in my views, so that my code is simpler and i don't have to handle refreshing views manually.

Acceptance criteria:

  • Side-by-side (master-detail) layout
  • Demo
    • Idea 1: In Tours app, select a tour in master view and edit the select tour in detail view.
    • Idea 2: In Assets app, select a folder in master view and show item thumbnails in a detail view.   
  • Achievable without hacks and in an understandable way


 Comments   
Comment by Saimir Gasa [ 30/Aug/18 ]

Team indicates the issue is a nice-to-have. Not necessary for 6.0 Release.

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