Re: compiled js files do not work, if compiled "obfuscated", only if compiled "pretty"

I got this problem, it was because we have a browser plugin that inserts javascript with obfuscated names too, so when the GWT calls a function like xf, it was really calling the plugin xf function.

On Monday, January 30, 2012 8:38:17 AM UTC-5, ustakraharez wrote:

Tried from the latest trunk, xs obfuscated still not working... Only
pretty .-)

Best:
Gabor

On jan. 24, 19:19, ustakraharez <ustakraha...@gmail.com> wrote:
> Thanks a lot for the quick answer!
>
> I tried with PRETTY and -optimize 9 and also optimize 0. Both of them
> worked, and the best optimization gives 5.8Mb file the worst give
> 6.5Mb so still not 2.5Mb that obfuscation gives. I try to investigate
> further tomorrow, thanks for the tip.
>
> On jan. 24, 18:07, Colin Alworth <niloc...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Compiling in PRETTY also turns off some of the optimizations, so turn them
> > back up again using -optimize 9 in your args. This will hopefully allow you
> > to reproduce the issue, but still see what the code looks like to find
> > where the error is taking place.
>
> > Seehttp://code.google.com/webtoolkit/doc/latest/DevGuideCompilingAndDebu...
> > for the full list of args that are possible.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/odxRsdxpcQIJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.