This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: SWT and AWT
- From: Bryce McKinlay <bryce at mckinlay dot net dot nz>
- To: Andrew Pinski <pinskia at physics dot uc dot edu>
- Cc: Stanley Brown <stanley dot brown at zimmer dot com>,java at gcc dot gnu dot org,chris burdess <dog at bluezoo dot org>
- Date: Thu, 4 Dec 2003 12:04:39 +1300
- Subject: Re: SWT and AWT
- References: <1069282815.24857.ezmlm@gcc.gnu.org> <3FBD04AD.9000302@zimmer.com> <16319.46864.165138.208549@cuddles.cambridge.redhat.com> <3FC222A5.9000104@zimmer.com> <20031124173307.GA12889@bluezoo.org> <3FC24D89.5050704@zimmer.com> <20031124192239.GA14282@bluezoo.org> <80FA174B-2533-11D8-A689-003065F97F7C@mckinlay.net.nz> <9E1D18CC-2534-11D8-8881-000393A6D2F2@physics.uc.edu>
On Dec 3, 2003, at 3:01 PM, Andrew Pinski wrote:
On Dec 2, 2003, at 17:53, Bryce McKinlay wrote:
There arn't any licensing issues with cocoa afaik, since its part of
the OS. In any case, cocoa and MFC are high-level APIs much like AWT
itself. Its probably better to use lower-level APIs to implement AWT,
both for efficiency and because its probably necessary in order to
implement AWT accurately. On Mac OS X, the right API would be
HIToolbox, which is an object orientated C API, somewhat similar to
GTK.
Note Cocoa is not build on top of HIToolBox at all.
Interesting. Do the two toolkits duplicate some functionality, or is
there another hidden API layer in there somewhere? Do you happen to
know what Apple's Java AWT/Swing implementations use?
Also if you build it on top of Cocoa, you can also build it on top of
GNUStep which is
the free version of OpenStep (like Cocoa but an older standard) and
there would be no need
to use GTK at all :).
Another problem with Cocoa however, would be using CNI and Objective C
in the same source file, right? At least until FSF GCC gets "Objective
C++".
Regards
Bryce.