Hello Christopher
Hi Anthony,
One more concern that comes to my mind is that the logic stated in the
Swing's method specification is going to be implemented on the AWT's side,
which I don't like much. So definitely we need more opinions on this
proposal.
This may be a stupid idea, so disregard it if it is :)
If the problem is having isValidateRoot() used by AWT code, why not promote:
public/protected boolean isValidateRoot()
to the Container class? It would obviously return false by default,
but if custom code wants to play with it (which is anyway unlikely to
happen) why not! After all, is there anything specially swingish with
this method?
This is a great idea and I like it!
I have been working on JDK 6 recently
and just forget that we can introduce new methods for JDK 7
:-)
The new method will fix all the mess
alexp
Cheers,
-Christopher
