On 1/19/13 3:47 AM, Martin Groenescheij wrote:
> On 19/01/2013 9:43 AM, Andrea Pescetti wrote:
>> Juergen Schmidt wrote:
>>> https://issues.apache.org/ooo/show_bug.cgi?id=121577
>>> The change is really easy and no big thing.
>>
>> Do we have a way to automatically produce a 4.0-compatible extension
>> starting from a 3.x extension?

no, we only document the migration path. Well if somebody wants to play
with an xsl transformation it should be possible to unpack an oxt
transform the Addon.xcu in the new format and repackage the oxt.


> Is it possible to have these extensions tested for the next release and
> add a note like:
>      "Tested successful with release x.x"?

yes, anybody can do that


>>
>> I'm quite concerned to leave hundreds of extensions behind and asking
>> their authors to upgrade them. Some of the most popular extensions are
>> not very actively maintained, so we should definitely think about
>> fixing the 10-20 most popular extensions by the time 4.0 is released.

well unmaintained code is always bad and I don't think that we will do
the work for external developers. Either developers take care of their
code or the code is open source and new maintainers can step in.

We have thought about a automatic migration but the effort is too huge.
But hey if somebody will invest his time here we will give support where
possible. But we have noticed that the whole extension manager is very
complex and I tend to say again an example of over engineered code. The
live deployment feature is of course nice but the overhead and
complexity it brings in the whole process is in no relation to the
benefit it provides. A clean restart of the office after the
installation would be for example much easier. And very often you have a
mixed env anyway and it works more by luck than by design ;-)

We should in the future keep things as easy and simply as possible to
fulfill the requirements and keep enough room for improvements. We
shouldn't look for 150% solutions that introduce more overhead than
necessary. We noticed that when the leading devs disappear in certain
areas it becomes not easy too maintain this code in the future.

>>
>> Reading the issue, I assume dictionaries are not affected since they
>> don't attach to toolbars, right?

yes they are not affected

Juergen


>>
>> Regards,
>>   Andrea.
>>
>>
> 

Reply via email to