On Sunday, August 21, 2016, Jens <email@example.com> wrote:
--Unfortunately, using a separate TextResource isn't quite what I'm looking for. I want the best of both worlds. :)Hm looking at the syntax of EQCSS again, it seems that you have to fork GWT anyways, because even if GSS would allow @element you would still need to obfuscate the selector (css id of class) if its a non-external css class/id managed by CssResource.Alternatively you could try to implement your own EqCssResource and write your own EqCssResourceGenerator since the ClientBundle/Resource mechanism is extendable in GWT for custom resources.-- J.
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+
To post to this group, send email to google-web-toolkit@
Visit this group at https://groups.google.com/
For more options, visit https://groups.google.com/d/
-.. .- ...- .. -.. ... -... . -.-. -.- . .-.
This message was sent from my mobile phone. Please excuse any typos or auto-corrections I might have missed.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.