[dev] External Properties in oxt
Hi I was wondering if there is an elegant way to make an extension modifyable without deploying a new oxt. Thus i want to provide external proptery - files which specify certain paths, i18n userinterface strings, and so on. Is there a special functionality / design guideline for such a purpose or should i just parse the config files with standard java code within my extension? Best Regards, Phil -- View this message in context: http://www.nabble.com/External-Properties-in-oxt-tp25019632p25019632.html Sent from the openoffice - dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] External Properties in oxt
No. However you could use the configuration. That is, a new extension installes a xcu containing the new data, which is then used by the first extension. But I think this will just complicate matters and it is probably best to ship a new version of your extension containing the modified data. Joachim Vil wrote: Hi I was wondering if there is an elegant way to make an extension modifyable without deploying a new oxt. Thus i want to provide external proptery - files which specify certain paths, i18n userinterface strings, and so on. Is there a special functionality / design guideline for such a purpose or should i just parse the config files with standard java code within my extension? Best Regards, Phil - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] External Properties in oxt
i would recommend that all necessary information comes with the extension and if necessary update the oxt. How you access these config files in your oxt is up to you. The PackageInformationProvider gives you access to the root dir of your oxt after installation. That means you should have access on the whole content of your oxt. For localized strings you can use a mechanism similar to Java property files that uses the office locale... See http://api.openoffice.org/docs/common/ref/com/sun/star/resource/module-ix.html and the DevGuide how to localize dialogs Juergen Vil wrote: Hi I was wondering if there is an elegant way to make an extension modifyable without deploying a new oxt. Thus i want to provide external proptery - files which specify certain paths, i18n userinterface strings, and so on. Is there a special functionality / design guideline for such a purpose or should i just parse the config files with standard java code within my extension? Best Regards, Phil - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
