Originally posted by kaprikawn
View Post
Announcement
Collapse
No announcement yet.
The CSD Initiative Is Pushing For Apps To Abandon Title Bars In Favor Of Header Bars
Collapse
X
-
-
Originally posted by nll_aIf they want devs to jump into their bandwagon, then they should start by making a CSD switch in their applications so that they are optional and can be turned off by other desktop environments and the people who hate them.Last edited by pal666; 27 January 2018, 02:50 PM.
- Likes 1
Comment
-
Originally posted by kaprikawn View PostPersonally I like Gnome, I like that there's a company that puts out software that doesn't feel like it's designed by committee.
Last edited by pal666; 27 January 2018, 03:15 PM.
- Likes 2
Comment
-
Originally posted by deve View PostCSD is idiotic. How should I know if user prefers dark/bright theme, small/large buttons, needs high contrast etc...
or idiots need high contrast for titlebar only, because idiots only use titlebars and ignore window content?
Comment
-
Originally posted by Gusar View PostThey may be trying to shape a better user experience, but there's no consensus that they're actually succeeding. I do not think headerbars are a better user experience, and going by the comments in this thread, I am far from alone in that thinking. That's the issue in your argumentation, you're equating "different" with "better". But something being different does not automatically make it better
Comment
-
Originally posted by M@yeulC View PostDWD - dynamic window decorations, where an application politely asks the SSD compositor if it can draw some widgets in their title bar. Originally proposed for KDE, but looks like it is on the back burner for now.
This WM-drawn design akin to KStatusNotifierItem/libappindicator is intended to allow any number of heterogeneously-rendered copies of the DWD widgets to exist simultaneously so it's possible to do things like exporting copies of them to a paired smartphone app with a more touch-appropriate visual representation or auto-publishing them through a D-Bus API à la AppleScript.
Comment
-
Originally posted by pal666 View Postcsd vs ssd is technical matter, invisible to people, and people who hate them are uninformed idiots. now talking about developers, csd do not make your app look "alien" because csd only affects 1% of your app with other 99% unaffected. so sane developer would be concerned more about 99% of app alien to desktop and to now this 1% of ssd. and sane devs long ago found solution for this issue, it is called "themes". so with csd you have to employ theming to draw not just 99% of app, but to draw app as a whole. and if you can't do that, then maybe you should wipe floors instead of software development. there is a reason why real developers behind gnome and weston use csd: it does not require additional step of composing app with csd, which can be suboptimal
(It's for that reason that I was surprised when I discovered Weston was CSD-based. Given the Wayland focus on security and keeping users in control of their desktop, it seems odd that they'd allow potentially malicious applications so much freedom to meddle with the most intuitive workflow for moving and closing windows.)
Among other reasons, that is why I intend to move to KWin as my compositor once it provides a mature alternative to running X11 on top of the nVidia binary drivers. (I'll just replace any applications which don't obey a "Hide your CSD. I'm drawing SSD whether you like it or not." order from it.)
- Likes 1
Comment
-
Originally posted by boudewijnrempt View Post
Not from what I can remember from the KDAB offices in Berlin; there was no drugs, but neither were there suits. It was an amazing, laid-back place for people who really liked hacking, though. Damn, this has made me all nostalgic for KOffice/Calligra sprints in Berlin!
Comment
-
Originally posted by ssokolow View Post
Not quite. It politely asks the WM to draw some widgets in its titlebar. Aside from "Visible. Hide the corresponding internal widgets" vs. "No room. Show the corresponding internal widgets", it has no idea where they're actually getting drawn.
This WM-drawn design akin to KStatusNotifierItem/libappindicator is intended to allow any number of heterogeneously-rendered copies of the DWD widgets to exist simultaneously so it's possible to do things like exporting copies of them to a paired smartphone app with a more touch-appropriate visual representation or auto-publishing them through a D-Bus API à la AppleScript.
And yes, you are right about the later part, it could be used for fun (albeit of doubtful usefulness) things such as publishing those actions to the touchbar on Mac or KDEconnect on phones :P
Anyway, I created #dwd_discussion on freenode to try to gather some people to discuss this with.
Comment
Comment