undefined | Better HN

0 pointsdilap8y ago0 comments

native in that it's not a web-app, sure, but it sure doesn't feel like a native citizen on the mac.

window can't be resized, standard menus are missing, standard keyboard shortcuts for text fields don't work, conversion text can't be selected, no way to cut or copy text (tho paste does seem to work).

is it implementing its own ui toolkit? qt maybe?

0 comments

flukus8y ago

Elsewhere they said opengl, which is why all that stuff doesn't work. You are correct though, it might be native code but it's not a native app.

amedvednikov8y 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.

dilapOP8y ago

cool, 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!

mwcampbell8y ago

Non-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.

1 more reply

j / k navigate · click thread line to collapse