Hi,

currently, no way exists fore mere UNO components to access localized
resources, i.e. data stored in OOo's *.res files [1]. That's Bad (TM),
since it forces UNO components to use unlocalized error messages, for
instance.

In theory, we have an API for loading resources:
css.resource.XResourceBundle/Loader [2]. Sadly, the bundle and thus
effectively the loader is deprecated. Not to mention that no
implementation exists for those interfaces.

Furthermore, the definition of the bundle seems to be, ehm, heavily
inspired from the respective Java API [3]. This is not bad in itself,
but it at least implies a resource file naming scheme which is not
conform to the resource file naming scheme used elsewhere in the
application.


I'd like to (at least initiate to :) resurrect the resource API, and
here are the items I'd like to discuss:

- Is anybody aware of an existing implementation of this API?

- Does it make sense to use the css.resource API for accessing OOo
  resources, or are there other problems ahead which suggest we define a
  new API?
  For instance, execpt the naming convention mentioned above:

  - Is it a problem that the css.resource API uses strings as keys to
    resource elements, while OOo's internal resource format is based on
    "resource type / resource id" pairs?

  - OOo's internal resource features hierarchic resources, a very
    powerful concept. This would (perhaps) be lost when using the
    existing css.resource API. Would it really? Would it be bearable to
    lose this feature?

- Is the naming convention issue really an issue? Can we "re-document"
  XResourceBundle to follow OOo's resource file naming conventions, or
  can we simply live with two different conventions (or even, on the
  medium term, move the existing resource files to the Java-like
  convention)?

- Is there any volunteer for implementing a XResourceBundle/Loader
  components? :)

Thanks for any opinions

Ciao
Frank

[1]No, please don't mention VclStringResourceLoader, which is only
   usable in language bindings like Basic and Python, and has a really
   crude syntax in all other bindings.

[2]http://api.openoffice.org/docs/common/ref/com/sun/star/resource/module-ix.html

[3]http://java.sun.com/j2se/1.5.0/docs/api/java/util/ResourceBundle.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to