On 2009/06/05 20:09:49, fabbott wrote:
Ping for comment. Bruce had asked about additional possible use cases for the property provider template thing. The abstract answer is "any case where a permuted property depends on a non-permuting one"... these are hypothetical, and off-the-cuff so not particularly strong, but I can imagine: * analogous negotiation for content-type, perhaps to permute over "efficient" image or resource formats in bundles as supported by browser, with a configured default fallback. * also analogous charset selection * hoisting default specification of e.g. logging level out of the provider, so users can adjust it with a set operation without asking users to rewrite the property provider (if they want to change the packaged default, ours or third-party). http://gwt-code-reviews.appspot.com/34832 --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---