Frank Schönheit wrote:
Hi Jürgen,
Having the overall picture (where we want to go in the future) in mind
can help to find the right solution for your localized strings now.
Who does have this picture, and when?
good question, i would say we have put the brushes and colors on the
table to start drawing ;-)
No, i think that we have some ideas. From my point of view the most
promising thing is the XUL approach for components first and maybe later
for other parts of the office also. And the second promising way is the
extension or redesign of the existing awt toolkit. But of course no
decision is made so far.
I agree that property files maybe can help here.
Reading Eike, who also has the requirement to access strings in existing
resources ....
Maybe we can define a "service OfficeResourceBundleLoader :
XResourceBundleLoader", which explicitly states that it is able to load
resources from OOo resource files. This way, we would not pollute the
basic interfaces.
good idea to solve the current problem and to provide a fast solution
for now. But nobody should expect that we will enable the deployment of
this resource files at this time, i won't make it public for components
until the question of a toolkit and a related resource format is answered.
Juergen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
