3 ms·
A "clean" UI is often a less functional or efficient UI; cleanliness is usually achieved by adding indirection or removing functionality. But Gtk3 isn't even cl
by barrkel 6y ago
A "clean" UI is often a less functional or efficient UI; cleanliness is usually achieved by adding indirection or removing functionality. But Gtk3 isn't even clean; it's often cluttered. Just look at the title bar on dconf-editor when you're 5 levels deep in a config tree.
Menus are ideal for commands which are individually infrequently used, but collectively frequently used. That is, where any given menu item isn't used often enough to warrant learning the keyboard shortcut (not that Gtk3 menus show shortcuts, because they don't), but the menu as a total is visited to execute a command frequently. Consider things like IDEs, photo manipulation, video editing, sound editing, basically anything with a lot of tools to apply.
I find it particularly ironic that Gimp - the OG Gtk - doesn't use a hamburger menu, because that would be ludicrous.
- p_l 6y agoAnother point with menus is that the typical top-of-the screen, and nowadays "hamburger" menu is just dumping ground for all functionality, and should be at most of a secondary use to common and context-specific actions represented by buttons/context menus/etc. Something usually lost in "clean" UIs...