On Jun 30, 2005, at 10:03 AM, Eric Christiansen wrote:
My company develops a cross platform C++/Java application, but they
have Mac specific code in places where it may not be needed. The
justification for some of this is that Mac Java components are not
implemented the same as Java on other platforms. This seems
believable since Apple has their own JVM. But is it true?
1) If an AWT component is heavyweight on Win XP, is it on the Mac
I'm sure others will give a more concise answer for you, but
I'll give it a shot.
Java defined the AWT when it was very early in age, so the
java code eventually calls some native code to draw its windows and
so on. This is controlled by the JVM. Heavyweights, while not exactly
the same on every system, do show the same characteristics of being
drawn by native code and not interacting well with pure java --
2) Is there a third in-between weight-ness on Mac? This is what my
cohorts say that prompted this e-mail. If true, what does this mean?
I know of no third class of windowing components. But to
comment on your pre-question ideas, pure java windowing components,
i.e. Swing, are designed to behave the same on all operating systems.
What they lack is a unified look-and-feel, and this is largely, if
not entirely, up to the programmer with that caveat that some LAFs
I hope this informs you.
Thought I'd ask the experts.
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden