This is the mail archive of the
java-patches@sources.redhat.com
mailing list for the Java project.
Re: Merging in more AWT stuff
- To: Bryce McKinlay <bryce at albatross dot co dot nz>,"green at cygnus dot com" <green at cygnus dot com>
- Subject: Re: Merging in more AWT stuff
- From: "Rolf W. Rasmussen" <rolfwr at ii dot uib dot no>
- Date: Tue, 15 Aug 2000 18:29:06 +0200
- Cc: "java-patches at sourceware dot cygnus dot com" <java-patches at sourceware dot cygnus dot com>
- References: <01C00573.F4B73840.green@cygnus.com> <399787B8.34526F3B@albatross.co.nz>
On Mon, Aug 14, 2000 at 05:46:32PM +1200, Bryce McKinlay wrote:
> Anthony Green wrote:
> > Yes - this is cool. Are you going to check your toolkit in?
[Responding to Anthony's original message:]
Sure, if there is a consensus for allowing it in. However, there are
some dependencies that need to be resolved before the code can go in,
see <URL:http://www.ii.uib.no/~rolfwr/jcnix/dependencies.html>. The
actual toolkit package is "no.rwr.awt.x". See
<URL:http://www.ii.uib.no/~rolfwr/jcnix/packages.html> for descriptions
of each package. The packages need to be renamed to something more
suitable before going into the libgcj tree. Bryce has suggested
"gnu.java.awt.peer.xlib" for the main toolkit package.
Some work is needed to resolve some of the dependencies. Linking to
libjpeg should be made optional. I'm working towards creating a
"plugin" mechanism for image decoders to make this possible.
The "no.rwr.image" package contains a rendering framework that is
is used by for efficient image manipulation. This framework currently
has some annoying limitations, and needs to be redesigned. I'm
expecting that I'll get a better idea of what is needed during the
design of the Java2D rendering pipeline (see
<URL:http://www.ii.uib.no/~rolfwr/pipeline.html> for some preliminary
notes.)
If there is an interest in getting the X toolkit in as soon as
possible, it should be easy to replaces the dependencies with
temporary stubs.
> > It would be
> > nice to configure --with-toolkit=Xlib or --with-toolkit=gtk, or something
> > like that.
>
> I like "--enable-java-awt=gtk,xlib" or maybe "--enable-java-awt-toolkit" for
> consistency with the existing gcc configure options. We should also add some
> configury to check for gtk/xlib and enable them automatically if present.
Either way, I think it's important that multiple toolkits can be
configured and compiled in at the same time. Actually, I'd like to see
it being possible run several different toolkits concurrently.
--
Rolf W. Rasmussen