-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
2.0
-
Cause Known
-
unknown
-
solaris_2.5
[sharonz]:
We need a way to "code" or group behavior across classes in the doc. Hans gives one example below, but there are others. We need a scheme to handle this properly.
From Hans [hmuller]:
Really need a way to let the read know that setUI, getUI, updateUI getUIClassID methods aren't important unless one is writing an app with mixed L&F or dynamic L&F, i.e. that supports changing the L&F on the fly. This applies to every JComponent subclass.
We need a way to "code" or group behavior across classes in the doc. Hans gives one example below, but there are others. We need a scheme to handle this properly.
From Hans [hmuller]:
Really need a way to let the read know that setUI, getUI, updateUI getUIClassID methods aren't important unless one is writing an app with mixed L&F or dynamic L&F, i.e. that supports changing the L&F on the fly. This applies to every JComponent subclass.