thx for the feedback.

About the XML: the easy parsing of the resources is why I chose XML as a dataholder. The format is so easy and generic that you never need to extend your parser. The idea of using VO’s to hold the localized strings would indeed have the big advantage of having type checking and code completion. However it felt like too much work to update the VO’s and the parsers every time we need new strings. My aim is also to provide a built in way of handling localization inside ARP. The less you have to do as a developer, the better IMO.

About the localeChanged event and the databinding: That’s actually something we’ve been thinking about as well. We didn’t implement it though because we were afraid that it wouldn’t be flexible enough for reasons that we couldn’t come up with at that moment. We could still introdude a new class LocaleBinder or something that lets you bind certain properties to certain resource strings in the resourcebundle.

Note that the localization efforts are experimental. Be sure to check back for new thoughts or updates. In the meantime, your thoughts are more than welcome.

regards,
Christophe

Thx for sharing =).

I have to admit that I havn´t wrote a localized application by now, just a few thoughts on your localization example anyway .
@XML Format: I also first thought about putting the localized strings into an xml file, but on the other side in java world, resource bundles have a format like:
DOCUMENT_DOWNLOAD=Download Document
If you use it that way, you can use existing resource bundle tools. On the other hand and xml file would be easier to parse for the first time.
Another idea would be parsing the file serverside and filling a VO, which is transfered with remoting to the client. The advantage of this method would be that you
can automatically generate a VO for the clientside developer, who can easily use code completion for setting the locale strings. So there are less typos.

I also thought about eliminating the need of a localeChanged event with a kind of databinding. But for this I need first an instance of my ressource bundle, which is referenced by the different views. e.g.: firstname_lbl.text = ressourceBundle.FIRSTNAME;. After data is received from serverside or xml the ResourceBundle instance is updated and because of the existing references the views too.

What do you think?

cheers

Christoph