<AWT Dev> java.awt.peer work

[Oleg Sukhodolsky]

Hi Roman,

Roman Kennke wrote:
> 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?

java.awt.peer is really special place.  Some people believes that peers 
are not part of public API and so we can change them as we want.  Others 
consider them as part of (semi)public interface and prefer to see 
special request for any API change in this area.

I'm from the first camp, so I believe that it is ok to remove all 
deprecated methods from these peers.  But I expect that we have some 
people from the second camp.  So, I'd suggest to wait couple days for 
their response (no response means they are ok ;)

Regards, Oleg.
> 
> /Roman
>