[317] in java-interest
Re: access to container or window
daemon@ATHENA.MIT.EDU (milor001@maroon.tc.umn.edu)
Wed Jun 14 16:16:56 1995
From: milor001@maroon.tc.umn.edu
To: ccombs%ucsdeva@ig1.att.att.com (Clinton Combs)
Date: Wed, 14 Jun 1995 14:53:43 -0500 (CDT)
Cc: java-interest@java.sun.com
In-Reply-To: <9506141929.AA12781@ucsdeva> from "Clinton Combs" at Jun 14, 95 03:29:15 pm
>
>
> <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.).
This would be Fresco. It is not really a "all new" InterViews but is
build by some of the same people and borrows ideas from it. It is suppose to
be designed to be implemented in many different OO languages. I wonder if
what Fresco is trying to do would be easier to do in Java.... Hmmmm.
==============================================================================
R. Alexander Milowski milor001@maroon.tc.umn.edu
Copernican Solutions Incorporated (612) 825 - 4132
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
