[3859] in java-interest
Comments about AWT, etc.
daemon@ATHENA.MIT.EDU (Don Park)
Thu Nov 30 00:23:16 1995
Date: Wed, 29 Nov 1995 19:14:08 -0800 (PST)
To: java-interest@java.sun.com
From: donpark@telewise.com (Don Park)
To the Java team,
I would appreciate it if following features are added to Java class framework.
1. Attribute support in Object or Component class.
Attribute support consists of ability to get, set, and add attributes.
Beside the obvious uses for the feature, this could be the means to support
platform specific features like allowing Font objects to support 'underline'.
2. Memento support in Object or Component class.
Memento support allows other objects to efficiently associate information
with given object. For example, a view object can leave view specific
information with the model object so it can be streamed out.
3. Dirty region management.
I seriously think that requiring Java programmers to rely on
double-buffering to avoid flickers is silly. Web browsers are getting
slower and becoming resource hogs. Why add to the problem?
4. Changable Component Z-order and light views
I do not see a way to change the order of components without removing all
and then reinserting. Also, all the components are implemented using heavy
views. It would be nice to have light views (decorators and adorners would
be nice too).
5. Dynamic interfaces
Adding, removing, replacing, overriding interfaces of objects at runtime
would be very very nice indeed.
6. Dynamic UI for setting applet restriction level.
This allows applets to declare what they do and get permission from the user
via UI.
7. Protected storage for applets to store both temporary and persistant data
at client.
Applets should be able to store data of reasonable size at client machine.
This can be done by implmenting a protected file system within a file.
Garbage collection and usage policies can be deployed to prevent applets
from misbehaving.
That is all I can remember right now. I am not expecting any of this to be
implemented given the situation you guys are in (squeezed, pickled, and
stapled to the desk) but at least you guys have one more e-mail to forward
upstairs to ask for more resources :).
Sincerely,
Don Park
PS: Regarding the Panel.reshape bug, I see now that Netscape 2.0 Beta 3's
AWT.DLL has the fix. Thanks! You don't know how much I needed that for my
demo this Friday. Whew!
PSS: Looking at the source for AWT.DLL, it seems there are some rules native
class writers should be aware of. Could you share that with the rest of us?
Safety tips against attacks from above and below? Which threads should
create windows? Blah, blah.
PSSS: Tracing through four stacks of hierarchy (Components, Peers, MPeers,
and CObject-based) to find out what is going is making me sea sick, how do
you guys debug this thing? Secrets?
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com
