Thursday, June 2, 2016

Re: window.showModelDialog replacement

Because I don't have source code for old application so I moved the submit/action/cancel buttons out of the legacy page and used GWT to render them

I have two questions
Based on showModalDialog, must a child page have "window.returnValue = somevalue" before it is closed? 



On Wednesday, May 25, 2016 at 9:57:43 PM UTC+8, Paul Stockley wrote:
What we did in our project to migrate these kind of modal windows on IE was as follows:-

1) Create a GWT modal dialog with an iframe in it and point this to the url for the window.
2) Add some code to the existing page to talk to the parent GWT window to close the dialog when the user clicks the submit or close button

There are quite a few more details to get it working smoothly but it works well. We also moved the submit/action/cancel buttons out of the legacy page and used GWT to render them. We then call into methods in the iframe when the user clicks on the GWT buttons. 

If you need more details I can give you a few tips. Unfortunately I can't share code because we don't use standard GWT widgets.

On Wednesday, May 25, 2016 at 3:12:04 AM UTC-4, Thomas Broyer wrote:
You won't find any equivalent. The platform has moved over to an "all async" model so you'll have to rewrite this code to work asynchronously (including handling other events while waiting for the "return value" to be passed into a callback/event/whatever.

This isn't really a GWT question though, it's more about the web platform.

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment