Re: Source maps

On Monday, April 2, 2012 10:17:15 AM UTC+2, Honza Rames wrote:

Thanks cool, this way it works just fine, I also had to symlink my java sources so the browser could access them, you can do this by creating a symlink to you com (org or whatever package you use as base) in you war/<project-name> folder (where the cache.htmls are generated and where you copy source maps to). It would probably be a lot better to have a servlet that can handle fetching the sources and also a modified linker that adds the sourceMappingURL to the generated JS (I guess this gets more complicated when code splitting is in play).

According to http://code.google.com/p/google-web-toolkit/source/detail?r=10760 only the xsiframe linker (<add-linker name='xsiframe'/>) will output the //@ sourceUrl=…

It's also only used for stack-trace deobfuscation (as is said on the wiki page), which is why it doesn't Just Work™ with Chrome's Developer Tools' support for Source Maps (no //@ sourceMappingURL=…, and the generated artifacts are not publicly accessible)

It also won't work if you use the experimental Closure Compiler backend.

--
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/-/98YPPJoosJQJ.
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.