Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
Received-SPF: pass (nike.apache.org: domain of jogischmidt@gmail.com
 designates 209.85.215.46 as permitted sender)
Message-ID: <50F6D4DE.8040203@gmail.com>
Date: Wed, 16 Jan 2013 17:27:10 +0100
From: =?ISO-8859-1?Q?J=FCrgen_Schmidt?= <jogischmidt@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: dev@openoffice.apache.org
Subject: Re: [CODE]: noticed a problem on trunk with add-on extensions and
 toolbars
References: <50F6ACD8.2020205@gmail.com> <20130116143517.GA3295@localhost>
In-Reply-To: <20130116143517.GA3295@localhost>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 1/16/13 3:35 PM, Ariel Constenla-Haile wrote:
> On Wed, Jan 16, 2013 at 02:36:24PM +0100, J�rgen Schmidt wrote:
>> Hi,
>> 
>> 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.
>> 
>> Does any body have an idea or is aware of changes here?
> 
> I guess you missed 
> https://issues.apache.org/ooo/show_bug.cgi?id=121577 See comment
> 2, the samples attached there, and the SDK examples:
> 
> odk/examples/java/Inspector/ 
> odk/examples/DevelopersGuide/Extensions/DialogWithHelp/ 
> odk/examples/cpp/complextoolbarcontrols/
> 

I had indeed the issue not in place but remembered that you wanted to
change it. I checked the schema and saw the new Title property for the
Toolbar. Good to know and we should communicate this very clear in the
release notes. I recommend a max version dependency for all add-on
extensions to 3.4/3.4.1 (have to check) and a quick and easy change
for 4.0. We know it is a very useful but incompatible change, future
extensions become much easier.

Thanks for the clarification

Juergen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBCgAGBQJQ9tTdAAoJEM/u8xZRtf3odhMQAIHkkOSZ6JHNl0HEXnWvz/qC
NqTAiSY8w/rPC5UvV3n1XyYScbuyOGgtvhrGzkyXT9aJIV8+aJgnpAFWV+mdOLzi
G//cX0YUyFWLD3FGBkqMtHUdkQoOzYgmfc/yCVIUPJJBA3n5d6Klk0pdIGd150xi
K+CanvZdvXSuxcf2IeaawbxKbqIT+GMFPOYjbJZbBCZb/al/cHNkbi3ZB+nTjCQt
CyKK0t756eaPZDStkv1777x7T2TqoQUyFvCDcSRTALRqVohZqRTqIysXkkempk8Y
m0iVQiAls/8sKF0ncaP++a+nS4Pu+jOS5HPrf7s5sQBGd7FZuot2U1dZ7oJbYWoM
2ahdY7+nH+68Rj4WRrWV8Wswy0hFK4SMssCQQqJFasbTvKq/oVCpEPiPaF3A8whx
ciiIXmU2PFmcsbAQd8u3LfORZsGkg0INMQCAOUbwkRk+duUct3cwleqQbFzqEJX9
jtfJWR6ujSJGdF19YafT76v/tlvh5EbJGcoA5+cmq2NyXe8PB6CiBUs9I+7IZBOY
eOe6Mgxz5CB71WfaAL9RAT1sZn8fTZCD3VcH04GG3WVBIUC62kRj7N4jqz6Hpp37
uY3b/JmQDlV4Jukj2lmmbS0siYBUtvGjDUXZYfiUCLYg/FbnLKR9QVZqa5qISFXC
zcjYFdIzZSdaeSuyEcaj
=GYo/
-----END PGP SIGNATURE-----