We worked on a migration plan a few weeks back. I don't think we need to mix css and gss together inside the same app.
At this point, the libraries have multiple reasonable options on compatibility: 1- Provide both css and gss file for the resource (recommended). The library will work fine regardless if the app enables gss or not as the right file will be chosen for the app. That's what we will do for internal resources in the SDK. 2- Keep providing the css file and make sure it works in strict mode. The library will work fine in css mode and will work with gss only if the legacy mode is enabled. 3- Keep the old css that requires lenient mode. The library will work fine in css mode and *may* work with gss if lenient legacy mode is enabled. More problematic part is the css inside uibinder. Like you said, simplest option is to introduce a temporary attribute in <ui:style> tag that marks the content as gss. In this case it is more tricky for the library to support compatibility mode similar to the mode (1) above. Either the lib should write the style that both compiles with css and gss or if it is not feasible then it should extract the resource to a file and follow the two file approach described above. On Mon, Oct 6, 2014 at 12:54 PM, Julien Dramaix <[email protected]> wrote: > > Hmm but still a bit of work if a library has lots of inline styles and > wants to use GSS stuff. > If you want to use GSS in all of your inline styles, you have first to > convert them to GSS and it will take more time than simply adding an > attribute that say that this inline style is using GSS. > > The problem with UiBinder is that we don't know if the developer is using > CSS or GSS because the CssResource interface is generated and we cannot > based our logic on the file extension as we do with normal CssResource. > > I have still to investigate but I'm pretty sure that adding an attribute > will be the easiest way to support correctly GSS in uibinder inline style. > > > > > -- > 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%3D4gaeww%3DY4cTkvNXXKKNmig6_s1CaOpwNAAemHXemb%2BjQ%40mail.gmail.com > <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABb_3%3D4gaeww%3DY4cTkvNXXKKNmig6_s1CaOpwNAAemHXemb%2BjQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAN%3DyUA2FYLyv%3DWYfOi0TqtojPbCTPkgzApW6J3BwnmJP19HVAQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
