Main page (dataApp.html, loaded as a single module, single entry
point) is the main application I am running.
In a variety of views I would like to give the user the option of
"popping out" the current data detail view, much the same way that
GMail allows you to pop out the e-mail composition window. I would
like to retain the full and normal use of the classes and
functionality in the popout window. Basically, I want to load a
class, ExternalViewer, in the popout window. I am not looking for a
panel within the root window, but a true separate browser window.
Any help or pointers as to where to read would be much appreciated.
Thanks in advance,
Jeff
Thanks, that is what I had learned from reading the previous
discussions. I guess my question then becomes how do I associate
multiple HTML pages with one GWT app? I assume this has to be done
with multiple modules and multiple entry points. I think I may have
had this solution working, but the development environment didn't seem
to work well, ie, it would only compile and run one module/entrypoint
at a time and for me to test if it is actually working both need to
work at the same time.
I am hesitant to load my entire application again and do a check to
see if it is running in the popup window, as it is rather huge (my
gwtOutput folder is 5.62MB).
After passing the initial object to display in the popup window, most
of the client interaction takes place over an RPC link. Thus, I'm not
too worried about sending messages back and forth between the two
windows. I would think from the perspective of development and
maintenance, having everything in the same application and accessing
the same set of common widgets would be optimal.
The list of things I'm stuck on:
1. Setting up GWT to handle multiple entrypoints and having one of the
modules load the other one
2. Sending the initial data item to the new window to be popped out.
3. Having the development and build environments handle the
interaction of multiple modules smoothly for testing.
Jeff
I think I may have had this solution working, but the development environment didn't seem
to work well, ie, it would only compile and run one module/entrypoint
at a time and for me to test if it is actually working both need to
work at the same time.
The list of things I'm stuck on:
1. Setting up GWT to handle multiple entrypoints and having one of the
modules load the other one
2. Sending the initial data item to the new window to be popped out.
3. Having the development and build environments handle the
interaction of multiple modules smoothly for testing.
Thanks so much for this. You have really helped enlighten me as to
the functional underpinnings of the toolkit.
The solution with multiple entry point and the check for parent or
child is exactly the combination I was looking for. I will use RPC
calls to handle the data transfer (not hard at all in my case as I am
already doing a lot with session management and session user data
persistence).
Thanks for the note about not sharing even static classes, that is
definitely good to know!
Thanks so much for your help on this, I really appreciate it.
Jeff
> - Write a new module called Bar that has a different entry point but
> may share classes with Foo
> - Add a second entry point class to Foo that implements your child
Thanks so much for this. You have really helped enlighten me as to
the functional underpinnings of the toolkit.
The solution with multiple entry point and the check for parent or
child is exactly the combination I was looking for. I will use RPC
calls to handle the data transfer (not hard at all in my case as I am
already doing a lot with session management and session user data
persistence).
Thanks for the note about not sharing even static classes, that is
definitely good to know!
Thanks so much for your help on this, I really appreciate it.
Jeff
> - Write a new module called Bar that has a different entry point but
> may share classes with Foo
> - Add a second entry point class to Foo that implements your child
> your child's would do a RootPanel.get ("child"). That method returns null if
Thanks again for the help.
Jeff
On Mar 19, 5:02 pm, "Ian Bambury" <ianbamb...@gmail.com> wrote:
> Jeff,
>
> I'm just going to stick an oar in here...
>
> There's no reason why you can't have two different HTML pages run the same
> GWT app (thereby not having to load a different cache.html file) but
> reacting in different ways.
>
> If your standard index.htm page opened another (pop.htm) page and passed it
> a querystring, then pop.htm could just display the widget you wanted with
> the data you passed it. This would have to be relatively simple data, of
> course.
>
> You could also have pop.htm go and get data from the index.htm window, or
> for that matter, great chunks of the DOM. The only problem with that is that
> you will lose clicklisteners and similar effects and have to rebuild them,
> since (obviously) the clicklistener isn't all that available in the popped
> up window.
>
> I've tried this and it works.http://write.roughian.com uses this principle
> (albeit with iframes) to add to the parent DOM. Above the 3px blue line is
> the main page, below is in iframes. I'm still adding loads of text to this
> so it's not all there, but if you go to, say, Act I, and click an item in
> the side menu (i.e. in the iframe), it changes a field in the
> index.htm(parent) frame. It could just as easily fetch data as send
> it.
>
> Ianhttp://examples.roughian.com