https://bugs.kde.org/show_bug.cgi?id=399308
--- Comment #18 from avlas <jsar...@gmail.com> --- > plasma code quality and semantics must be at the highest degree always I agree and second that > So what can be done? > I propose different plasmoids: > 1. A plasma plasmoid for global menu (that already exists, and we just need > to maintain it) > 2. A plasma plasmoid for active window title that could provide some basic > options for its style and what it would show when there isnt an active window > 3. A plasma plasmoid for active window titlebar buttons. This is absolutely > possible as demonstrated at: https://bugs.kde.org/show_bug.cgi?id=399757 > 4. A plasma plasmoid separator e.g. a line. That could have some options in > its criteria when to show. I like and very much agree with the simplicity argument, it's in fact what I'm currently doing within a latte dock, using my active application plasmoid (https://github.com/kupiqu/plasma-active-application strongly derived from AWC) and the official global menu side by side, while AWC buttons appear on the opposite right corner only on maximized windows. However I see a cons, having two different plasmoids for name and menu will not be totally polished in my opinion. For instance, it won't resolve the latency in the appearing between the name and the menus. Note that it is not currently resolved for the appearing of the different menues in the official global menu plasmoid itself, but it could. Please see: https://bugs.kde.org/show_bug.cgi?id=398357 In the end that issue made me stop integrating the name and the menu within a single plasmoid, because until bug #398357 is not fixed, there is no much of a point. -- You are receiving this mail because: You are watching all bug changes.
