Kimberley Burchett wrote:
> I have a few questions before I volunteer to help with the AWT:
Thanks for writing!
> - What is the point of the peer architecture? If each peer has a
> non-peer counterpart, why not do everything directly in the non-peer?
> (I've been wondering the answer to this question ever since I first
> learned the AWT)
The awt design wasn't the world's greatest. The main reason for peers is
that was the way it was designed by Sun.
> - Since a regular Java app only new's the non-peer classes, and you
> haven't started on them yet, how do you know the peers are working
> at all? Do you have test progs that new the peers directly,
> bypassing the non-peers?
I believe the GTK+ peers Paul and Jim are working on work with the JDK, thus
they can be tested with the JDK. I'm still waiting for a HotJava screenshot
with our supercool Classpath mascot on it.
> - I don't have a Windows or Solaris box at home, so I can't run the
> JDK (as far as I know). I assume this would make it difficult to
> compare the behavior of a program under the JDK vs Classpath.
This is both good and bad. The JDK is terribly buggy. We don't want to
emulate that behavior. We should conform to specs. (Paul converted me on
this one). What kind of machine do you have? There are JDK ports to Linux
and FreeBSD and almost everything else I think.
--
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/
