Myles, If your library code is JavaScript, you can always use JSNI methods in GWT to call it. You could turn off optimizations in order to make GWT produce such a JS, but GWT is designed to produce a highly-optimized JavaScript for your app, not lots of little library JavaScripts, each with potentially unused code.
I'm pretty sure a "shared library" feature has been requested on the issue tracker, but I can't find it at the moment. For the time being, code splitting (which requires a single Java code base) is the only way to break a large GWT app into multiple JavaScripts. /dmc On Wed, Dec 15, 2010 at 3:17 PM, Myles Bostwick <[email protected]> wrote: > Even if the code is not being compiled together, it seems like a library > module could be created that could then be shared by all widgets in this > scenario. Someone please correct me if I'm wrong. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- David Chandler Developer Programs Engineer, Google Web Toolkit http://googlewebtoolkit.blogspot.com/ -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
