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
