Re:My Golang UI package: lessons learned about threading and...
by andlabs on Monday June 30, 2014 @12:41AM
(#7963726)
Note: since writing that article I have now started, and am now mostly finished with, this rewrite, having only one last ink to work on... dialog boxes. This was always a big disaster ecause every OS has a wildly different model, and now I'm sitting on a Stack Overflow question related to Cocoa thinking if I should just force all dialogs to be application modal but then need a way to make them always on top on all platforms...
[ Parent
| on HN ]
Re:My Golang UI package: lessons learned about threading and...
by shaunxcode on Monday June 30, 2014 @12:54AM
(#7963748)
I am curious to know if you spent any time studying the eXene (http://alleystoughton.us/eXene/future.pdf) approach? I ask because it is the an ML CSP informed UI toolkit. If so how would you contrast that with your current (new api) approach?
Re:My Golang UI package: lessons learned about threading and...
by dimsuz on Monday June 30, 2014 @04:25AM
(#7964195)
Interesting project. Looks like it's somewhat stalled, do you know anything about its current state/plans?
Re:My Golang UI package: lessons learned about threading and...
by grey-area on Monday June 30, 2014 @04:10AM
(#7964162)
Have you looked at setLevel on NSWindow?
[dialog setLevel:NSStatusWindowLevel];
It's probably not a viable solution long-term because users will expect more Mac OS X-like behaviour and non-modal dialogs, but it would help you do what you want I think.