> And externals writtin in Java would be _real_ neat. Hmmm... sounds like a
> good use for Java.
Please, please, please don't even think about writing externals in Java.
The java VM takes up about 5Mb of RAM and takes too long to load (G3
300Mhz). The first (and possible all) call to an external would incur a
5-10 second delay at least. Also, Java's abilities are very limited while
still staying cross-platform, ie sound support is hopeless, playing CD-ROMS
is impossible, and drawing to another applications window, ugggh, forget it!
No, stick with C, C++, pascal, assembler anything (almost) but Java for
externals. The best option would be to not have externals at all though.
See, we shouldn't need them, we simply provide a way for them to be compiled
directly into the code (hey that's what OpenSource is all about). We simply
define a set of protocols for how to write code that implements a new
function in OC and let people go wild. That way we get more developers
improving OpenKard.
Adrian Sutton
**************************************************************
Email: [EMAIL PROTECTED] Ph: 3714 4649
I have been complimented many times and they always embarrass me;
I always feel that they have not said enough.
-- Mark Twain.
**************************************************************
