GWT and big applications - Google Web Toolkit

Message from discussion GWT and big applications

Jason Essington

More options Mar 12, 11:56 am

From: Jason Essington <jason.essing...@gmail.com>

Date: Wed, 12 Mar 2008 09:56:57 -0600

Local: Wed, Mar 12 2008 11:56 am

Subject: Re: GWT and big applications

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

As it turns out, the size of the javascript doesn't increase linearly
with the size of the application.

As you begin to reuse widgets on additional "forms" you don't incur
additional bytecount for that reuse, so large applications tend to be
just fine in GWT.

I have yet to hear of anyone who as had the javascript payload of
their large application overrun the available memory in the client
browser.

Overall, the one module (page, project) per form idea that is
typically used for server side technologies is particularly
inefficient when it comes to GWT because you will end up not
benefiting from code reuse (talking about the compiled javascript
here), and your overall byte count will likely be quite a lot larger.

-jason
On Mar 12, 2008, at 2:03 AM, mrblue wrote:

> How GWT works with applicactions which have about 50-70 screens
> (forms)? It should be created on one page? I think I'll have a lot of
> JS and my GWT application will work very slow.

Reply to author Forward