Re: Incompatible change for extensions

2013-07-31 Thread Mathias Röllig
Hi! I must correct myself: I wrote But: It doesn't work for com.sun.star.frame.StartModule With an other extension I saw, it works! So I searched for the problem. For the first try to edit the Addons.xcu I have made a mistake and I inserted the new prop Title ... not at the right place.

Re: Incompatible change for extensions

2013-07-30 Thread Mathias Röllig
Hello! Now I'm trying AOO 4.0 and have to work over my extensions. First: Thank you for the change! But: It doesn't work for com.sun.star.frame.StartModule (Should I file a separate issue or comment bug 121577?) Second: As stated in https://issues.apache.org/ooo/show_bug.cgi?id=121577#c2

Re: Incompatible change for extensions

2013-02-04 Thread Oliver Brinzing
Hi What do you think how much effort it would be to create a new scheme for the new extended toolbars and keep the old one at least for a while? +1 due to api changes (e.g. toolsbars, com.sun.star.awt.XMessageBox, ...) i cannot run my oo32 extension with aoo 3.5 at the moment. so testing is

Re: Incompatible change for extensions

2013-01-23 Thread Bernard Marcelly
Hi Ariel and all, Bug 121582 is very vague and does not detail the proposed changes. It looks like an intended obfuscation, so that nobody will react in time. The XSimpleFileAccess is indicated as merely an example, but I will develop on it. If bug 121582 proposes for Apache OpenOffice 4.0

Re: Incompatible change for extensions

2013-01-23 Thread Jürgen Schmidt
On 1/23/13 9:36 AM, Bernard Marcelly wrote: Hi Ariel and all, Bug 121582 is very vague and does not detail the proposed changes. It looks like an intended obfuscation, so that nobody will react in time. The XSimpleFileAccess is indicated as merely an example, but I will develop on it. If

Re: Incompatible change for extensions

2013-01-23 Thread Bernard Marcelly
Message de Jürgen Schmidt date 2013-01-23 10:12 : exactly and that means a minor code change and a rebuild. If this kind of cleanup changes are not allowed with a major release than we do something wrong. You should not forget the benefit for new developers that we want to reach. A cleaner and

Re: Incompatible change for extensions

2013-01-23 Thread Jürgen Schmidt
On 1/23/13 3:08 PM, Bernard Marcelly wrote: Message de Jürgen Schmidt date 2013-01-23 10:12 : exactly and that means a minor code change and a rebuild. If this kind of cleanup changes are not allowed with a major release than we do something wrong. You should not forget the benefit for new

Re: Incompatible change for extensions

2013-01-22 Thread Ariel Constenla-Haile
Hi *, Replaying in general to the thread, that is based mainly on bug 121577. The discussion about incompatibility, centered on this bug, is meaningless: bug https://issues.apache.org/ooo/show_bug.cgi?id=121582 is the real code-incompatible change, every extension developer will have to check

Re: Incompatible change for extensions

2013-01-17 Thread Jürgen Schmidt
On 1/17/13 12:24 PM, Bernard Marcelly wrote: Hello, I read report 121577 and did not notice the problem. https://issues.apache.org/ooo/show_bug.cgi?id=121577 Then I found this in the dev mailing list : http://www.mail-archive.com/dev@openoffice.apache.org/msg02906.html I noticed that

Re: Incompatible change for extensions

2013-01-17 Thread Bernard Marcelly
Message de Jürgen Schmidt date 2013-01-17 13:19 : I disagree, the old mechanism is a design bug and should be resolved. It was always planned to fix this a major release. Now with 4.0 we can make such changes and we had long discussions about incompatible changes for major releases. Extensions

Re: Incompatible change for extensions

2013-01-17 Thread Jürgen Schmidt
On 1/17/13 3:00 PM, Bernard Marcelly wrote: Message de Jürgen Schmidt date 2013-01-17 13:19 : I disagree, the old mechanism is a design bug and should be resolved. It was always planned to fix this a major release. Now with 4.0 we can make such changes and we had long discussions about