I may not be understanding your question. GWT will compile your code into whatever Javascript is actually used.
So when GWT compiles your user's code, if they don't use the parts that rely on the optional library, they won't get that library automagically, AFAIK, by the GWT compiler recognizing this. Caveat: The inherits stuff in the module configuration might still cause code to be compiled, but the dead-code elimination in the compiler should cause it to not be included in the result, thus your user's code should have those optional libraries omitted. If you care about compilation-speed, you'd have to have the user edit your gwt.xml file to include only the modules used by your code they rely on. Perhaps someone more familiar with the internals of the gwt compiler can comment as to whether or not my explanation is correct or way off base. On Sun, Mar 15, 2009 at 12:28 AM, John Gunther <[email protected]>wrote: > > Is it possible to release a GWT library that has optional features > that require an additional library (written by someone else, packaged > in a module JAR) but that does not require its users to load that > additional library if they don't need the optional features? > > What is the best way to do this that results in users of the library > having the least number of steps to configure it with or without the > optional features? > > John > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
