As to your questions about Module-A and Module-B, you don't HAVE to make the interfaces for Module-B available in Module-A; but if you also want to use those interfaces in Module-C, it will be more efficient to download the interfaces first, in Module-A, so both Module-B and Module-C can implement that interface knowing it won't have to duplicate the same boilerplate code. I'm going to PRETTY compile, upload to appengine and inspect to verify my inferences, then post back here, or on a more relevant thread and just post a link.
PS - The entry point I posted isn't terribly nice on the UI, as the cache.js files of both runAsync() calls block the js while they download; but it works so it makes me happy inside. A better method would be to use one runAsync() to stick an animated "loading" gif on the center of the page, then use a single callback to build the main UI, whose buttons all call runAsync() on their first click. ...Me thinks... PEACE! --Wise Words Woven With Will Wake Worlds-- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
