On 06/01/2010 10:54 AM, geoffre wrote:
> Le 01/06/2010 09:52, geoffre a écrit :
>> Le 01/06/2010 09:50, geoffre a écrit :
>>> Hi,
>>>
>>> I have the following problem; the method this.tr() use for
>>> internationnalization return me a "qx.locale.LocalizedString" instead of
>>> a "qx.locale.String".
>>>
>>> Am I obliged to add a toString() after each this.tr() ?
>>>
>>> Thanks.
>>>
>>>
>>> ------------------------------------------------------------------------------
>>
>> Just for information, I use qooxdoo 1.0.1.
>>
>>
>> ------------------------------------------------------------------------------
>
> Hi,
>
> I have added the following lines to my config.json jobs part to set the
> "qx.dynlocale" to "off":
>
> "source-script" :
> {
> "variants" :
> {
> "qx.debug" : ["on"],
> "qx.dynlocale" : ["off"]
> }
> },
>
> "build-script" :
> {
> "variants" :
> {
> "qx.debug" : ["on"],
> "qx.dynlocale" : ["off"]
> }
> },
>
> With this modification I don't have the problem, but what will be the
> incidence of this modification on the rest of the application ?
The basic difference is that a qx.locale.LocalizedString will react on
changes to the locale during application run time (e.g. with
qx.locale.Manager.getInstance().setLocale()). A string won't do that, it
is static. A qx.locale.LocalizedString will immediately reflect the new
setting. So the question boils down to whether you want to support
locale changes in the running application or not.
T.
>
> Thanks.
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
