3 ms·
It's so terrible that we've been using it for more than 20 years for a 600kloc cross-platform digital audio workstation. It's so terrible that it's FLOSS-iness
by PaulDavisThe1st 3y ago
It's so terrible that we've been using it for more than 20 years for a 600kloc cross-platform digital audio workstation.
It's so terrible that it's FLOSS-iness encouraged us to fix problems with the macOS (then OS X) and windows aspects, and contribute them back (mostly) to the project.
It's so terrible that when I meet other developers we swap stories about their chosen cross-platform GUI toolkit, and things seem to pretty much even out.
- HexDecOctBin 3y agoGTK doesn't have accessibility on Windows and macOS, correct? Do you implement your own a11y? Because music as a profession seem to have a higher proportion of visually-impaired people, and I would have though that any DAW, etc. would make sure to cater to them to be competitive in the market.
- zogrodea 3y agoI think that was the case, but I remember hearing that GTK4 has made accessibility a priority and introduced some kind of system similar to what ARIA is on the web. Not sure if those accessibility plans were fully realised though.
- seabass-labrax 3y agoLooks like the accessibility features are really extensive now: https://docs.gtk.org/gtk4/iface.Accessible.html https://docs.gtk.org/gtk4/iface.Accessible.html Look at how many widget classes are listed in the 'implementations' subsection!