On Saturday 16 May 2009, 10:19, Mathias Bauer wrote: > > Is cleaning up Ariel's menu interface mess in awt incompatible? > > I don't know what he did, but "cleaning up a mess" sounds incompatible > by default. :-)
Carsten blogged about that http://blogs.sun.com/GullFOSS/entry/framework_team_and_community_contributions [ the issue he reffers to is wrong, it should be http://www.openoffice.org/issues/show_bug.cgi?id=96390 ] now I'm not sure if Carsten's idea was to show how easy it can be to contribute code to OOo, or how easy it is to mess OOo source code... anyway I'll clean up my own mess (once we're granted with the "perfect situation" I've talked about in http://wiki.services.openoffice.org/wiki/User:Arielch/Menu_API_Enhancement#New_Menu_API_.28and_its_design_problems.29) > We now live with some bad APIs for a lot of years. It didn't kill us and > the problems in our code base are not primarily caused by bad UNO APIs. IMHO you developers do not have the prespective of an API client, an extensions developer. If the bad API didn't kill OOo, it did and does hinder the interest of external developers willing to extend OOo functionality via add-ons. Just compare OOo's extensions with Firefox's or Kde's. Regards -- Ariel Constenla-Haile La Plata, Argentina --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
