Discussion
Loading...

Post

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Emmanuele Bassi
@ebassi@mastodon.social  ·  activity timestamp 2 days ago
Emmanuele Bassi
@ebassi@mastodon.social  ·  activity timestamp 3 days ago

Time for plumbing a whole new accessibility setting from desktop to toolkit: 3 hours

Time for knowing what to plumb: 20 years

Time for bikeshedding on the type of the setting: Positive infinity

RE: https://mastodon.social/@ebassi/115429613083886645

Got nerdsniped around lunchtime yesterday, and ended up implementing a shared "reduced motion" setting for GNOME and the rest of the xdg stack:

- https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/9077
- https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/merge_requests/114
- https://github.com/flatpak/xdg-desktop-portal/discussions/1839
- https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/merge_requests/236
- https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/3253

#a11y #accessibility #gnome #gtk #xdg #portals

GitHub

Add a "reduced motion" preference to the settings portal · flatpak xdg-desktop-portal · Discussion #1839

Under GNOME we're currently abusing the boolean "enable animations" toggle, but this poorly maps to the actual accessibility issue of reduced motion. Ideally, we want to map to the same kind of set...
  • Copy link
  • Flag this post
  • Block
Emmanuele Bassi
@ebassi@mastodon.social replied  ·  activity timestamp 2 days ago

This kind of stuff is not hard, per se; some middling competence with C and time will get you far enough. The hard part is building enough cachet with the ecosystem to get you through the door; the considerably harder part is having enough time (and fireproof pants) to deal with the inevitable bikeshedding when it comes to sharing functionality across projects

  • Copy link
  • Flag this comment
  • Block
Emmanuele Bassi
@ebassi@mastodon.social replied  ·  activity timestamp 2 days ago

Having said that, there are plenty of similar changes that can be implemented across the stack by relative newcomers; the recommendation is to stay laser focused on a small enough scope, and avoid trying to generalise solutions, turning a fix into a rewrite of the world. That's a sure fire way to burn out, never finish anything, and build a reputation of an architecture astronaut that never amounts to anything except hot air on issue trackers

  • Copy link
  • Flag this comment
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About · Code of conduct · Privacy · Users · Instances
Bonfire social · 1.0.0-rc.3.21 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login