From api-return-177-apmail-openoffice-api-archive=openoffice.apache.org@openoffice.apache.org Thu Jan 17 11:24:54 2013 Return-Path: X-Original-To: apmail-openoffice-api-archive@www.apache.org Delivered-To: apmail-openoffice-api-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 87131EDF2 for ; Thu, 17 Jan 2013 11:24:54 +0000 (UTC) Received: (qmail 52443 invoked by uid 500); 17 Jan 2013 11:24:54 -0000 Delivered-To: apmail-openoffice-api-archive@openoffice.apache.org Received: (qmail 52217 invoked by uid 500); 17 Jan 2013 11:24:50 -0000 Mailing-List: contact api-help@openoffice.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: api@openoffice.apache.org Delivered-To: mailing list api@openoffice.apache.org Received: (qmail 52182 invoked by uid 99); 17 Jan 2013 11:24:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 11:24:48 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [93.17.128.81] (HELO smtp24.services.sfr.fr) (93.17.128.81) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2013 11:24:42 +0000 Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2402.sfr.fr (SMTP Server) with ESMTP id E16CB7000070 for ; Thu, 17 Jan 2013 12:24:20 +0100 (CET) Received: from [192.168.1.80] (83.7.75.86.rev.sfr.net [86.75.7.83]) by msfrf2402.sfr.fr (SMTP Server) with ESMTP id BD0D8700006E for ; Thu, 17 Jan 2013 12:24:20 +0100 (CET) X-SFR-UUID: 20130117112420774.BD0D8700006E@msfrf2402.sfr.fr Message-ID: <50F7DF5F.6090700@club-internet.fr> Date: Thu, 17 Jan 2013 12:24:15 +0100 From: Bernard Marcelly User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: API Apache Subject: Incompatible change for extensions Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello, I read report 121577 and did not notice the problem. Then I found this in the dev mailing list : "I noticed that add-on extensions with toolbars have a problem on trunk. The ext can be installed but the toolbar is not visible and also not in the View -> Toolbars menu. Top-level menus coming with the same ext are visible. I am currently don't know if it is related to the bigger changes with the name or something else in the context of add-on, means the framework part." As you can read in answers to this thread, it means that the next version of Apache OpenOffice will be _incompatible_ with _all_ extensions created before. Such a case should only happen for a compelling reason. I think this is not the case. Bug 121577 is introduced only for a futile purpose: "the extension developer has to create a configuration file WindowState.xcu for every office module where the toolbar is to be displayed, even if the toolbar name will be exactly the same in every module." This is futile because it is not a big simplification of the creation of the various xml files of an extension. In fact the only "human" way of creating the numerous files of an extension is to use a tool. Then the invoked complexity or tediousness (almost) disappears. See : Of course an extension packager can be modified to the new addon syntax. The problem is not here, it is that all existing extensions will not work as designed unless they are each modified. And modified extensions will not be compatible with previous versions or with LibreOffice. Regards Bernard