On Mon, May 11, 2009 at 10:56 AM, Mathias Bauer <[email protected]> wrote: > > For the time being we had to keep "OnLoad" for compatibility reasons > (both for registering as well as for sending), but the documentation > would be changed to suggest "OnOpen" instead. This can be changed (and > perhaps will be changed) in the first release that allows for > incompatible API changes (I assume this will be 4.0). > > Alternatively, we can stay with "OnLoad" until the incompatible change > and then switch to "OnOpen" without any intermediate compatibility > arrangements. > > Comments, anyone?
That you even consider removing this event is exactly the lack of commitment to compatibility I have critized in the long thread about OOo quality recently. There is ONLY ONE acceptable solution for changing the name. - introduce the new event name - keep the old event name for compatibility FOR ALL ETERNITY. It is NOT acceptable to retire it with OOo 4.0! NOT acceptable to retire it with OOo 5.0. People build their businesses on OOo. Your petty interests in language aesthetics are irrelevant! If you are worried about the overhead of sending the same event twice, well, there's also this option: - Live with the bad name, compensate it with good documentation and then find something more productive to waste your time on than breaking existing code. Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
