Re: Where to find information about *.xcu schema (extension, dev, toolbar)

>Where to find information about *.xcu schema (extension, dev, toolbar) Use this extension: http://wiki.services.openoffice.org/wiki/Extensions_Packager Easy to produce OXT - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apa

Re: Where to find information about *.xcu schema (extension, dev, toolbar)

On 04/07/2016 07:55 AM, Christian Giehl wrote: Hi, I'm currently working on a custom toolbar for my oo-extension. To create the visual appearance of the toolbar, I have to write an Addons.xcu file, which contains a custom xml. However, the tag names and attributes I found in the tutorial all

Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues

On Thu, Apr 7, 2016 at 9:59 AM, Marcus wrote: > Am 04/07/2016 06:35 PM, schrieb Dennis E. Hamilton: > >> My only concern is that this is a giant CTR and pretty much assures that >> the "R" will not happen. >> > > yes, but especially with old issues I don't see a big problem here. Maybe > for sing

Apache OpenOffice Mailing List Statistics

[BCC to PMC] The tabulation below provides the rate of mailing list usage for all of public lists since Apache OpenOffice became a top-level project in November 2012. The full, auditable compilation of the data can be found in the PDF at . In the tabulation below, th

Re: Cross Script vulnerabilities in AOo Extensions?

On 4/7/16, toki wrote: > All: > > In reading > http://arstechnica.com/security/2016/04/noscript-and-other-popular-firefox-add-ons-open-millions-to-new-attack/ > is the same type of vulnerability is possible with AOo extensions? > > jonathon "By piggybacking off the capabilities of trusted third-p

Re: Cross Script vulnerabilities in AOo Extensions?

On 07/04/2016 16:35, Dennis E. Hamilton wrote: > Multi-component collaborative exploit staging is possible although unnecessary. Rephrasing: For the time being, at least, one can "safely" ignore this type of exploit, because other vectors are much easier to exploit. Still, for those who are para

Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues

Am 04/07/2016 06:35 PM, schrieb Dennis E. Hamilton: My only concern is that this is a giant CTR and pretty much assures that the "R" will not happen. yes, but especially with old issues I don't see a big problem here. Maybe for single issues. But IMHO this is no argument to keep every issue

RE: Cross Script vulnerabilities in AOo Extensions?

Toki, thanks for your useful question. Here are some factors to consider. 1. The Apache OpenOffice project does not vet or review extensions and templates that are produced by third parties and downloadable from the SourceForge extension and template collections. These are all "at your own r

RE: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues

My only concern is that this is a giant CTR and pretty much assures that the "R" will not happen. So be it. However, do not disable the issues mails for any reason. There is a difference between R not happening and R not being possible. - Dennis > -Original Message- > From: Marcus [

Re: Eclipse Module Export UNO -> OOo package does not proceed

Am 4/7/2016 um 12:47 AM schrieb Carl Marcum: On 04/06/2016 04:35 AM, Christian Giehl wrote: Hi, I'm fairly new on the field and wanted to start developing an extension to be used in Writer. I started on reading the wiki and just tried to follow the tutorial here: https://wiki.openoffice.org/wik

Where to find information about *.xcu schema (extension, dev, toolbar)

Hi, I'm currently working on a custom toolbar for my oo-extension. To create the visual appearance of the toolbar, I have to write an Addons.xcu file, which contains a custom xml. However, the tag names and attributes I found in the tutorial all across the www are not sufficient for my case a

Cross Script vulnerabilities in AOo Extensions?

All: In reading http://arstechnica.com/security/2016/04/noscript-and-other-popular-firefox-add-ons-open-millions-to-new-attack/ is the same type of vulnerability is possible with AOo extensions? jonathon signature.asc Description: OpenPGP digital signature

Re: [DISCUSS] Cleanup needed for RESOLVED-FIXED issues

Am 04/07/2016 12:43 AM, schrieb Kay Schenk: I think typically the process for RESOLVED-FIXED (those issues that were fixed by some kind of code change to /trunk) issues is to: * commit the change to a release build * once the release build is out for testing, check that the bug is fixed, and use