On Thu, May 28, 2009 at 9:53 AM, Matthias B. <[email protected]> wrote:
Hi, > If you absolutely want to break the events API, then do it properly > and do away with the use of plain strings as event identifiers and > replace them with constants/enums. I agree here with you. I dislike magic constants in the code. We can say that "OnLoad" is magic constant too. But, if your extension code really has 90.000 lines, it's designer / programmer fault too. And in a huge extension like your one, I'd expect your own constants with "OnLoad", ... values. You can't expect that API will never change. Everything is under evolution (slow or fast). > a) that an extension is actively being developed. Well, there are > extensions that are finished, with a complete feature set and no > remaining bugs and whose developers have moved on to other projects or > left the company. Or a company may have decided to cease selling an > extension because the profit margin is too thin. Or.... I'm sorry, but you can't expect, that your extension will automatically work with new major versions. Nice example is Firefox, where lot of extensions doesn't work with new major version. Many more examples exist ... > b) that the extension is free (in whatever sense). If it isn't, then > "just a recompile" translates to "users are forced to purchase updates > just to keep using the extension" No one is forced, you can stay with old OO.o. Otherwise welcome to commercial world. Company can offer free update if this is just about recompilation. It's about their business policy, not about OO.o API. > versions of more than 1 complex and work-critical component at the > same time. So telling them "you have to up the extension version at > the same time you deploy the new OOo version" doesn't go over well and > they come complaining to us for not making our extension compatible > with new OOo versions. I'm sorry, but if you update OO.o, you have to test all your extensions and you can prepare convenient package to deploy OO.o with your extension. > my notion of "soon enough" which again will diverge from my customer's > notion of "soon enough". Everything is about CWS. You can check CWS Features mailing list, which should be read by every extension developer. You can read all specifications here, proposed changes, etc. -- Robert Vojta --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
