Difficulty embedding Development mode Choosel-example in iFrame

[Jamie Starke]

I'm having a large amount of difficulty with what I thought should be
a simple problem. It seems that the main part of the problem lies in
the Development mode GWT server.

If I take the standard running URL (http://127.0.0.1:8888/index.html?
gwt.codesvr=127.0.0.1:9997) and embed it in an iframe, I receive a pop
up error "plugin failed to connect to hosted mode server at
127.0.0.1:9997", and the javascript console shows an error of "Unsafe
JavaScript attempt to access frame with URL file:///C:/Users/jstarke/Desktop/test.html
from frame with URL http://127.0.0.1:8888/org_thechiselgroup_chooselexample/hosted.html?org_thechiselgroup_chooselexample.
Domains, protocols and ports must match."

Is there a different way that I can launch Choosel to make this work?

[Lars Grammel]

Hi Jamie,

I think this might be because you loaded the page with the iframe from
your hard drive - it might be worth a try to load the page through a
http server. If you add it to the web pages in choosel mashups, it
should work. However, I am not sure if you will encounter cross-domain
issues if the iframe gets embedded in a different domain - can you
send me the example page?

Cheers,

Lars

> --
> You received this message because you are subscribed to the Google Groups "Choosel" group.
> To post to this group, send email to cho...@googlegroups.com.
> To unsubscribe from this group, send email to choosel+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/choosel?hl=en.
>
>

--
Lars Grammel
PhD Candidate, University of Victoria
http://larsgrammel.de
http://lgrammel.blogspot.com/

[Lars Grammel]

On Tue, Nov 9, 2010 at 12:30, Lars Grammel <lars.g...@googlemail.com> wrote:
> Great to hear that it works with the online version!
>
> With regards to creating a simplified version of Choosel, I thought
> about trying it the other way round: instead of removing
> functionality, start with zero functionality and just add the required
> view (I am assuming that we export single views).
>
> ChooselApplication.createMainPanel adds the main panel to the root
> panel - instead of adding the main panel, we could add the target
> view. My suggestion would be to create an if-else in the init() method
> that checks for the single-view-parameter, and if it exists, the
> simplified version gets created (and the whole desktop stuff will not
> get called).
>
> What do you think?
>
> Cheers,
>
> Lars
>
> On Tue, Nov 9, 2010 at 12:20, Jamie Starke <jrst...@gmail.com> wrote:
>> Hey Lars, it is the most simple page evar!
>> <iframe src="http://127.0.0.1:8888/index.html?gwt.codesvr=127.0.0.1:9997"
>> width="800px" height="600px">
>> Essentially, just a cheap attempt to see if I could embed it in an iframe.
>>  That being said, it works if you change the url to
>> http://choosel-mashups.appspot.com.
>> I'm also looking at the init and trying to decide what could be shut off to
>> allow for a very simplified version.  So far, I managed to turn off a number
>> of the options (see screenshot) just by commenting out it is an interesting
>> balancing act to see what else is effected when you turn something off.
>> So I know that you had wanted to save the windows (where as I was pushing
>> for saving views).  I thought of some trade offs with saving windows.  We
>> will then have to differentiate if a window is the normal window, or a saved
>> window, for things like the title of the window (should be able to change it
>> if it's saved) and the close (does it make sense to close the only window in
>> our mini-choosel?)
>> Thoughts?
>>
>> Jamie Starke
>> --
>> Research Assistant
>> CHISEL Lab
>> University of Victoria
>> www.jamiestarke.com