<AWT Dev> java.awt.peer work

[Roman Kennke]

Hi there,

as part of the OpenJDK challenge project 'portable GUI backends', I'd
like to put some love to the interfaces in java.awt.peer. Several tasks
spring to mind:

- Add documentation all around.
- Remove depracted (dupe) methods, and use the new ones instead. [1]
- Remove unused stuff.

[1] This is really a little weird. There are new methods (for example,
getPreferredSize() instead of preferredSize()), but the old methods are
used everywhere, so the new ones could just as well be removed. OTOH, I
feel that the new ones should be used and the old ones removed. Having
both in the interface doesn't help anybody, not for backwards
compatibility and not for developing new peers.

I know that java.awt.peer is a little special, as it is in the public
namespace but not publicly documented. What are the constraints on
changing these interfaces and docs? If it's not feasible anyway, I
probably better don't touch it at all. What is your optinion?

/Roman

-- 
Dipl.-Inform. (FH) Roman Kennke, Software Engineer, http://kennke.org
aicas Allerton Interworks Computer Automated Systems GmbH
Haid-und-Neu-Straße 18 * D-76131 Karlsruhe * Germany
http://www.aicas.com   * Tel: +49-721-663 968-0
USt-Id: DE216375633, Handelsregister HRB 109481, AG Karlsruhe
Geschäftsführer: Dr. James J. Hunt