Re: Paypal Integration / JNSI
Thank you so much for the reply!
So you're calling JSNI above from the return/cancel page correct?
If so are you doing something like window.parent. paypalClose() from inside
the IFRAME that paypal insert
the return/cancel pages from?
Thanks!
On Monday, 28 May 2012 03:42:58 UTC-5, Sydney wrote:
public static native void paypalClose() /*-{
if (top top.opener top.opener.top) {
top.opener.top.dgFlow.closeFlow();
top.close();
} else if (top) {
top.dgFlow.closeFlow();
top.close();
}
}-*/;
On Sunday, May 27, 2012 8:21:25 PM UTC+2, Mayumi wrote:
How did you end up fixing this?
On Saturday, 12 May 2012 08:41:58 UTC-5, Sydney wrote:
I use the Paypal Adaptive API. So far I managed to display the paypal
page using a lightbox. But I have a problem when trying to close the
lightbox. I failed in Step 4
*3. Include the PayPal JavaScript functions from dg.js.*
*
*
*script src=https://www.paypalobjects.com/js/external/dg.js;*
*/script*
*
*
*4. Create an embedded flow object and associate it with your payment
form or button.*
*
*
*script*
*var dgFlow = new PAYPAL.apps.DGFlow({ trigger: 'submitBtn' });*
*/script*
*
*
*After Completing This Task:
*
*
*
*On the pages you identify as the return and cancel URLs in the Pay API
operation, you must*
*include the PayPal JavaScript functions from dg.js and close the
PayPal window, as in the*
*following example:*
*
*
*dgFlow = top.dgFlow || top.opener.top.dgFlow;*
*dgFlow.closeFlow();*
*top.close();*
*What I did:*
For step 4, I call the following JNSI method:
private native void paypalLight() /*-{
var dgFlow = new $wnd.PAYPAL.apps.DGFlow({
trigger : 'submitBtn'
});
}-*/;
The paypal page is displayed in the lightbox, than I click the cancel
button. My cancelURL is
http://127.0.0.1:/xxx.html?gwt.codesvr=127.0.0.1:9997#!homePage;cancel=trueand
in this page I process the cancel parameter by calling the following
JNSI:
public static native void paypalClose() /*-{
dgFlow = $wnd.top.dgFlow || $wnd.top.opener.top.dgFlow;
dgFlow.closeFlow();
$wnd.top.close();
}-*/;
When I cancel the transaction, the cancelUrl gets called, and the
paypalClose method is called. I get the error: (TypeError): $wnd.top.opener
is null.
Any ideas?
Thanks
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/VzdiU4boHuMJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Paypal Integration / JNSI
Thanks :)
On Saturday, 12 May 2012 08:41:58 UTC-5, Sydney wrote:
I use the Paypal Adaptive API. So far I managed to display the paypal page
using a lightbox. But I have a problem when trying to close the lightbox. I
failed in Step 4
*3. Include the PayPal JavaScript functions from dg.js.*
*
*
*script src=https://www.paypalobjects.com/js/external/dg.js;*
*/script*
*
*
*4. Create an embedded flow object and associate it with your payment
form or button.*
*
*
*script*
*var dgFlow = new PAYPAL.apps.DGFlow({ trigger: 'submitBtn' });*
*/script*
*
*
*After Completing This Task:
*
*
*
*On the pages you identify as the return and cancel URLs in the Pay API
operation, you must*
*include the PayPal JavaScript functions from dg.js and close the PayPal
window, as in the*
*following example:*
*
*
*dgFlow = top.dgFlow || top.opener.top.dgFlow;*
*dgFlow.closeFlow();*
*top.close();*
*What I did:*
For step 4, I call the following JNSI method:
private native void paypalLight() /*-{
var dgFlow = new $wnd.PAYPAL.apps.DGFlow({
trigger : 'submitBtn'
});
}-*/;
The paypal page is displayed in the lightbox, than I click the cancel
button. My cancelURL is
http://127.0.0.1:/xxx.html?gwt.codesvr=127.0.0.1:9997#!homePage;cancel=trueand
in this page I process the cancel parameter by calling the following
JNSI:
public static native void paypalClose() /*-{
dgFlow = $wnd.top.dgFlow || $wnd.top.opener.top.dgFlow;
dgFlow.closeFlow();
$wnd.top.close();
}-*/;
When I cancel the transaction, the cancelUrl gets called, and the
paypalClose method is called. I get the error: (TypeError): $wnd.top.opener
is null.
Any ideas?
Thanks
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/d6HspEhL7_cJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Paypal Integration / JNSI
How did you end up fixing this?
On Saturday, 12 May 2012 08:41:58 UTC-5, Sydney wrote:
I use the Paypal Adaptive API. So far I managed to display the paypal page
using a lightbox. But I have a problem when trying to close the lightbox. I
failed in Step 4
*3. Include the PayPal JavaScript functions from dg.js.*
*
*
*script src=https://www.paypalobjects.com/js/external/dg.js;*
*/script*
*
*
*4. Create an embedded flow object and associate it with your payment
form or button.*
*
*
*script*
*var dgFlow = new PAYPAL.apps.DGFlow({ trigger: 'submitBtn' });*
*/script*
*
*
*After Completing This Task:
*
*
*
*On the pages you identify as the return and cancel URLs in the Pay API
operation, you must*
*include the PayPal JavaScript functions from dg.js and close the PayPal
window, as in the*
*following example:*
*
*
*dgFlow = top.dgFlow || top.opener.top.dgFlow;*
*dgFlow.closeFlow();*
*top.close();*
*What I did:*
For step 4, I call the following JNSI method:
private native void paypalLight() /*-{
var dgFlow = new $wnd.PAYPAL.apps.DGFlow({
trigger : 'submitBtn'
});
}-*/;
The paypal page is displayed in the lightbox, than I click the cancel
button. My cancelURL is
http://127.0.0.1:/xxx.html?gwt.codesvr=127.0.0.1:9997#!homePage;cancel=trueand
in this page I process the cancel parameter by calling the following
JNSI:
public static native void paypalClose() /*-{
dgFlow = $wnd.top.dgFlow || $wnd.top.opener.top.dgFlow;
dgFlow.closeFlow();
$wnd.top.close();
}-*/;
When I cancel the transaction, the cancelUrl gets called, and the
paypalClose method is called. I get the error: (TypeError): $wnd.top.opener
is null.
Any ideas?
Thanks
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/4hYeb7drNPgJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT application freezes when new version is deployed while using it
Hi Thomas! Thanks for the reply. Freeze means the whole app becomes unresponsive (buttons are not clickable, etc) You can also observe in the developers tool that no further requests are made to the server from that point. Full refresh means F5 as you guessed. I am thinking the problem is #3 . We are using code splitting and this freeze occurs only when the code changes (meaning a new cache.js file is created meaning old once are not effective any more) On Dec 30, 6:14 am, Thomas Broyer t.bro...@gmail.com wrote: What do you mean by a freeze? and a full refresh? 1. users won't have the new version unless they refresh (F5) the page. For this though, you have to ensure the *.nocache.js is effectively not cached by browsers or proxies (or at a minimum cached with a must-revalidate condition) 2. any change to a GWT-RPC class (particularly objects that are transfered through RPC) will break older versions that are still in use, with an IncompatibleRemoteServiceException, because client and server must use the same serialization policies; you can track this to tell users to refresh the page (I guess this is what the GWT-based Google Groups UI does) 3. if you use code splitting (runAsync) and you remove the old *.cache.* files, users won't be able to download the fragments while they're using the old version of the app. You can, again, catch this in the onFailure of the RunAsyncCallback to tell users to refresh the page. 4. Every compilation should produce differently named *.cache.* files, so you can safely set long cache times for these files: http://code.google.com/webtoolkit/doc/latest/DevGuideCompilingAndDebu... -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
GWT application freezes when new version is deployed while using it
While using the GWT application, I deployed the new version of the application. Once deployment is complete my application freezes until I do the full refresh. I originally thought this was caching problem, so I assigned all the files to be no-cache by setting all response headers using the filter. But still with this filter application freezes when I deploy a new version. What could be a cause of this? What I am trying to achieve here is to be able to deploy a new version of GWT application while user is using the application. This means when the JavaScript changes I want user to get it from the server instead of using the cached one without any glitch (maybe slow response time since request need to go to the server in this case). -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT application freezes when new version is deployed while using it
This is observed when deployed with the changes in the code, so I am guessing one of the cache.js file. When deployed without any changes to a code this is not observed. On Dec 30, 12:35 am, mayumi mayumi.liyan...@gmail.com wrote: While using the GWT application, I deployed the new version of the application. Once deployment is complete my application freezes until I do the full refresh. I originally thought this was caching problem, so I assigned all the files to be no-cache by setting all response headers using the filter. But still with this filter application freezes when I deploy a new version. What could be a cause of this? What I am trying to achieve here is to be able to deploy a new version of GWT application while user is using the application. This means when the JavaScript changes I want user to get it from the server instead of using the cached one without any glitch (maybe slow response time since request need to go to the server in this case). -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
How to display unparsed html text in textarea?
I need to display raw HTML text inside the textarea without parsing it. Something like below: textarea a href=someurlClick Here/a /textarea Where I should see anchor tag and all the raw HTML tags inside the textarea. Normally you do following: textarea lt;a href=quot;someurlquot;gt;Click Herelt;/agt; /textarea Which will display the unparsed raw anchor in side the textarea. But in GWT in UiBinder `lt;a href=quot;someurlquot;gt;Click Herelt;/agt;` never gets converted to `a href=someurlClick Here/a` inside the textarea. Is there any workaround for this? Thanks! -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
GWT Anchor's visited pseudo-classes is not working on IE8, IE9.
I have GWT's anchor which contains click event to invoke some actions
programatically. I have CSS psudo-classes something like below:
a:link{ color: red }/* unvisited links */
a:visited { color: blue } /* visited links */
a:hover { color: yellow } /* user hovers */
a:active { color: lime } /* active links*/
Problem is when a link is clicked, it does not go into a:active state,
instead the CSS definition stays at a:hover. I am guessing that with
IE8 the browser does not recognize GWT's click event as a:active or
a:visited.
What exactly happens is when a link is clicked, the dialog which a
link resides hides itself and invokes another dialog. When I open the
original dialog, a link is at a:hover state.
What is a solution for this?
Thanks.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
GWT hosted mode does not work in FF4
I upgraded my FF to FF4 today and GWT hosted mode crashes with the message [ERROR] [bam] - Failed to create an instance of 'net.bookedin.bam.client.BAM' via deferred binding How can I fix this? Thanks, -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: onResize issue with IE 7
Could you please explain more in details on your workaround? I am having same problem with IE 7. Thanks. On Dec 2, 10:19 am, Magnus alpineblas...@googlemail.com wrote: Hi, I found a problem with onResize on IE 7: My panel receives an onResize, but at this point, getOffset[Width| Height] returns the old window size, not the new size. I am currently using a workaround like this: Within onResize I schedule a deferred command, which does the resize actions later, when the new window size is returned by getOffset[Width| Height]. This workaround is not nice, since I cannot hide it in some base class, but have to deal with in every derived class. In every onResize method I cannot rely on getOffset[Width|Height], so I always have to do the deferred stuff within the derived classes. Is this a known issue and can I expect a solution in the near future? Or is there a better workaround? Thank you very much! Magnus -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
GWT IE 7 Window Resizing Bug
For a GWT project I am working on, I having trouble fixing a weird IE 7 bug having to do with window resizing. Basically, when I re-size the window and change the history token(load the different section of the app) center of the app stops resizing, so sort of like becoming fixed positioning. Center of the app is styled with g:LayoutPanel with g:Layer as child element. There is no custom styling for this section of the page. So basically when you re-size the window and re-size it back to full screen, window does re-sizes but not the app (app is weirdly fixed in the previously re-sized position) Does anyone know how to fix this issue? Thanks -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: onResize issue with IE 7
A senior developer that I work with found the solution.
We used forceLayout() on LayoutPanel which will
layout the children immediately.
Thanks for the reply.
Mayumi
On Dec 3, 12:20 pm, Magnus alpineblas...@googlemail.com wrote:
Hi Mayumi,
I am happy that there is someone else struggling with this problem.
Well, within onResize I just call resizeLater:
public void onResize()
{
super.onResize();
resizeLater();
}
Ans resizeLater just schedules this action to be performed later:
private void resizeLater ()
{
Scheduler.get().scheduleDeferred
(
new ScheduledCommand()
{
public void execute()
{
myResize ();
}
}
);
}
And in myResize I do the resize actions themselves. When this method
is called, the new sizes are available through getOffset[Width|
Height].
But this is not a solution for me, since I have to deal with this
stuff in every subclass.
HTH (but I hope that someone helps me .-))
Magnus
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
