- User Since
- Apr 15 2015, 5:07 PM (221 w, 5 d)
Sun, Jul 14
The resize should happen in the same steps as the config allows (and reads/writes), otherwise the UI will end up being confused, in particular the menu.
Wed, Jul 3
@filipf: Yep, sounds sensible :)
I've edited the proposal, taking some of the text from my 2017 proposal but mostly trying to do a fresh take. Please help me edit it further!
Tue, Jul 2
I've resisted patches like this for years now hoping someone would implement this properly in the Konsole KPart as part of the profile system where translucency is regulated, but no one did, so let's go with this.
Mon, Jun 24
Sun, Jun 23
This sounds good to me, although we'll need to handle some (literal) corner cases like having two panels at a right angle to each other without a sufficient gap to avoid the panel configurator UIs overlapping. And probably some similar space issue with "zll widgets visibly show their widget-specific options (remove, configure, rotate, resize, etc).".
Sat, Jun 22
You can do it for Dash, though -- check that isDash check where it already adds some runners to the Dash it doesn't add to App Menu.
Let's only do it for Kickoff and the Dash? The Kicker UI is really not made for arbitrary runners.
I'm not super happy with hardcoding directory separators and schemas, judicious use of QUrl::fromLocalFile or QUrl::fromUserInput would probably be better to norm behavior.
Ironically quite similar to a DDoS vector on the Task Manager. Apps suck :)
That's wrong, sorry - I'm uploading a different patch that fixes the underlying cause.
Fri, Jun 21
As the Task Manager maintainer I agree with @mart's take -- it's strange to have this (and have this be popular) as an option in the Task Manager but not a UI that serves a similar purpose, and also gets invoked from the TM.
I'm in principle quite OK with this minus that other patch I need to be written first to move DragHelper out into the lib (see other comment). Pitch: If you do that, it'll make it much easier to make the other menus (and other things) act similarly later, with smaller patches there.
Mon, Jun 17
Sun, Jun 16
Currently on airports, will do from the Plasma sprint :)
Jun 14 2019
Thanks for restoring my sanity & faith in panels, this annoyed me for weeks :)
The work Geon and I did in GSoC had an fcitc5 backend with plans to add a second one.
Jun 13 2019
In the hybrid approach, we can also get more ambitious than a widget list: System Settings could totally have a minimap version of your entire system that shows the screens with panels and a little config icon on each element that brings up the respective master dialog. The part shown in SysSe can get a little more free form if it doesn't have to show every widget.
I understand the motivation here, and it's worth entertaining as a thought experiment, but I think as-is it has problems.
Jun 12 2019
- Fix typo
Jun 11 2019
As the comment on Youtube points out the slides are not readable. Can you upload them somewhere and link here or in the video, so one can follow your talk better. I would also like to get an overview on current state on X11 in particular.
I submitted the same goal last year:
Jun 10 2019
Jun 6 2019
Jun 5 2019
Jun 3 2019
May 31 2019
I'm still a bit grumpy about this and dragging my feet! My gut still says it's both option clutter and UI noise :-)
May 27 2019
I'm not sold on this. "Display" fonts typically have spacing and metrics optimized for large sizes and use cases like signage. The FAQ entry quoted in the task you linked talks about Noto Sans UI. I'd like some more solid documentation on how Display relates to this "UI" cut or something from upstream.
May 24 2019
May 23 2019
I wouldn't call this implementation ready for frameworks, though - it just resets all the time, which is very slow as it forces views to destroy and recreate delegates instead of just updating them. A better implementation would just (re)filter source rows corresponding to the current page. This could be done as a subclass of QSortFilterProxyModel or custom; KItemModels' KRearrangeColumnsProxyModel can serve as inspiration to some degree. As it stands I wouldn't actually use this if it was in the framework.
It's not that easy I'm afraid.
May 13 2019
I'd say it's up to the Breeze maintainers. From my end I'm very interested in the app having a Breeze-compatible icon, because I'd like it to integrate well with KDE's workspaces and other apps. Review by the Breeze community is very appreciated to help with that. Application code needs to ship the icon anyway though for systems that don't have the theme and can't be reasonably expected to provide every app icon, so it's not vital to be included with the theme.
@trickyricky26 It's great! What do you think about adding the detailed SVG as 256 version?
May 6 2019
May 5 2019
Apr 30 2019
Looks great to me. Subtle visual refreshs like this are very appreciated, especially when they improve consistency, too.
Apr 26 2019
Apr 24 2019
Apr 22 2019
Apr 15 2019
Personally I'm not a big fan. I think the square OSD has more character and visual flair. The change proposed here looks rather cramped and removes some identity from the system.
Apr 14 2019
Apr 10 2019
Works here now, thx!
Apr 9 2019
I think it would be safer to Math.floor() rather than Math.round().