how about compressing css?

1 view
Skip to first unread message

Martin Trummer

unread,
Dec 3, 2009, 5:16:32 AM12/3/09
to Google Web Toolkit
when using GWT together with 3rd party libs, you sometimes get really
huge css files.

would it be possible to use some mechanism like the i18n constants for
css classes and styles, so that the css-classnames could be shortened/
obfuscated?
Not only would it decrease filesize (like zipping the response), we
could use interfaces to refer to the css-style names and thus gain
compile time checks.

any thoughts?

Thomas Broyer

unread,
Dec 3, 2009, 6:30:42 AM12/3/09
to Google Web Toolkit
What you describe is *exactly* what ClientBundle/CssResource does in
GWT 2.0. It's an evolution of ImmutableResourceBundle/CssResource from
the GWT Incubator, which can be used in previous versions of GWT (1.7,
at least)

Martin Trummer

unread,
Dec 3, 2009, 7:31:41 AM12/3/09
to Google Web Toolkit
D'oh!
they did it again: goolge stole my idea.

and the worst thing: they did it month before I even had it!

that can only mean one thing: google do have the time-machine

please, please google: let me use it only once to go back in
time and prevent Wham! from singing 'Last Christmas'

BTW: thanks for the answer, I somehow missed that

7bf

unread,
Dec 3, 2009, 5:59:03 AM12/3/09
to Google Web Toolkit
isn't that exactly what all these compressors out there (take
http://developer.yahoo.com/yui/compressor/ for example) do?

Content zipping is something most application servers support, without
any need to change
your application. But there are other, better, way to archive this.
Take a look what for example http://grails.org/plugin/ui-performance
does at compile time.

On Dec 3, 11:16 am, Martin Trummer <martin.trum...@24act.at> wrote:
Reply all
Reply to author
Forward
0 new messages