GWT code compiled with the standard linker is in an iframe but the RootPanel and widgets are in the original document. You could hack and redefine the RootPanel pointing to the iframe's document but I dont think this is a good idea because you should to redefine $wnd, $doc and write several JSNI lines.
The best solution is what you say. Use a loader module just to write an Iframe whose content is pointing to your real application. In this way both modules could be deployed in other domain, although the loader has to be compiled using the xs linker. Manolo Carrasco On Tue, Aug 25, 2009 at 4:28 PM, Jason Essington <[email protected]>wrote: > > By default, GWT already loads itself into an iFrame. I believe that > the XS linker does that as well. You don't need to do anything extra. > > -jason > On Aug 24, 2009, at 3:05 AM, John O'Conner wrote: > > > > > I've searched the GWT discussion group, but I haven't found an answer. > > As a newb with GWT, I may simply not know enough to understand the > > answer even if I've found it. :( > > > > My application runs on a customer's website. On each of their > > documents, they've embedded a single JS link to my application on a > > different domain. I'd like to load my application into a separate > > iframe which doesn't exist in their document. So, I think my entry > > point needs to create a new iframe and load itself into that iframe. > > > > My initial thought is that I probably need TWO entry points to > > accomplish this: > > 1. the first entry point will create the iframe and inject the link to > > the second entry point > > 2. the iframe loads the second entrypoint JS file > > > > Does this seem reasonable? I don't like the idea of two separate JS > > modules but it seems unavoidable. My understanding is that each entry > > point (module?) basically requires 2 GET requests: one to load the > > <module>.nocache.js and the second to load the broswer-specific JS > > that contains the application. So, with my approach, I would actually > > need FOUR (4) GET requests: > > 1. get the initial landing js file (<module1>.nocache.js) > > 2. get the js entrypoint (111111.js) that creates the iframe with a > > link to the main app > > 3. get the 2nd entry point's landing js file (<module2>.nocache.js) > > 4. get the js that contains the 2nd entrypoint (22222.js) > > > > Is there a better way? > > > > Regards, > > John O'Conner > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
