Hi, I've pushed the code for the so called GssResource.
The code has been split in two patches: - The first one contains the code for the converter. The converter can be used in order to convert the existing css files to a GSS compatible file. - The second one contains the code for the generator that parses and compiles the GSS file and produces the implementation of the related CssResources. It would be nice to get this code in GWT 2.7, so could you review the two patches ? The GSS support won't be enabled by default. In order to enable it, you will have to set the configuration property named "CssResource.enableGss" to true. When enabled, all of the CssResource will be generated by using the GssGenerator. If your application is using a third-party library that defines some CssResource that aren't converted to GSS, you can also enable the in-memory conversion (of css files with .css extension) to GSS by setting the configuration property "CssResource.legacy" to true. This conversion can run in strict (throw error if the original file contains some errors) or lenient mode (does its best to fix the original file) . Now I think we should allow the inverse: give the ability to third party libraries to use GSS in their CssResource even if the CssResource.enableGss is set to false. This could be done by either using an annotation or by using a configuration property in the module file. What do you think it would be the best ? I'm more in favor of the annotation. Julien -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4HmWFv0V2BVi5qf3B8Jdjkt-eUXZD4hBLvuM5X_U5qxQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
