I mean, I used Cinnamon on my main machine, and GNOME everywhere else. It wasn't until later in the KDE 5 lifecycle that I felt KDE was going in the right direction - and then soared right past GNOME.
I quickly understood that they hate us right back in early 2011 when they pulled the carpet out from under all the users of Gnome 2,
and then I fully understood exactly how much they hate us over the course of the following couple years where I had to completely rewrite from scratch my custom GTK theme many times, hours of my time wasted in the most painful possible way, because they were constantly breaking themes.
I always knew something like Libadwaita was coming.
also not to mention the snarky jerk comments from gnome devs on gitlab pages that pop up all over internet searches about GTK usability issues or mal-features
@thomholwerda BTW, found this new gem via the Phoronix forum: #KDE dev arguing with #GNOME folks about their arrogant icons handling which is breaking on other desktops:
GNOME: »Icon themes are not a very prominent feature in current app development […]« LMAO
KDE: »If this breaks GNOME, it's because you folks chose to repurpose an FDO icon theme to be something it wasn't designed to be which breaks its non-GNOME consumers.«
Phoronix: KDE Readies More Changes For Next Month's Plasma 6.1
KDE developers have been busy the first few days of May with all eyes shifting to the upcoming Plasma 6.1 desktop...
https://www.phoronix.com/news/KDE-Starts-May-2024
I agree so much with skeevy420's and cakeisamadeupdrug's comments on usability. That especially hits home for me.
Maintaining my own custom GTK theme for years, even enduring the gnome people's best attempts to make me give up by breaking the CSS over and over and over every point release, isn't something I did for fun.
I did it because I have ASD and severe sensory issues. Having my choice of colours is a NEED for me
Dear #Fediverse
We are funding accessibility infrastructure on Linux :linux:
We are focusing on issues and regressions related to Wayland and Flatpak :wayland: :flatpak:
Please share your feedback and ideas, even if you're not sure if it's in s…
Hi, I have sensory issues and having a dark mode with user interface controls tinted dark red makes much much more comfortable for me to use my computer.
Currently, I have had to maintain my own GTK theme to make this possible, hours of very painful work over the years just to have a tolerable user experience for me.
I think having the ability to change the UI colours is an essential accessibility feature.
See Windows High Contrast Mode, or its Web counterpart forced-colors (usable outside Windows in Firefox color settings). I rely on the latter when I have an overstimulation flareup: it lets me override all colors on all websites with my own palette. Websites and Windows apps should avoid any hard reliance on a color palette to convey meaning for this reason, and instead rely on borders and foreground contents.
(The name “high contrast mode” is a misnomer, as users can specify any palette of any contrast level).
The forced-colors CSS media feature is used to detect if the user agent has enabled a forced colors mode where it enforces a user-chosen limited color palette on the page. An example of a forced colors mode is Windows High Contrast mode.
For prior work on other OSes, I'm not really sure what to suggest, but windows (afaik) has a high contrast accessibly mode with configurable colours, GTK2 allowed the user to set colours, Tcl/Tk allows the user to set the default colours for both the classic widgets and the Ttk widgets (I wrote the patch for Ttk allowing that), Qt allows you to set colours.... Etc
Maxi 9x 💉
in reply to Thom :linux: :a_openbsd: • • •Thom :linux: :a_openbsd:
in reply to Maxi 9x 💉 • • •Thom :linux: :a_openbsd:
in reply to Thom :linux: :a_openbsd: • • •dusthillresident
in reply to Thom :linux: :a_openbsd: • • •I quickly understood that they hate us right back in early 2011 when they pulled the carpet out from under all the users of Gnome 2,
and then I fully understood exactly how much they hate us over the course of the following couple years where I had to completely rewrite from scratch my custom GTK theme many times, hours of my time wasted in the most painful possible way, because they were constantly breaking themes.
I always knew something like Libadwaita was coming.
dusthillresident
in reply to dusthillresident • • •Maxi 9x 💉
in reply to dusthillresident • • •@thomholwerda BTW, found this new gem via the Phoronix forum: #KDE dev arguing with #GNOME folks about their arrogant icons handling which is breaking on other desktops:
GNOME: »Icon themes are not a very prominent feature in current app development […]«
LMAO
KDE: »If this breaks GNOME, it's because you folks chose to repurpose an FDO icon theme to be something it wasn't designed to be which breaks its non-GNOME consumers.«
https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/issues/288
Symbolic icons only have the `-symbolic` suffix, breaking compatibility with FDO-compatible apps (#288) · Issues · GNOME / adwaita-icon-theme · GitLab
GitLabMaxi 9x 💉
in reply to Maxi 9x 💉 • • •KDE Readies More Changes For Next Month's Plasma 6.1 - Phoronix Forums
Phoronix Forumsdusthillresident
in reply to Maxi 9x 💉 • • •I agree so much with skeevy420's and cakeisamadeupdrug's comments on usability. That especially hits home for me.
Maintaining my own custom GTK theme for years, even enduring the gnome people's best attempts to make me give up by breaking the CSS over and over and over every point release, isn't something I did for fun.
I did it because I have ASD and severe sensory issues. Having my choice of colours is a NEED for me
matzipan
in reply to dusthillresident • • •Sonny (@sonny@floss.social)
FLOSS.socialdusthillresident
in reply to matzipan • • •Ahh, then I'll forward my feedback.
#linux #accessibility
@sonny
Hi, I have sensory issues and having a dark mode with user interface controls tinted dark red makes much much more comfortable for me to use my computer.
Currently, I have had to maintain my own GTK theme to make this possible, hours of very painful work over the years just to have a tolerable user experience for me.
I think having the ability to change the UI colours is an essential accessibility feature.
Sonny
in reply to dusthillresident • • •@dusthillperson @matzipan
Hello, not having a freedesktop API for this makes it difficult indeed.
Could you link to literature regarding sensory issues and perhaps prior work in other OSes?
Seirdy
in reply to Sonny • • •See Windows High Contrast Mode, or its Web counterpart forced-colors (usable outside Windows in Firefox color settings). I rely on the latter when I have an overstimulation flareup: it lets me override all colors on all websites with my own palette. Websites and Windows apps should avoid any hard reliance on a color palette to convey meaning for this reason, and instead rely on borders and foreground contents.
(The name “high contrast mode” is a misnomer, as users can specify any palette of any contrast level).
forced-colors - CSS: Cascading Style Sheets | MDN
MDN Web Docsdusthillresident
in reply to Sonny • • •@sonny @matzipan
https://www.theraspecs.com/blog/light-sensitivity-autism/
https://autism.org.uk/advice-and-guidance/topics/sensory-differences/sensory-differences/all-audiences
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9748440/
For prior work on other OSes, I'm not really sure what to suggest, but windows (afaik) has a high contrast accessibly mode with configurable colours, GTK2 allowed the user to set colours, Tcl/Tk allows the user to set the default colours for both the classic widgets and the Ttk widgets (I wrote the patch for Ttk allowing that), Qt allows you to set colours.... Etc
Sensory differences - a guide for all audiences
autism.org.uk