Re: Full page in GWT or just parts?

@Uemit: I agree but not completely as your comment aren't suited for
larger app's (in my case).

Don't forget that the current code splitting isn't perfect such that
the left-over fragment can become rather large, as in my case.
As such, that the simple login screen results with a big initial load,
whereas if I split it from the core application part, it becomes very
small. This is important as you don't want the user to wait too long
for the login screen to appear.

But of course I would like to make it as one gwt app, but this
currently results in bad results.

Apart from the code reuse, for me at this moment it's all about
resource management that GWT performs well as explained above.

- Ed

On Oct 12, 3:28 pm, Uemit <uemit.se...@gmail.com> wrote:
> I think GWT is best utilized in a full page scenario because of "code
> sharing" of re-usable components.
> If you go the other route and "just" embed GWT code in different host pages
> (i.e. application with multiple entry points) you lose the benefits of
> javascript code re-use of reusable components because every entrypoint will
> have its own module.nocache.js file which has to be transferred to the
> client. If you create a re-usable component (let's say a CellTable
> component) which is used in different places  (in both entry points) the
> same code will be part of the module.nocache.js file and thus downloaded two
> times.
> It probably doesn't make a big difference for small web-sites where some
> parts are done with GWT but for complex apps where you might re-use a lot of
> components it might be an issue.
> However in case you go with the one host page (one entry point) solution you
> will probably not use any of the your backend's flow controls (MVC) but it
> will solely act as a data-backend.

--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.