[316] in java-interest
Re: access to container or window
daemon@ATHENA.MIT.EDU (Clinton Combs)
Wed Jun 14 15:58:22 1995
From: ccombs%ucsdeva@ig1.att.att.com (Clinton Combs)
Date: Wed, 14 Jun 95 15:29:15 EDT
Original-From: ccombs@ucsdeva (Clinton Combs)
To: java-interest@java.sun.com
<AU> >
<AU> > A lot of the classes like List, TextField etc. need a container which can be
<AU> > a form or a window. where do I get this variable from inside my applet
<AU> > subclass ?
<AU>
<AU> If you want to make an applet, you are out of luck. If you want to
<AU> create your own separate Frame, then the container is the Frame.
<AU>
<AU> With Applets, you cannot embed native window items. This is a major
<AU> drawback of the current system, which is why it's being redone. It's
I've heard this 'redoing' of awt mentioned before, but no details
(or generalities) about how this is being reworked have been discussed.
Could someone please give us a hint as to what to expect? Can we
expect the same classes that we have now? What new features are
being planned? I'd like to see many of the features of the Stanford
InterViews 3.1 C++ library (its new name as part of X11R6 eludes me)
included in the 'new' awt (Glyphs, etc.).
Thanks,
Clint
<AU> also why Arthur whipped together the Embedded Component demo, and why
<AU> I picked it up and improved it to the point that it's more usable for
<AU> sophisticated applets.
<AU>
<AU> If you want a scrolling list in an applet, you must subclass
<AU> AppComponent and create a scrolling list. It wouldn't be that hard to
<AU> do. I am partially done implementing a full multi-line text widget as
<AU> an AppComponent, so that I can have real text inside my applets. It
<AU> works very well. A scrolling list is little more than static version
<AU> of a text widget.
<AU> -
<AU> Note to Sun employees: this is an EXTERNAL mailing list!
<AU> Info: send 'help' to java-interest-request@java.sun.com
<AU>
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com