TimePicker setDate() + 1
Using gwt-incubator-20100204-r1747.jar
I'm calling
com.google.gwt.gen2.picker.client.TimePicker.setDate(Date), which is
supposed to set the date without affecting the time. I'm finding that
the resulting date is one day later than that which is set. I looked
at the code, and noticed a + 1, the purpose of which I don't
understand, and would explain my results. Am I missing something?
/**
* @param date the date to be set. Only the date part will be set,
the time
* part will not be affected
*/
public void setDate(Date date) {
// Only change the date part, leave time part untouched
dateInMillis = (long) ((Math.floor(date.getTime() / DAY_IN_MS) +
1) * DAY_IN_MS)
+ dateInMillis % DAY_IN_MS;
for (TimeSpinner spinner : timeSpinners) {
spinner.getSpinner().setValue(dateInMillis, false);
}
}
--
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: Major memory leak with RPC, Internet Explorer and GWT 2.0 (MS1 MS2)
Sorry, I thought the XMLHttpRequests weren't leaking, but apparently
they still might be.
Here's what I did:
Google Chrome 4.0.249.22 (Development version)
GWT 2.0.0 RC2
Created GWT app: webAppCreator -out MemTest memtest.MemTest
Added this to onModuleLoad():
Timer timer = new Timer() {
@Override
public void run() {
greetingService.greetServer(xxx, new AsyncCallbackString() {
public void onFailure(Throwable caught) {
}
public void onSuccess(String result) {
}
});
}
};
timer.scheduleRepeating(1 * 1000);
Ran the generated MemTest launcher (OOPHM) and clicked Launch Default
Browser (Chrome).
After a couple hours, the mem was 50MB+ (according to Task
manager/Stats for nerds) and Page/Developer/Developer Tools/
Profiles/Heap Snapshot indicated 2500+ instances of XMLHttpRequest.
Though, the snapshot indicated that only 5MB or so of memory was being
used, so I don't know what is using the other 45MB+.
I also opened a OOPHM session in IE8, and the same steady memory
increase was observed (though the growth was actually slower).
On Dec 4, 3:32 pm, mrpantsuit kevin.peter.w...@gmail.com wrote:
Regarding theXMLHttpRequestleak, it seems I just need to wait for
the garbage collector to run. Does anyone know how to manually
initiate garbage collection in Chrome (or in the other browsers, for
that matter)?
On Dec 4, 2:41 pm, mrpantsuit kevin.peter.w...@gmail.com wrote:
I downloaded the Developer Channel version of Chrome, which has some
nice heap analysis developer tools. I thought that perhaps my memory
leaks were not restricted to IE, but were simply more pronounced on
it. Turns out I had several memory leaks.
I changed to use the GWT incubator progress bar instead of the GWT Ext
one, which seemed to reduce the IE leakage significantly. I don't
know theleakis inherent to the GWT Ext progress bar, or perhaps I
was just using it wrong.
I also noticed that I was leaking XMLHttpRequests. I rebuilt with GWT
2.0 RC2, but theleakpersisted. I'm still investigating that one.
I was also leaking HTTPCollections. I have a FlexTable that I rebuild
every few seconds after RPCing data from the server. I'm still
investigating that one, too.
Thanks,
Kevin
On Dec 3, 11:59 am, Chris Ramsdale cramsd...@google.com wrote:
A diff on com.google.gwt.xhr.client.XMLHttpRequestshould give you an idea
of what code has changed and when it changed. That said, Rob points out
earlier in this thread that he is not seeing the issue in 1.7.
Are you in a position where you could build your app with RC2 to see if
the
leakgoes away?
On Thu, Dec 3, 2009 at 11:35 AM, mrpantsuit
kevin.peter.w...@gmail.comwrote:
I'm seeing a similar memoryleakin 1.7. Does anyone know if this bug
predated 2.0, or was it introduced therein?
On Nov 14, 11:28 am, Rob rob.a.st...@gmail.com wrote:
Seehttp://code.google.com/p/google-web-toolkit/issues/detail?id=4133
andhttp://code.google.com/p/google-web-toolkit/issues/detail?id=4229
Issue 4133 was raised almost a month ago but doesn't seem to have been
acknowledged yet - would anyone from the GWT team care to comment ?
Cheers
Rob
On Nov 13, 2:18 pm, Rob rob.a.st...@gmail.com wrote:
I've been trying out one of my existing apps with GWT 2.0 to see
what
advantages it has and have noticed a majormemoryleakwhen using RPC
with Internet Explorer 8.0.
Basically my application reads some values from a database and
displays these in the browser every 1 second. I am seeing amemory
leakof 16k per second -i.e.every time I make an RPC request the
browser leaks 16k ofmemory. This eventually leads to an out of
virtualmemorysystem error. If I switch back to using GWT 1.7 then
the problem goes away, there are no leaks at all.
I have managed to reproduce the problem with a very simple RPC
example
which I can supply if required.
Has anyone else noticed anything similar ?
Cheers
Rob
--
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.comgoogle-web-toolkit%2Bunsubs
cr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
--
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
Re: Major memory leak with RPC, Internet Explorer and GWT 2.0 (MS1 MS2)
Oh, eventually windows reports that Chrome has crashed, though
dismissing the error leaves Chrome open (strange). Developer Tools/
Scrips shows an error like this every second (the same period as the
RPC timer set up in onModuleLoad() ):
Uncaught Error: Error calling method on NPObject!
On Dec 7, 3:05 pm, mrpantsuit kevin.peter.w...@gmail.com wrote:
Sorry, I thought the XMLHttpRequests weren't leaking, but apparently
they still might be.
Here's what I did:
Google Chrome 4.0.249.22 (Development version)
GWT 2.0.0 RC2
Created GWT app: webAppCreator -out MemTest memtest.MemTest
Added this to onModuleLoad():
Timer timer = new Timer() {
@Override
public void run() {
greetingService.greetServer(xxx, new
AsyncCallbackString() {
public void onFailure(Throwable caught) {
}
public void onSuccess(String result) {
}
});
}
};
timer.scheduleRepeating(1 * 1000);
Ran the generated MemTest launcher (OOPHM) and clicked Launch Default
Browser (Chrome).
After a couple hours, the mem was 50MB+ (according to Task
manager/Stats for nerds) and Page/Developer/Developer Tools/
Profiles/Heap Snapshot indicated 2500+ instances ofXMLHttpRequest.
Though, the snapshot indicated that only 5MB or so of memory was being
used, so I don't know what is using the other 45MB+.
I also opened a OOPHM session in IE8, and the same steady memory
increase was observed (though the growth was actually slower).
On Dec 4, 3:32 pm, mrpantsuit kevin.peter.w...@gmail.com wrote:
Regarding theXMLHttpRequestleak, it seems I just need to wait for
the garbage collector to run. Does anyone know how to manually
initiate garbage collection in Chrome (or in the other browsers, for
that matter)?
On Dec 4, 2:41 pm, mrpantsuit kevin.peter.w...@gmail.com wrote:
I downloaded the Developer Channel version of Chrome, which has some
nice heap analysis developer tools. I thought that perhaps my memory
leaks were not restricted to IE, but were simply more pronounced on
it. Turns out I had several memory leaks.
I changed to use the GWT incubator progress bar instead of the GWT Ext
one, which seemed to reduce the IE leakage significantly. I don't
know theleakis inherent to the GWT Ext progress bar, or perhaps I
was just using it wrong.
I also noticed that I was leaking XMLHttpRequests. I rebuilt with GWT
2.0 RC2, but theleakpersisted. I'm still investigating that one.
I was also leaking HTTPCollections. I have a FlexTable that I rebuild
every few seconds after RPCing data from the server. I'm still
investigating that one, too.
Thanks,
Kevin
On Dec 3, 11:59 am, Chris Ramsdale cramsd...@google.com wrote:
A diff on com.google.gwt.xhr.client.XMLHttpRequestshould give you an
idea
of what code has changed and when it changed. That said, Rob points out
earlier in this thread that he is not seeing the issue in 1.7.
Are you in a position where you could build your app with RC2 to see if
the
leakgoes away?
On Thu, Dec 3, 2009 at 11:35 AM, mrpantsuit
kevin.peter.w...@gmail.comwrote:
I'm seeing a similar memoryleakin 1.7. Does anyone know if this bug
predated 2.0, or was it introduced therein?
On Nov 14, 11:28 am, Rob rob.a.st...@gmail.com wrote:
Seehttp://code.google.com/p/google-web-toolkit/issues/detail?id=4133
andhttp://code.google.com/p/google-web-toolkit/issues/detail?id=4229
Issue 4133 was raised almost a month ago but doesn't seem to have
been
acknowledged yet - would anyone from the GWT team care to comment ?
Cheers
Rob
On Nov 13, 2:18 pm, Rob rob.a.st...@gmail.com wrote:
I've been trying out one of my existing apps with GWT 2.0 to see
what
advantages it has and have noticed a majormemoryleakwhen using RPC
with Internet Explorer 8.0.
Basically my application reads some values from a database and
displays these in the browser every 1 second. I am seeing amemory
leakof 16k per second -i.e.every time I make an RPC request the
browser leaks 16k ofmemory. This eventually leads to an out of
virtualmemorysystem error. If I switch back to using GWT 1.7 then
the problem goes away, there are no leaks at all.
I have managed to reproduce the problem with a very simple RPC
example
which I can supply if required.
Has anyone else noticed anything similar ?
Cheers
Rob
--
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.comgoogle-web
Re: Major memory leak with RPC, Internet Explorer and GWT 2.0 (MS1 MS2)
I downloaded the Developer Channel version of Chrome, which has some nice heap analysis developer tools. I thought that perhaps my memory leaks were not restricted to IE, but were simply more pronounced on it. Turns out I had several memory leaks. I changed to use the GWT incubator progress bar instead of the GWT Ext one, which seemed to reduce the IE leakage significantly. I don't know the leak is inherent to the GWT Ext progress bar, or perhaps I was just using it wrong. I also noticed that I was leaking XMLHttpRequests. I rebuilt with GWT 2.0 RC2, but the leak persisted. I'm still investigating that one. I was also leaking HTTPCollections. I have a FlexTable that I rebuild every few seconds after RPCing data from the server. I'm still investigating that one, too. Thanks, Kevin On Dec 3, 11:59 am, Chris Ramsdale cramsd...@google.com wrote: A diff on com.google.gwt.xhr.client.XMLHttpRequest should give you an idea of what code has changed and when it changed. That said, Rob points out earlier in this thread that he is not seeing the issue in 1.7. Are you in a position where you could build your app with RC2 to see if the leak goes away? On Thu, Dec 3, 2009 at 11:35 AM, mrpantsuit kevin.peter.w...@gmail.comwrote: I'm seeing a similar memory leak in 1.7. Does anyone know if this bug predated 2.0, or was it introduced therein? On Nov 14, 11:28 am, Rob rob.a.st...@gmail.com wrote: Seehttp://code.google.com/p/google-web-toolkit/issues/detail?id=4133 andhttp://code.google.com/p/google-web-toolkit/issues/detail?id=4229 Issue 4133 was raised almost a month ago but doesn't seem to have been acknowledged yet - would anyone from the GWT team care to comment ? Cheers Rob On Nov 13, 2:18 pm, Rob rob.a.st...@gmail.com wrote: I've been trying out one of my existing apps with GWT 2.0 to see what advantages it has and have noticed a majormemoryleakwhen using RPC with Internet Explorer 8.0. Basically my application reads some values from a database and displays these in the browser every 1 second. I am seeing amemory leakof 16k per second -i.e.every time I make an RPC request the browser leaks 16k ofmemory. This eventually leads to an out of virtualmemorysystem error. If I switch back to using GWT 1.7 then the problem goes away, there are no leaks at all. I have managed to reproduce the problem with a very simple RPC example which I can supply if required. Has anyone else noticed anything similar ? Cheers Rob -- 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.comgoogle-web-toolkit%2Bunsubs cr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- 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: Major memory leak with RPC, Internet Explorer and GWT 2.0 (MS1 MS2)
Regarding the XMLHttpRequest leak, it seems I just need to wait for the garbage collector to run. Does anyone know how to manually initiate garbage collection in Chrome (or in the other browsers, for that matter)? On Dec 4, 2:41 pm, mrpantsuit kevin.peter.w...@gmail.com wrote: I downloaded the Developer Channel version of Chrome, which has some nice heap analysis developer tools. I thought that perhaps my memory leaks were not restricted to IE, but were simply more pronounced on it. Turns out I had several memory leaks. I changed to use the GWT incubator progress bar instead of the GWT Ext one, which seemed to reduce the IE leakage significantly. I don't know theleakis inherent to the GWT Ext progress bar, or perhaps I was just using it wrong. I also noticed that I was leaking XMLHttpRequests. I rebuilt with GWT 2.0 RC2, but theleakpersisted. I'm still investigating that one. I was also leaking HTTPCollections. I have a FlexTable that I rebuild every few seconds after RPCing data from the server. I'm still investigating that one, too. Thanks, Kevin On Dec 3, 11:59 am, Chris Ramsdale cramsd...@google.com wrote: A diff on com.google.gwt.xhr.client.XMLHttpRequestshould give you an idea of what code has changed and when it changed. That said, Rob points out earlier in this thread that he is not seeing the issue in 1.7. Are you in a position where you could build your app with RC2 to see if the leakgoes away? On Thu, Dec 3, 2009 at 11:35 AM, mrpantsuit kevin.peter.w...@gmail.comwrote: I'm seeing a similar memoryleakin 1.7. Does anyone know if this bug predated 2.0, or was it introduced therein? On Nov 14, 11:28 am, Rob rob.a.st...@gmail.com wrote: Seehttp://code.google.com/p/google-web-toolkit/issues/detail?id=4133 andhttp://code.google.com/p/google-web-toolkit/issues/detail?id=4229 Issue 4133 was raised almost a month ago but doesn't seem to have been acknowledged yet - would anyone from the GWT team care to comment ? Cheers Rob On Nov 13, 2:18 pm, Rob rob.a.st...@gmail.com wrote: I've been trying out one of my existing apps with GWT 2.0 to see what advantages it has and have noticed a majormemoryleakwhen using RPC with Internet Explorer 8.0. Basically my application reads some values from a database and displays these in the browser every 1 second. I am seeing amemory leakof 16k per second -i.e.every time I make an RPC request the browser leaks 16k ofmemory. This eventually leads to an out of virtualmemorysystem error. If I switch back to using GWT 1.7 then the problem goes away, there are no leaks at all. I have managed to reproduce the problem with a very simple RPC example which I can supply if required. Has anyone else noticed anything similar ? Cheers Rob -- 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.comgoogle-web-toolkit%2Bunsubs cr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- 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: Major memory leak with RPC, Internet Explorer and GWT 2.0 (MS1 MS2)
I'm seeing a similar memory leak in 1.7. Does anyone know if this bug predated 2.0, or was it introduced therein? On Nov 14, 11:28 am, Rob rob.a.st...@gmail.com wrote: Seehttp://code.google.com/p/google-web-toolkit/issues/detail?id=4133 andhttp://code.google.com/p/google-web-toolkit/issues/detail?id=4229 Issue 4133 was raised almost a month ago but doesn't seem to have been acknowledged yet - would anyone from the GWT team care to comment ? Cheers Rob On Nov 13, 2:18 pm, Rob rob.a.st...@gmail.com wrote: I've been trying out one of my existing apps with GWT 2.0 to see what advantages it has and have noticed a majormemoryleakwhen using RPC with Internet Explorer 8.0. Basically my application reads some values from a database and displays these in the browser every 1 second. I am seeing amemory leakof 16k per second -i.e.every time I make an RPC request the browser leaks 16k ofmemory. This eventually leads to an out of virtualmemorysystem error. If I switch back to using GWT 1.7 then the problem goes away, there are no leaks at all. I have managed to reproduce the problem with a very simple RPC example which I can supply if required. Has anyone else noticed anything similar ? Cheers Rob -- 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.
incubator gen2 vs. widgetideas
There is a SliderBar in both com.google.gwt.gen2.picker.client and com.google.gwt.widgetideas.client. Which one should I use? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
ImageBundle reuse images
This might be a stupid question, but can I use the same Image created from an ImageBundle in multiple places on my page? I guess the more general question is can I use the same Image in multiple places in my page. I assume so. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Scriptaculous appear effect with PNG with transparency shows black background on IE
I'm actually using the GWT Widget Library's Effect class, which has an Effect.appear(Widget) method. On IE, When the widget is an Image that's a PNG with transparency, while the effect is animating the background of the image shows black. The same applies for other transparency effects, e.g., Effect.pulsate(), etc. This doesn't occur when the image is retrieved from an ImageBundle with only one image. If I add other images to the ImageBundle, the problem returns. (Also, if I use an image created with the Image (String) constructor, the problem occurs.) Thus, as a workaround, for each image that will have an Effect animation applied, I create a new ImageBundle. Does anyone know what's going on here? Does anyone have a better solution? 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 -~--~~~~--~~--~--~---
button with image AND text
I want an HTML button with and image AND text. I could use a control form a widget library, but I want my button to be a native HTML button. Anyone know how to do this? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
TextBox with label inside
I want a GWT control that's a TextBox with the label as light grey text inside the field (as opposed to beside it). You know, so you see what the field's for, but it saves space. And when you click inside the text box, the light grey label disappears. Anyone know if there's a widget library with something like that? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
IE6 PNG transparency fixes for CSS images
I can't seem to get any of the IE6 PNG transparency fixes (SuperSleight, unitpngfix, http://www.komodomedia.com/blog/2007/11/css-png-image-fix-for-ie/) working in my GWT app. (Note that my PNGs are specified in my CSS, so solutions like PNGImage won't help.) Has anyone gotten any of these working? --~--~-~--~~~---~--~~ 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: getting Content-Type must be 'text/x-gwt-rpc' with 'charset=utf-8' after updating to gwt 1.5RC1
I had the same problem and fixed it by doing a Ctrl-F5 refresh in the browser. On Aug 11, 6:56 am, TimTimGo [EMAIL PROTECTED] wrote: Hi, after updating to gwt 1.5, I'm getting this error: 2008-08-11 12:16:33.899:/:WARN: Exception while dispatching incoming RPC call javax.servlet.ServletException: Content-Type must be 'text/x-gwt-rpc' with 'charset=utf-8'. at com.google.gwt.user.server.rpc.RPCServletUtils.readContentAsUtf8(RPCServlet Utils.java: 141) at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceSer vlet.java: 76) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java: 443) ... (and so on) I already read similar postings in this google group, but they didn't adress excactly this error. For examplehttp://groups.google.com/group/Google-Web-Toolkit/browse_thread/threa... . The difference is that the error message in this discussion is Content Type must be text/plain and my error message is Content Type must be 'text/x-gwt-rpc'. I figured the proposed solution to replace the server libraries would work for me too. Thus I replaced client jars and also server jars. Nevertheless, I still get this errormessage. Maybe I forgot to update a library somewhere. Actually, I don't believe that, as I created a new project completely with gwt 1.5. I guessed this way gwt should use the new libraries, but the error still keeps showing up. I really don't know how to solve this, but maybe you professionals here have another clue for me. I guess for helping me, you will need some information about my setup: For development, I'm using Cypal Studio for gwt in Eclipse. This will compile the gwt project. As server, I use an embedded jetty in an eclipse application. I deploy the service servlet as well as the static content which is in the gwtOutput directory to this. Thanks for helping TimTimGo --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
