<AWT Dev> RFC: KeyboardFocusManager patch
roman.kennke at aicas.com
Wed Jul 18 02:14:56 PDT 2007
> 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.
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
More information about the awt-dev