Do you plan to bring Closure Compiler (-XenableClosureCompiler option) back to GWT? It was very useful for us.
Do you plan to bring Closure Compiler (-XenableClosureCompiler option) back to GWT? It was very useful for us.No. It was experimental and had some rough edges that haven't been fully implemented.
And why don't keep it experimental too in 2.8 instead of removing it?
And why don't keep it experimental too in 2.8 instead of removing it?Why keeping it if it's only half baked into GWT and you can run it externally as well?
Do you have a step by step guide to run the closure compiler externally ?
What if we have SSO linker ?
Then no hacks is needed, right ?
Then just run the Google Closure Compiler on the output.
I've tried WITHOUT any success to use closure compiler externally with GWT 2.8
I have some glue. Google JS Compiler used in chrome is able to detect some patterns and jit. But some patterns are not detected.
Ex: for are deceted, do ... while sometimes not.
It happens so that GWT produce patterns detectable for JS Compiler. And Closure can break that structure.
I am happy that GWT dropped cl suppert and focus on JsInterop (where is JsIndexer?)
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/topic/google-web-toolkit/IIQk4xH0-g8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsub...@googlegroups.com.
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.
Do you use SSO ? SSO script is smaller then no SSO. Did you run CC on it ?
I also use smaller css class names:
<set-configuration-property name="CssResource.obfuscationPrefix" value="empty" />
In my very specific case this makes a big difference.
I do multiple build manually for each language until I find a better solution.