I've done quite a bit of searching to find any information about this, but it seems that people are more concerned with writing GWT libraries to keep in GWT before compilation.
I would like to write the libraries I frequently use in my projects in GWT, then compile and expose them to hand-written Javascript. I have several issues with the way GWT seems to handle what I want to do: 1) Bootstrapping. I understand that the iframe loading method is highly efficient for large codebases so as to make the page non- blocking, but for a small library bootstrapping is overkill. To test, I tried writing my TableGenerator library (a 7kb handwritten non- minified library) in GWT. The result was a 6 kb deferred binding loader file (table.nocache.js) and 4 permutations of compiled JS weighing in at 20-30kb each. Which brings me to issue #2 2) For compiling the code, GWT seems to produce LARGER codebases. Fast, yes, but how does 3-5kb of source result in 20-30kb of compiled javascript? Is there a way to crop out all the unnecessary cruft GWT seems to think I need? 3) I would prefer to not have a bootloader - I anticipate the compiled form of my code is going to be smaller than the bootstrap code and would rather it just be loaded. Is there a compilation option to disable permutations and output (obviously more to handle different implementations) code that works in all browsers? Sincerely, Scott Rabin -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
