This is the mail archive of the
java-patches@sources.redhat.com
mailing list for the Java project.
RE: Xlib AWT peers and Java 2D
- To: "'Rolf W. Rasmussen'" <rolfwr at ii dot uib dot no>, "java-patches at sources dot redhat dot com" <java-patches at sources dot redhat dot com>
- Subject: RE: Xlib AWT peers and Java 2D
- From: Anthony Green <green at cygnus dot com>
- Date: Sun, 8 Oct 2000 09:38:44 -0700
- Organization: Red Hat
- Reply-To: "green at cygnus dot com" <green at cygnus dot com>
On Saturday, October 07, 2000 2:05 PM, Rolf W. Rasmussen
[SMTP:rolfwr@ii.uib.no] wrote:
> I've been working a bit on merging in my X based AWT toolkit.
This is really cool. I'm building it right now.
> I'm a bit unsure whether the current package naming scheme is
> satisfactory.
Right - we need guidelines on how to use the gnu package. I think it's been
managed in an ad-hoc manner so far. I believe Warren and Tom have given this
some thought before, but I don't remember the details. Maybe they can
comment.
> The current patch will build the Xlib dependent code into a separate
> library named libgcjx.so. Is this a good idea? The alternative;
> making libgcj.so dependent on Xlib, seems like a poor solution.
Yes, that makes sense. Remember also that if you use the special naming
conventions the class loader will find code in .so files so users don't have
to link it in explicitly. For instance, if it's looking for Foo.Bar.Zing it
looks for Foo-Bar-Zing.so, then Foo-Bar.so, then Foo.so. I suppose this could
be a symlink to libgcjx.so.
I have given very little thought to swing, so I'll just wait and see what
Bryce and others have to say.
Thanks Rolf!
AG