[MGNLUI-3585] Action bar is not well structured when there are many actions Created: 30/Apr/15 Updated: 11/Mar/21 Resolved: 11/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | actionbar |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Andreas Weder | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 2 |
| Labels: | blocked, feature-work, mh5371, overwhelms-me, pain-point, team-priority, ux | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 4d 1h | ||
| Original Estimate: | 3d | ||
| Attachments: |
|
||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||
| 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: | |||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||
| Description |
|
We already have large sets of actions in some Action bars. The design concept behind Action bars actually also asks for sections, not only groups (we already group actions). Sections bundle related actions under a title and can be opened and closed. The design ideas behind sections are:
Having a clear distinction between the primary and other sections requires developers and designers to decide on the core set of actions they want to offer in any given app or sub app. It also helps in keeping a low UI complexity in cases there's not a lot of space for showing actions. As for the current state of implementation, we already do have limited support for sections. We can configure them, but not open and close them. In addition, action availability is not aware of sections. |
| Comments |
| Comment by Mikaël Geljić [ 29/Jan/16 ] |
|
Summarizing a few points after PoC review:
|
| Comment by Sang Ngo Huu [ 18/Feb/16 ] |
|
Problem when implementing this ticket:
My conclusion: |
| Comment by Mikaël Geljić [ 29/Mar/16 ] |
|
Let's get another opinion on a high-level first:
Worth re-iterating that these changes should have no effect right now, until we start applying a new section scheme, starting in pages app (ticket to follow). Apart from that, widget changes seem to be pretty ok. I won't mention ctors/deprecations yet; this we can still decide and do last. |
| Comment by Aleksandr Pchelintcev [ 01/Apr/16 ] |
|
After looking at it - I must say I like the approach chosen, it would allow us to update the apps to the new schema one by one. |
| Comment by Mikaël Geljić [ 10/May/16 ] |
|
As part of specifying the guidelines for content apps, we took another look with weder, and re-visited some of the points from before:
Re: configuration & multi-selection, we don't want to multiply configuration, so we'll have to find options (decorating the action bar main title dynamically?). |