Re: Bundled extensions
Hi, Am 12.04.2012 04:23, schrieb xia zhao: Josef, The bundled extension is easy to remove. After you install AOO, select Tools-Extension Manager. In the extension manager dialog, you can Disable or Remove the extension very easily. Thats well-known. But you have to do it every time after installing a new version. Installed extensions remain during a installation. So there is IMHO no reason to install the bundled ones again. In earlier version of OO the extensions were included as separate (DEB)-packages, so that you could delete them after unpacking. I used a script to download, delete some packages and install OO. Regards Josef -- PGP Schlüssel: 311D1055 http://keyserver.pgp.com
Re: Bundled extensions
Hi, Am 12.04.2012 06:46, schrieb Andre Fischer: Which ones and why? Do you want to drop any non-german dictionary, or any extension that is not de-DE? - dict-de_DE-frami_2011-06-03.oxt - a modified dict-en.oxt with GB only - report-builder If you remain to bundle extensions it would be easier to prevent (with a separate package) that they will be installed. Would that really be the right place to make extensions optional? I am not so sure. With windows you can do a user defined installation to deselect unwanted things. With linux this should be also possible before installation. It's not necessary that each new version installs per default extensions which I don't want, espacially the older ones remain. Regards Josef -- PGP Schlüssel: 311D1055 http://keyserver.pgp.com
Re: Bundled extensions
On 11.04.2012 09:40, drew jensen wrote: On Wed, 2012-04-11 at 03:28 +0200, Jürgen Schmidt wrote: On 4/10/12 3:45 PM, O.Felka wrote: Am 10.04.2012 15:28, schrieb Rob Weir: On Tue, Apr 10, 2012 at 6:43 AM, O.Felkaolaf-openoff...@gmx.de wrote: The bad news: - The error http://download.translate.org.za/spellchecker/dict-en_ZA-latest.update.xml does not exist. is still present - looks not very professional. That URL is an external one, not one that we control. Do you know what the behavior is in OOo 3.3 when checking for an update of that extension? No, I have no idea what OOo 3.3 will do. But I think it would behave the same. But I'm sure we wouldn't have bundled it. yes it should it be the same problem in OOo3.3. I would propose that we don't bundle extensions that will include an external update Url or something like that. We should bundle extension only that will be supported and completely handled by our extension repo. ah - ok, that sounds reasonable at it's face. Now if an extension is published at the AOO ext. repository and it's implemented in a scripted language (basic, js, python, etc) the oxt (extension body) is the source code, so that makes easy sense. Removed the extension from main/extensions.lst in revision is 1324590. -Andre What if the extension is in java or c++ or some other language where an external source repository is used, however the extension runtime and support vector are both through the AOO ext. repository - I would assume given a suitable license on the source that it would be, eligible, for consideration. Anyway - I'm putting forth a question that doesn't need to be answered today, just thinking out loud I suppose. //drew If no update Url is given in the extension and the extension is distributed via the ext repo the update info Was (and hopefully is, will be) generated on demand. Juergen
Re: Bundled extensions
Felka, This should be old problem, another volunteer report the similar problem as well though I didn't catch it when I install English full package and Simple Chinese full package on Mac lion and Windows XP. For the bundle, which extension should be bundled should depend on the real usage. For example, for English package, the english related directories should be bundled. And for one specific lanauge package, the related language directory should be bundled as well. But if many directories for one language, say, English, should we bundle all of them? It should depend one user requirements and if it is handled by our extension pool. For other extension not related to directory, we may also bundle it depend on the if most user will need. Actually for one extension used by most people, I prefer driving it to become one feature of next release. Best Regrads, Lily 2012/4/10 O.Felka olaf-openoff...@gmx.de Moin, I've tested r1309668 en_US to verify the fix for issue 119114 [1]. The good news: - No crash when checking for updates. The bad news: - The error http://download.translate.**org.za/spellchecker/dict-en_** ZA-latest.update.xmlhttp://download.translate.org.za/spellchecker/dict-en_ZA-latest.update.xmldoes not exist. is still present - looks not very professional. - Clicking on 'Show all Updates' shows English (South Africa) spell checker as update available. The description field shows 'An error occurred: Not found!' - looks not very professional. - The presenter screen extension is not installed. Groetjes, Olaf [1] https://issues.apache.org/ooo/**show_bug.cgi?id=119114https://issues.apache.org/ooo/show_bug.cgi?id=119114
Re: Bundled extensions
Josef, The bundled extension is easy to remove. After you install AOO, select Tools-Extension Manager. In the extension manager dialog, you can Disable or Remove the extension very easily. Best regards, Lily 2012/4/11 Josef Latt josef.l...@gmx.net Hi, Am 11.04.2012 12:17, schrieb Andre Fischer: On 11.04.2012 18:05, Josef Latt wrote: Hi, Am 11.04.2012 10:26, schrieb xia zhao: I would prefer that no extensions are bundled. Can you provide reasons for that ? As you can see below, there are IMHO some unnecessary extensions for a German user. I prefer installing only needed extensions. The problem comes up every time if you install a new version of OOo. In this package Apache_OpenOffice_incubating_**3.4.0_Linux_x86-64_install-**deb_de.tar these extensions are bundled: dict-de_DE-frami_2011-06-03.**oxt dict-de_AT-frami_2011-06-03.**oxt dict-de_CH-frami_2011-06-03.**oxt dict-en.oxt dict-it.oxt ooo-dictionnaire-fr-moderne-**v4.2.oxt presentation-minimizer.oxt presenter-screen.oxt They are in this package 'ooobasis3.4-core01_3.4.0-1_**amd64.deb' and will be automaticly installed when OOo is started the first time. IMHO not so good. Why? If you remain to bundle extensions it would be easier to prevent (with a separate package) that they will be installed. Regards Josef -- PGP Schlüssel: 311D1055 http://keyserver.pgp.com
Re: Bundled extensions
On 11.04.2012 21:27, Josef Latt wrote: Hi, Am 11.04.2012 12:17, schrieb Andre Fischer: On 11.04.2012 18:05, Josef Latt wrote: Hi, Am 11.04.2012 10:26, schrieb xia zhao: I would prefer that no extensions are bundled. Can you provide reasons for that ? As you can see below, there are IMHO some unnecessary extensions for a German user. Which ones and why? Do you want to drop any non-german dictionary, or any extension that is not de-DE? I prefer installing only needed extensions. The problem comes up every time if you install a new version of OOo. In this package Apache_OpenOffice_incubating_3.4.0_Linux_x86-64_install-deb_de.tar these extensions are bundled: dict-de_DE-frami_2011-06-03.oxt dict-de_AT-frami_2011-06-03.oxt dict-de_CH-frami_2011-06-03.oxt dict-en.oxt dict-it.oxt ooo-dictionnaire-fr-moderne-v4.2.oxt presentation-minimizer.oxt presenter-screen.oxt They are in this package 'ooobasis3.4-core01_3.4.0-1_amd64.deb' and will be automaticly installed when OOo is started the first time. IMHO not so good. Why? If you remain to bundle extensions it would be easier to prevent (with a separate package) that they will be installed. Would that really be the right place to make extensions optional? I am not so sure. -Andre
Bundled extensions
Moin, I've tested r1309668 en_US to verify the fix for issue 119114 [1]. The good news: - No crash when checking for updates. The bad news: - The error http://download.translate.org.za/spellchecker/dict-en_ZA-latest.update.xml does not exist. is still present - looks not very professional. - Clicking on 'Show all Updates' shows English (South Africa) spell checker as update available. The description field shows 'An error occurred: Not found!' - looks not very professional. - The presenter screen extension is not installed. Groetjes, Olaf [1] https://issues.apache.org/ooo/show_bug.cgi?id=119114
Re: Bundled extensions
On Tue, Apr 10, 2012 at 6:43 AM, O.Felka olaf-openoff...@gmx.de wrote: Moin, I've tested r1309668 en_US to verify the fix for issue 119114 [1]. The good news: - No crash when checking for updates. The bad news: - The error http://download.translate.org.za/spellchecker/dict-en_ZA-latest.update.xml does not exist. is still present - looks not very professional. That URL is an external one, not one that we control. Do you know what the behavior is in OOo 3.3 when checking for an update of that extension? -Rob - Clicking on 'Show all Updates' shows English (South Africa) spell checker as update available. The description field shows 'An error occurred: Not found!' - looks not very professional. - The presenter screen extension is not installed. Groetjes, Olaf [1] https://issues.apache.org/ooo/show_bug.cgi?id=119114
Re: Bundled extensions
Am 10.04.2012 15:28, schrieb Rob Weir: On Tue, Apr 10, 2012 at 6:43 AM, O.Felkaolaf-openoff...@gmx.de wrote: The bad news: - The error http://download.translate.org.za/spellchecker/dict-en_ZA-latest.update.xml does not exist. is still present - looks not very professional. That URL is an external one, not one that we control. Do you know what the behavior is in OOo 3.3 when checking for an update of that extension? No, I have no idea what OOo 3.3 will do. But I think it would behave the same. But I'm sure we wouldn't have bundled it. Regards, Olaf
Re: Bundled extensions
On Wed, 2012-04-11 at 03:28 +0200, Jürgen Schmidt wrote: On 4/10/12 3:45 PM, O.Felka wrote: Am 10.04.2012 15:28, schrieb Rob Weir: On Tue, Apr 10, 2012 at 6:43 AM, O.Felkaolaf-openoff...@gmx.de wrote: The bad news: - The error http://download.translate.org.za/spellchecker/dict-en_ZA-latest.update.xml does not exist. is still present - looks not very professional. That URL is an external one, not one that we control. Do you know what the behavior is in OOo 3.3 when checking for an update of that extension? No, I have no idea what OOo 3.3 will do. But I think it would behave the same. But I'm sure we wouldn't have bundled it. yes it should it be the same problem in OOo3.3. I would propose that we don't bundle extensions that will include an external update Url or something like that. We should bundle extension only that will be supported and completely handled by our extension repo. ah - ok, that sounds reasonable at it's face. Now if an extension is published at the AOO ext. repository and it's implemented in a scripted language (basic, js, python, etc) the oxt (extension body) is the source code, so that makes easy sense. What if the extension is in java or c++ or some other language where an external source repository is used, however the extension runtime and support vector are both through the AOO ext. repository - I would assume given a suitable license on the source that it would be, eligible, for consideration. Anyway - I'm putting forth a question that doesn't need to be answered today, just thinking out loud I suppose. //drew If no update Url is given in the extension and the extension is distributed via the ext repo the update info Was (and hopefully is, will be) generated on demand. Juergen
