Hi Alyxandor,

  Thx a lot for very detailed explanation. infact, im using a similar
pattern you have explained regarding callback(its for a different case using
JSNI). but i have few questions here,

1. How can two Gwt Modules share a same interface(java class). i mean if i
put this common lib in some package other than client package the
compilation fails isnt it? even if i create two identical interface
definitions and place them in the client package of these different modules,
still the java package name would be different so i pass the interface
definition to one module from another module would the compiled javascript
be able to understand?

2. As these are two different modules, two will have two HTML files and im
loading these two modules as FRAME's in a parent window so if i invoke One
of the module and get the common lib code would the other module be able to
understand? please let me know if there a better way to load two different
modules in one container module.

Please let me know your views on the above two cases. your help is very much
appreciated.

Thank you,
bala.

On Sat, Oct 10, 2009 at 5:40 PM, Alyxandor <
[email protected]> wrote:

>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to