Since the mouse features were to easy to add and my Android vacation should take a bit longer, our OS X port was a good candidate to burn some hours I don’t have.<\/p>\n
What should work for OS X by now:<\/p>\n
<\/p>\n
The window positioning code was a torture, since the AWT components are not top-level on OS X. Hence we have to calculation the proper screen size position in bottom-left coordination space, even when resizing the window.
\nMaybe there are still some glitches in case of a NEWT child within an AWT floating Container, but most cases work fine.<\/p>\n
Shared or offscreen context destruction was another issue.
\nWe have to run this task on the MainThread, otherwise we experienced a ~10s freeze.<\/p>\n
Btw our MainThread semantics have been simplified a lot.
\nOn OS X, it just launches the user main class in a new thread while continuing as<\/i> the NSApp MainThread.
\nIn short, it is no more required when using an AWT enabled JVM, since it already launches as the NSApp MainThread.<\/p>\n
After a few more cleanups, I will prepare the next release and test our new native Jar loading mechanism
\nand Applets in general.<\/p>\n
But be aware that these features will be promoted to the next release RC4, Note on the side: Motivation for the OS X port was not my liking of the platform, which I don’t, but to just complete our platform independent solution. Hence having NEWT working well on OS X is mandatory here.<\/p>\n","protected":false},"excerpt":{"rendered":" Since the mouse features were to easy to add and my Android vacation should take a bit longer, our OS X port was a good candidate to burn some hours I don’t have. What should work for OS X by now: NEWT Top-Level Windowing NEWT Child Window w\/ NEWT Parent NEWT Child Window w\/ AWT… Continue reading Jogl OS X Port is Nigh \ud83d\ude42<\/span>
\nso you would need to wait or use the autobuilds, see Downloading the latest automatic build<\/a>.<\/p>\n