GWT and big applications - Google Web Toolkit

Message from discussion GWT and big applications

David

More options Mar 12, 12:11 pm

From: David <david.no...@gmail.com>

Date: Wed, 12 Mar 2008 17:11:13 +0100

Local: Wed, Mar 12 2008 12:11 pm

Subject: Re: GWT and big applications

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

Hey,

It all depends on how the applications handles the screen switching
ofcourse. If you put all the screens in a big DeckPanel then I'm sure
the application will slow down when you really have a lot of screens.
But if you are smart enough and just keep the panels which state must
be preserved (when going back and forth through a flow) then the
number of screens do not have much impact.

The JavaScript file grows, but as Jason said its not linear... in fact
its hard to beat the compactness of the generated code, and if your
applications defines reusable widgets you will see a very small
increase when a screen is added. We have a large application running
in GWT and the generated code is about 100KB.

If I look at some old struts application we created in the past... I
noticed that someone managed to add a JS calendar widget that was
actually 200KB in size!

David

On Wed, Mar 12, 2008 at 4:56 PM, Jason Essington

<jason.essing...@gmail.com> wrote:

> 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