4 ms·
These are valid observations. Right now the focus is on features and performance, but the app is going to be polished before the 1.0 release to have a more nat
by amedvednikov 9y ago
These are valid observations.
Right now the focus is on features and performance, but the app is going to be polished before the 1.0 release to have a more native feel: native notifications, shortcuts, textfields, etc.
- dilap 9y agocool, good to hear. with enough dedication and an eye for ui detail, i believe it is possible to make a custom-widget app feel like a good citizen -- the unity editor is a good example of this, imo. it's a ton of work tho! (actually, i'm not sure if it's possible to make your app friendly to screen readers w/o using native widgets. maybe?) if you do pull it off, you'll end up with a great ui toolkit for go. that would be a very interesting thing!
- mwcampbell 9y agoNon-native widgets can certainly be accessible with screen readers and other assistive technologies. But it's a lot of work. You'll need to implement the UI Automation provider API for Windows, AT-SPI for desktop Linux, and the Cocoa accessibility API for Mac. And you probably won't get any of them right the first time. So I think it would have been better not to create a custom toolkit.
- dilap 9y agoIt's a huge task, sure, but someone needs to take on huge tasks from time to time (and Go does not currently have any good UI toolkit story). :-)