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: chris burdess <dog at bluezoo dot org>
- Cc: Stanley Brown <stanley dot brown at zimmer dot com>,java at gcc dot gnu dot org
- Date: Wed, 3 Dec 2003 14:53:34 +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>
On Nov 25, 2003, at 8:22 AM, chris burdess wrote:
frankly i think this is all a bit of a non sequitur. swt was designed
as
a replacement for awt, and its design goals are different. and just
using it as a bridge doesn't resolve the licensing issues regarding
linking to mfc/cocoa. if it's possible to resolve those issues, we
should write proper mfc and cocoa awt implementations.
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.
Regards
Bryce.