Thorsten Behrens wrote: > Hi Malte, > > you wrote: >> I think it's better to break AWT API compatibility once, instead of many >> times in many releases. >> > Which really also might turn out as "never" - the unlikeliness of > the big-bang-change to happen was already pointed out (since when > are we talking about awt redesign? I personally think it's >8 years > now).
If it doesn't happen, the pain to have them obviously is not big enough. If it hurts you that much, go on and make the change. The change basically would be to replace every setSomething() call by an attribute in that interface and to add the (in most cases) trivial implementation everywhere. All in all a few days of work for an experienced developer. In that case I would like to see some more from Carsten's suggestions for awt changes becoming implemented (as much as we can add without holding back the "add the get methods" task force). Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[email protected]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
