Swing still has four heavyweight containers. These must have native
peers. They must.
At some point, there must be a window that has a corresponding native
platform window (Motif, Windows, whatever).
There must be some native window that can be displayed by the native
platform. Usually this is the top-level container that contains the
rest of your GUI.
I don't intend the following to be a shameless plug :-) but my
recently released book covers all these concepts in the context of
structuring your apps.
"Java GUI Development"
Vartan Piroumian
Sams
ISBN 0-672-31546-7
Vartan
berry writes:
>
>
> > > Another question:
> > >
> > > With Swing classes, at what point is native code actually
> > > called to do drwing . If you could tell me, I am wondering what classes
> it
> > > happens in and what is specifically happening. In 1.1 it would be
> > > the peer classes.
> >
> > I know that one : )
> > swing uses
> > Canvas
> > Frame
> > Dialog
> > Window
> > The native peers are called there.
> >
>
> I thought that the whole point of swing was that there were not any peers.
>
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
