How to see generated JS code before its sent to linking step.

28 views
Skip to first unread message

Marko Vuksanovic

unread,
Jul 10, 2011, 2:30:26 AM7/10/11
to google-we...@googlegroups.com
Hi,

I wanted to see what was getting generated by CompilePerms step and sent to linker. For that purpose I executed Precompile and CompilePerms steps manually. I got hold of permutation-x.js files. When I opened any of those files in text editor the output was not readable. The problem was not code obfuscation but weird characters in the file. How can I get those js files output in some format with ASCII characters? Or is there some other way I can get to JS files that are actually input to Linker?

Marko

Thomas Broyer

unread,
Jul 10, 2011, 5:05:53 AM7/10/11
to google-we...@googlegroups.com
How about using a Linker with @LinkOrder(Order.PRE) and output the artifacts' content from there?

Marko Vuksanovic

unread,
Jul 10, 2011, 5:36:42 AM7/10/11
to google-we...@googlegroups.com
That's one of options I had in mind. I was hoping there is a way to read the actual content of permutation-x.js files :)


On Jul 10, 2011, at 11:07 AM, Thomas Broyer <t.br...@gmail.com> wrote:

How about using a Linker with @LinkOrder(Order.PRE) and output the artifacts' content from there?

--
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/-/tmP5xdoC2NsJ.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

Thomas Broyer

unread,
Jul 10, 2011, 7:13:19 AM7/10/11
to google-we...@googlegroups.com
Quickly looking at the code, they're probably FileBasedObjects, i.e. using Java serialization.
Reply all
Reply to author
Forward
0 new messages