Opened 4 years ago
Last modified 4 years ago
#16465 new enhancement
[InterfaceKit] Implement truncation prioritising
| Reported by: | bitigchi | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Kits/Interface Kit | Version: | R1/beta2 |
| Keywords: | ui | Cc: | |
| Blocked By: | #16464 | Blocking: | |
| Platform: | All |
Description
Whilst truncating toolbar items, a priority system is needed to decide which item is gonna be shown. For instance, a WebPositive window should leave the address bar and the back button to the last, while truncating (possible) extension buttons first.
While coding, a ”.priority(0)” can be added by default, “0” can be changed according to the priority level (higher the number less the priority).
Change History (2)
comment:1 by , 4 years ago
comment:2 by , 4 years ago
AppKit (macOS) does this. For instance, I usually have gazillion Safari windows open at the same time, and I mostly keep them at the smallest size possible, leaving only content visible (thanks to responsive design). Safari first gets rid of extension buttons, then share, downloads etc. only leaving address bar, navigation buttons and sidebar switch.
Mail also does this as well.
In addition to that, maybe some toolbar items can be marked as ".nonHideable()", keeping them visible at any window size.
Toolbars usually have semantic meaning in the order of buttons, so I don't think this is such a good idea. If no other toolkits do this, I'd say we shouldn't either.