The lingo that’s used around java will all the abbreviations is certainly a pain.

When this is finished, we should be able to run JBoss (we may already be able to… I suppose I should try it again here.)

And you’ll most certainly be able to write a program that looks like BeOS, take the compiled set of .class files and run them MacOS X with it looking like an OS X program.

The AWT (abstract windowing toolkit) is actually native BeOS components, just as they’re real Win32 components on Windows and use Motif on X11. In MacOS, they’re even using native Carbon (maybe even Cocoa now).

As for Swing based apps (a different toolkit, far more flexible, and much better imho) we plan to make a BeOS R5 (and probably Haiku R1) Look and Feel, which should emulate the BeOS appearance very well. We’ll get to that / more on that later.

FinnB – It’s far from all ‘my’ progress. There’s others working on this too! But from all of us, thanks for the compliments!

I am amazed by your progress. I am a free-time (and quite lame…) BeOS coder, just learning Java in my spare-time, and I am very happy about your progress. I don’t know how “my Java future” will be and thus, how imortant Java on BeOS will become for me, but your work is very important for the future of our beloved system :-)

Thanks to you and Andrew,
Finn

I am not 100% clued into Java – the hundereds of different project names, versions and types of Java products (Beans/EJB’s) get me seriously confused, but how does this help getting things like JBoss running on BeOS?

When this is finished, will I be able to write a program in Java on BeOS that looks like a BeOS program, then run the program on OS X, and have it look like an OS X program?