[MGNLUI-3234] Allow additional components in workbench toolbar Created: 03/Nov/14  Updated: 23/Jun/15  Resolved: 05/Mar/15

Status: Closed
Project: Magnolia UI
Component/s: workbench
Affects Version/s: None
Fix Version/s: 5.4

Type: New Feature Priority: Neutral
Reporter: Jaroslav Simak Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLDAMEXT-1 Make search box in workbench configur... Closed
dependency
depends upon MGNLUI-3263 Revise and generalise Page editor ext... Closed
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.

Optionally, we might consider allowing "extensions" in the workbench status bar as well (would be aligned with page editor extendability).



 Comments   
Comment by Aleksandr Pchelintcev [ 26/May/15 ]

Some remarks:

  • When creating a ContentTooPresenter with component provider - would be a good idea to provide a tool definition in vararg list, then presenter could use it to construct the view.
  • WorkbenchView.Listener#onSetSearchQuery => onSearchQueryChange
  • SearchContentToolPresenter - JavaDoc
Comment by Aleksandr Pchelintcev [ 04/Jun/15 ]
  • Manually fixed my previous remarks.
  • Discussed briefly quirks with Robert.
Comment by Mikaël Geljić [ 05/Jun/15 ]

Guess we could briefly review some naming after beta too:

  • Especially for definitions, still not much convinced by ContentTool, and it's gonna be harder to change afterwards (will require upgrades)
  • Simplify QueryStatementChangedEvent. Maybe we do this in depending ticket MGNLUI-3263 actually.
Generated at Mon Feb 12 09:04:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.