[MGNLDAM-184] Replace our asset chooser with the standard chooser UI Created: 28/Mar/13  Updated: 08/Dec/16  Resolved: 07/Jun/13

Status: Closed
Project: Magnolia DAM Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Improvement Priority: Blocker
Reporter: Andreas Weder Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: assets_app
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLDAM-248 Remove old class and configurations. Closed
depends upon MGNLUI-1577 Make idKeyTranslator configurable in ... Closed
is depended upon by MGNLDAM-185 Asset chooser dialog shows videos as ... Closed
is depended upon by MGNLDAM-183 When choosing a video asset, I can't ... Closed
relation
is related to MGNLRSSAGG-211 Old properties are still present in b... 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

 Description   

I suggest to replace the existing asset chooser dialog for Magnolia 5.0 with the standard chooser UI offered by content app.

The current chooser has a number of issues we'd have to fix:

  • it has no search
  • it has no other view than the thumbnail view, which is especially bad if we have two assets with the same preview
  • the hierarchy chooser is a new element, which we would have to properly style.

What we would loose:

  • navigating the hierarchy in the thumbnail view

What we would gain:

  • proper search
  • a list and tree view
  • we can focus on finalizing the list and tree views and the corresponding chooser UI

I do have mockups for introducing hierarchy browsing in both list and thumbnails view. I'd like to implement this feature properly in a later release.



 Comments   
Comment by Andreas Weder [ 28/Mar/13 ]

Marking this as a blocker since I'd like to discuss this soon.

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