Ok, fine. I'm starting the internal process. Will keep you notified.
Thanks,
Anton.
Roman Kennke wrote:
Hi Anton,
In the original javadoc comment you mentioned KeyboardFocusManager.initPeer(),
the method where the current toolkit is checked for being implementing
the KFMPeerProvider interface. As the javadoc for the interface (that becomes
a kind of internally public) is a specification, any mentioning of any
methods, classes etc. in the specification becomes a part of it.
Thus we're making the method KeyboardFocusManager.initPeer() a part of the
specification (and so we will have to support it in the future).
But as you can see this method is private and we're free to change it anytime.
Also I said that the developer anyway mustn't know where exactly his toolkit is
retrieved for a KFMPeer it provides. What the developer should do
is just to implement the KFMPeerProvider. Mentioning in the javadoc that
the KFM peer is retrieved _somewhere_ in the KFM would be enough, right?
Have I explained this clear now?
Ah ok. I thought you were speaking about something in the code. Yeah I
fully agree with your points.
Cheers, Roman
