Re: How to resize the layer of a DeckLayoutPanel when showing the layer after it has been hidden

2015-08-19 Thread rkvaja
Thanks jaga.

I have actually got a Absolute panel in the layer. This has a width and 
height of 100%. The child of the absolute panel is another absolute panel 
(restricted here as I am doing drag and drop using the GWT D'N'D library). 
It is the child absolute panel which is ending up with a height of zero.

I'm not entirely sure but I may have to create an extension of 
AbsolutePanel that imlpements the ProvidesResize method by the sounds of it.

On Saturday, 25 July 2015 09:15:33 UTC+1, jaga wrote:

 Try onResize or forceLayout. The problem might be that u are using a flow 
 type widget within the layout panel. In that case try setting width height 
 to 100%. Also, if you are using a LayoutPanel for your child widget then 
 you could inherit from ResizeComposite. That will give u the required 
 interfaces and the correct onResize method.

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


FileUpload and Content-Disposition

2015-08-19 Thread ehodges
I'm trying to upload a file to a servlet using the example provided 
on 
http://www.gwtproject.org/javadoc/latest/com/google/gwt/user/client/ui/FileUpload.html.
 
 The multipart request arrives at the servlet, but the attachment doesn't 
have a Content-Disposition header.  I can't find any way to set it.  Any 
suggestions?

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


Re: GWT release prioritization

2015-08-19 Thread steve Zara
Yes, this would be helpful.

On Monday, 10 August 2015 11:33:42 UTC+1, James Horsley wrote:

 Any chance someone from the steering committee could comment on this?

 On 3 August 2015 at 09:37, maticpetek matic...@gmail.com javascript: 
 wrote:

 1+


 On Friday, July 31, 2015 at 11:39:00 AM UTC+2, James Horsley wrote:

 Firstly, I am very much looking forward to the next generation j2cl 
 compiler for GWT and think the new compiler vision is great. That said, I 
 think the community would benefit greatly with the steering committee 
 placing a higher priority on closing out on the 2.8 release. I know that 
 the current 2.8 is considered usable for production but 2.8 isn't feature 
 complete and organizations can be very hesitant to use non-GA versions of 
 libraries. In particular it would be a big win to have a done version of 
 JsInterop v1 and clear guidance on using the current version of elemental.

 I, and I'm sure the rest of the GWT community, would greatly appreciate 
 a clearer view on current release expectations and prioritization; is there 
 anything you guys can share on that front?

 Again, really appreciate the recent work and love the plans for GWT 3.0.

 Cheers,
 James

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




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


Re: GWT release prioritization

2015-08-19 Thread Nagin
Yes, I agree too
+1 for this

On Thursday, August 20, 2015 at 1:21:41 AM UTC+5:30, steve Zara wrote:

 Yes, this would be helpful.

 On Monday, 10 August 2015 11:33:42 UTC+1, James Horsley wrote:

 Any chance someone from the steering committee could comment on this?

 On 3 August 2015 at 09:37, maticpetek matic...@gmail.com wrote:

 1+


 On Friday, July 31, 2015 at 11:39:00 AM UTC+2, James Horsley wrote:

 Firstly, I am very much looking forward to the next generation j2cl 
 compiler for GWT and think the new compiler vision is great. That said, I 
 think the community would benefit greatly with the steering committee 
 placing a higher priority on closing out on the 2.8 release. I know that 
 the current 2.8 is considered usable for production but 2.8 isn't feature 
 complete and organizations can be very hesitant to use non-GA versions of 
 libraries. In particular it would be a big win to have a done version of 
 JsInterop v1 and clear guidance on using the current version of elemental.

 I, and I'm sure the rest of the GWT community, would greatly appreciate 
 a clearer view on current release expectations and prioritization; is 
 there 
 anything you guys can share on that front?

 Again, really appreciate the recent work and love the plans for GWT 3.0.

 Cheers,
 James

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




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


Re: GWT release prioritization

2015-08-19 Thread Nagin Kothari
Yes, I agree
+1 for this

On Thu, Aug 20, 2015 at 1:21 AM, steve Zara steve.z...@googlemail.com
wrote:

 Yes, this would be helpful.

 On Monday, 10 August 2015 11:33:42 UTC+1, James Horsley wrote:

 Any chance someone from the steering committee could comment on this?

 On 3 August 2015 at 09:37, maticpetek matic...@gmail.com wrote:

 1+


 On Friday, July 31, 2015 at 11:39:00 AM UTC+2, James Horsley wrote:

 Firstly, I am very much looking forward to the next generation j2cl
 compiler for GWT and think the new compiler vision is great. That said, I
 think the community would benefit greatly with the steering committee
 placing a higher priority on closing out on the 2.8 release. I know that
 the current 2.8 is considered usable for production but 2.8 isn't feature
 complete and organizations can be very hesitant to use non-GA versions of
 libraries. In particular it would be a big win to have a done version of
 JsInterop v1 and clear guidance on using the current version of elemental.

 I, and I'm sure the rest of the GWT community, would greatly appreciate
 a clearer view on current release expectations and prioritization; is there
 anything you guys can share on that front?

 Again, really appreciate the recent work and love the plans for GWT 3.0.

 Cheers,
 James

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


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




-- 
Nagin Kothari
Co-founder,
Zilicus Solutions
www.zilicus.com

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


Re: Chrome and SEVERE: CLIENT EXCEPTION: com.google.gwt.user.client.rpc.StatusCodeException: 0

2015-08-19 Thread Jens


 Thanks for the reply. This error happens intermittently (and very often) 
 while there is definitely no problem with network connections. It starts 
 after upgrading to Chrome version 44. Clearing browser cache can stop the 
 problem from happening for a while (about an hour), then it happens again 
 very often.


Without changing anything in the app code and without deploying the app on 
the server? Then its probably a Chrome issue. GWT doesn't do any magic when 
making a server request. 

While its not really related to cache cleaning but do you know if your 
server supports SPDY (the Google protocol that was the foundation of 
HTTP/2) ? We had some issues with Statuscode 0 exceptions with Chrome + 
SPDY server in the past and had to disable SPDY on the server. Maybe its a 
SPDY / HTTP2 issue between Chrome and your server. In Chrome you can type 
chrome://net-internals into your address bar for more connection 
information.

-- J.

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


Re: Chrome and SEVERE: CLIENT EXCEPTION: com.google.gwt.user.client.rpc.StatusCodeException: 0

2015-08-19 Thread Thomas Broyer
You should find a bit more info (not necessarily useful, but you won't know 
until you see it) in the Network tab in the Chrome Developer Tools.
A status=0 might also mean that the request has been aborted.

On Wednesday, August 19, 2015 at 12:23:58 AM UTC+2, Mandy Shen wrote:

 Thanks for the reply. This error happens intermittently (and very often) 
 while there is definitely no problem with network connections. It starts 
 after upgrading to Chrome version 44. Clearing browser cache can stop the 
 problem from happening for a while (about an hour), then it happens again 
 very often.

 On Tuesday, August 18, 2015 at 2:01:07 PM UTC-7, Jens wrote:

 The exception means that your Browser can't reach your server. It does 
 not get a server response with a HTTP status code and thus 0 is used.

 I would guess its an issue with your server, network or DNS.

 -- J.



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