Comment by [email protected]:
Recording that I think the simplest approach is actually
{{{<append-configuration-property>}}}. I think there are sane answers to
all the question raised:
* Should a delimiter be added automatically? If not, what happens if the
string was previously empty, thus creating a bogus initial delimiter?
No automatic delimiter. It'd be up to the user to provide whatever
delimiter they needed. The "initial delimiter" problem isn't too hard to
solve with careful design. As an example, with a Java path it's harmless
to have an initial delimiter, or even multiple delimiters in a row, since
empty string is distinct from a single dot for current directory.
* How do we differentiate the concept of 'no value' from the concept
of 'has a value that is the empty string'?
Our APIs could return 'null' vs. "". However, ideally generators wouldn't
care and would just treat them the same.
* Can you append a 'no value'?
It would have no effect since it would not change the property string
(since GWT would not automatically add delimiters).
* How would we recommend people parse this string within generators?
{{{String.split(delimiter)}}}, ignore any empty pieces.
For more information:
http://code.google.com/p/google-web-toolkit/wiki/MultiValuedConfigProperties
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---
