Hi Frank,

On Tue, Mar 14, 2006 at 13:09:29 +0100, Frank Schönheit wrote:

> 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.
> 
> - Is anybody aware of an existing implementation of this API?

AFAIR Dirk Voelzke had a "private" implementation of it, or something
alike.


> - 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?

I know of at least one case where being able to access already existing
OOo resources would be of help, which is about obtaining the localized
language/locale names OOo knows, see
http://qa.openoffice.org/issues/show_bug.cgi?id=59738


>   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?

I'm not sure how mapping strings to IDs would work without having to
define yet another ugly mapping table. Maybe Dirk can shed some light on
that.


>   - 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?

I wonder whether that is actually used anywhere above svx, if at all..


> - Is the naming convention issue really an issue? Can we "re-document"
>   XResourceBundle to follow OOo's resource file naming conventions,

Since that is a yet unimplemented OOo API I'd say sure, why not. If it's
only the file naming and no type information change it shouldn't be
a problem, even if someone had an own implementation of the interface.

>   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)?

I don't think that's worth the effort. Or would it have any other
benefit than just following Java's naming convention?

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

Go ahead ;-)

  Eike

-- 
 OOo/SO Calc core developer. Number formatter stricken i18n transpositionizer.
 GnuPG key 0x293C05FD:  997A 4C60 CE41 0149 0DB3  9E96 2F1A D073 293C 05FD

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

Reply via email to