Author: [email protected]
Date: Wed Jun 3 13:22:41 2009
New Revision: 5500
Modified:
wiki/DefaultLocaleBinding.wiki
Log:
Edited wiki page through web user interface.
Modified: wiki/DefaultLocaleBinding.wiki
==============================================================================
--- wiki/DefaultLocaleBinding.wiki (original)
+++ wiki/DefaultLocaleBinding.wiki Wed Jun 3 13:22:41 2009
@@ -35,7 +35,7 @@
The `AbstractLocalizableImpleCreator` code has to recognize generators
that operate only on "default," and decide based on whether
`default.locale` is or is not set and whether "default" is or is not in the
locales list whether and when to run a given generator; in this example,
the "fr_CA" permutation would run generators that run on all locales,
on "fr_CA" _or_ on "default". This requires access not to the defined
values (from `define-property` and `extend-property`), but to the set
values, which is currently inaccessible.
-More interesting changes happen in the property provider, which today can
access only selection properties _with multiple values_. I propose adding
access to configuration properties as well, using a template syntax in the
property provider JavaScript and token substitution in
`SelectionScriptLinker`, somethinglike this fragment from I18n.gwt.xml:
+More interesting changes happen in the property provider, which today can
access only selection properties _with multiple values_. The default
locale should not be multiple, which is one reason I suggest it as a
configuration property. I propose giving property providers access to
configuration properties as well, using a template syntax in the property
provider !JavaScript and token substitution in `SelectionScriptLinker`,
something like this fragment from I18n.gwt.xml:
{{{
while (!__gwt_isKnownPropertyValue("locale", locale)) {
@@ -49,4 +49,4 @@
}
}}}
-Note that this is a static substitution, because configuration properties
have fixed value, unlike selection properties. The substitution is used in
generated the selection script, so a request for locale "jp" will fail to
match known property values and be assigned "fr_CA" instead, as the
requested `default.locale`.
+Note that this is a static substitution, because configuration properties
have fixed value, unlike selection properties. The substitution is used in
generated the selection script, so a request for locale "jp" will fail to
match known property values and be assigned "fr_CA" instead, as the
requested `default.locale`.
\ No newline at end of file
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---
