Using unchanged CSS class names (no obfuscation or prefixing at all)

22 views
Skip to first unread message

sinelaw

unread,
Nov 28, 2010, 5:06:22 AM11/28/10
to Google Web Toolkit
I've created a patch for CssResources to not change CSS class names at
all.

Details + motivation are given in the issue here:
http://code.google.com/p/google-web-toolkit/issues/detail?id=5659

Also, see at least one case where a developer (other than me) needed
such a feature:

http://code.google.com/p/google-web-toolkit/issues/detail?id=5659&can=4&colspec=ID%20Type%20Status%20Owner%20Milestone%20Summary%20Stars


Comments welcome,
Noam Lewis
EntireOne Inc.

jhulford

unread,
Nov 30, 2010, 9:35:11 AM11/30/10
to Google Web Toolkit
I'm probably missing something, but how is this different than using
the "CssResource.style" property in your module's XML and setting the
value to "pretty"? Doing that results in disabling the class name
obfuscation.

You can also use the @External annotation on individual css classes to
do the same if you don't want everything in a CssResource being
unobfuscated.


On Nov 28, 5:06 am, sinelaw <jones.noa...@gmail.com> wrote:
> I've created a patch for CssResources to not change CSS class names at
> all.
>
> Details + motivation are given in the issue here:http://code.google.com/p/google-web-toolkit/issues/detail?id=5659
>
> Also, see at least one case where a developer (other than me) needed
> such a feature:
>
> http://code.google.com/p/google-web-toolkit/issues/detail?id=5659&can...

regis.dev

unread,
Sep 5, 2011, 11:09:59 PM9/5/11
to google-we...@googlegroups.com
Hi i found a solution. no obfuscation or prefixing at all.
At the begin of your css file put this line.

@external *


PS: it working with gwt 2.4-rc1 (it should work for the olders versions)
Reply all
Reply to author
Forward
0 new messages