3 ms·
Both reasons are why I'm trying to develop an OSS alternative with easiness & platform-independence of the web but much lower system requirements than what elec
by cztomsik 7y ago
Both reasons are why I'm trying to develop an OSS alternative with easiness & platform-independence of the web but much lower system requirements than what electron has.
I'm currently close to prealpha, if you're interested.
https://github.com/cztomsik/graffiti/ https://github.com/cztomsik/graffiti/
- wccrawford 7y agoA friend and I were just wishing something like this existed. "pre-prealpha" is a bit too early for me, but I definitely wish you luck in this.
- jamesgeck0 7y agoUnder project scope, there's this statement: > To name just a few things you usually don't need: ... flawless i18n & accessibility Lack of basic accessibility support is (or should be) a complete nonstarter for any serious project.
- gmueckl 7y agoAlso, what is "flawless" i18n support?
- cztomsik 7y agoTo have what browsers do. And getting there would take few months on its own so it's not a priority right now.
- DonHopkins 7y agoI'd demand better than basic accessibility support! https://www.youtube.com/watch?v=GwSh0dAaqIA https://www.youtube.com/watch?v=GwSh0dAaqIA
- cztomsik 7y agoyou can join the effort and help me, the scope is limited to something I can do myself in reasonable time :-)
- Macha 7y agoThis is ultimately why I went with gtk in a recent Rust project. Qt bindings are a pain, and the license stuff was coming out. But most of the native Rust GUI libraries don't even try. Maybe its a maturity thing and they'll get there but I picked GTK for now
- mwcampbell 7y agoNote though that GTK has no accessibility support on Windows and Mac. If you're only targeting GNOME, then that's fine. For something that's more or less accessible cross-platform, I'd go with wxWidgets or something Web-based.