[gwt-contrib] Re: Better support of IE6 for ImageResourceGenerator
Hi, > As for the question on adding another permutations... I think that > adding an ie7 permutation might be not necesarry. I posted a small > example on how I handle ie6/7(or 8 in ie7 mode) in my application... > it just means a small extra indirection but the cost is very low. It's > not like we are creating ImageBundles in a tight loop in our > applications (that is a bit against the whole idea of using them in > the first place). Your remark just made me think to something. The problem with extra permutations is mainly compile time. When 2 permutations are very close to one another (a lot of deferred binding will lead to the same implementation for the 2 permutations), dynamic selection through indirection might not be that costly in performance. There is also a loss because of some optimization that will not take place, but one will have to accept that. Then GWT could have an option to say that such and such permutation must be separated at runtime instead of compile time. That will allow the compilation to be as quick as now, but the designers will still be able to use the deferred binding mechanism to handle ie6/ie7 (for example). Moreover, one can imagine an option to have all permutations separated at runtime for speeding up the compilation in development mode. Did I miss something obvious? -- Benjamin Lerman --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: support for internationalized svninfo
> Description: > This is in response to Sebastien's complaint of 1jul09, that trunk > didn't compile because his French svn info gave output that didn't match > our English regexps. > > There are two parts to this: >1. If the output propety is already defined, don't > run svn, don't match the output, don't risk failing. > That would have given Sebastien a workaround, by > defining gwt.svnrev in local.ant.properties. >2. Change the regexps to be word-neutral, so that they > don't care about the language of the tags, just the > shape of the values. This trades a language > sensitivity for a positional one. Wouldn't using svn info --xml solve those problems? -- Benjamin Lerman --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
