Re: Cocoa, Java and C
Re: Cocoa, Java and C
- Subject: Re: Cocoa, Java and C
- From: mmalcolm crawford <email@hidden>
- Date: Wed, 2 May 2001 18:53:44 +0100
email@hidden wrote:
I can't speak to what Apple will do with the JRE, but technically
speaking,
there already is "complete support" for Java
Assuming you mean "complete support" for accessing Cocoa APIs from Java,
unfortunately this turns out not to be entirely true. Archiving in
particular seems broken under Java, at least if you're using NSCoder et
al.
There are also some "oddities" about the way some things work in Java,
such as nib loading and drawing (loadNibNamed is in NSApplication, not
NSBundle; NSGraphics provides the methods for drawing attributed
strings) -- although whether these seem odd may depend on your heritage,
but it may be confusing if you're looking at some of the older
documentation and trying to translate.
To pick up on one point:
Is there a recommended strategy for archiving mechanism?
NSCoder is clearly a useful "entry level" mechanism, but received wisdom
suggests that this may not be the best long-term industrial strength
strategy. Sketch uses property lists, which have the joint benefits of
(a) working with Java, and (b) providing the user with a hand-editable
textual representation of the data, but they can be a pain to create.
Any alternative suggestions?
mmalc.