SWT on OS X now works, better

On Nov 10, 2008, at 7:13, Kevin Reid wrote:

> (For those that don't know, E+SWT+Mac OS X stopped working even as  
> well as it had with the introduction of Mac OS X 10.5 Leopard.) ...  
> If the main thread, that is the one which public static void  
> main(String[] args) is executed in, does not exit, then SWT  
> applications work. ... I suspect, even though keeping that thread  
> around is *sufficient*, that the *correct* solution is to use that  
> special thread as the SWTRunner's thread I will attempt to modify  
> the SWTRunner to implement this when I have time.

For now, I have committed the cheap fix: Rune.main now never exits.  
Since normal termination of an E JVM is by the Rune$Terminator causing  
System.exit(), this does no harm.

Also, due to changes by Apple, SWT apps on Leopard do not need to be  
wrapped in an application bundle; i.e. you can do rune myapp.e-swt and  
the GUI will function properly, just like for AWT/Swing apps.

Please test my fix, <svn://svn.synchrona.org/erights/e/trunk> revision  
513; particularly, let me know if it causes E to not exit properly in  
some situations, and whether there's any remaining brokenness in SWT  
on OS X or any other platform.

-- 
Kevin Reid                            <http://homepage.mac.com/kpreid/>