[MGNLDAMEXT-1] Make search box in workbench configurable and allow additional components in it's location Created: 19/Sep/14  Updated: 16/Feb/15  Resolved: 22/Sep/14

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

Type: New Feature Priority: Neutral
Reporter: Jan Haderka Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLUI-3234 Allow additional components in workbe... Closed
dependency
is depended upon by MGNLDAMEXT-3 Multiprovider Asset App Closed
relation
is related to MGNLDAMEXT-5 Search component cannot be fully extr... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Currently search box is the only component that is allowed in top right corner of the view above workbench and is closely tied to view implementation. Apps like dam need additional filtering or selection criteria exposed in this area.
Once this issue is fixed, search box should be extracted and whole area should allow components to be displayed there to be configurable.



 Comments   
Comment by Jaroslav Simak [ 19/Sep/14 ]

https://git.magnolia-cms.com/gitweb/?p=enterprise/dam-ext.git;a=shortlog;h=refs/heads/MGNLDAMEXT-1

Comment by Jan Haderka [ 19/Sep/14 ]
  • Why are those extra components called extensions? Isn't there better name? We have already contentViews next to it so maybe contentTools (since any tool can be inserted there like S&R for PoC done previously) or contentFilters (since they filter what is seen in the view)?
  • Why is search treated special? Would not all (most) of those components need to register callback?
Comment by Jaroslav Simak [ 22/Sep/14 ]

Why are those extra components called extensions? Isn't there better name? We have already contentViews next to it so maybe contentTools (since any tool can be inserted there like S&R for PoC done previously) or contentFilters (since they filter what is seen in the view)?

i forgot to rename it - i called it contentTools.

Why is search treated special?

Search is quite tightly bound to the Workbench, thats why its always included in the toolbar.

Would not all (most) of those components need to register callback?

I think i don't understand - what kind of callback do you mean?

Comment by Jan Haderka [ 22/Sep/14 ]

Reviewed with Search & callback issues being handled in MGNLDAMEXT-5 as they expose deeper design flow in workbench/browser.

Generated at Mon Feb 12 00:40:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.