I can lob out this: on a previous project, not written in GWT but rather the old fashioned way with Javascript, we created a browser app (single HTML page, DOM managed in Javascript and XMLHTTP) that had about 250,000 lines of javascript. We deployed it to some fairly limited (read: old) machines in our call centers and did not have any significant issues relating to performance. We've written a number of smaller apps using GWT and are now in the process of replacing the old first generation app with a new one written in GWT, with significantly more features. We expect it to be very "large" and we are certain that the GWT compiler will produce tighter javascript code than I could ever write. Just my thoughts....
Good luck! Later, Shaffer On Jan 23, 5:46 pm, Shawn Pearce <[email protected]> wrote: > I'm not using GXT, but Gerrit2 (live demo at gerrit2.source.android.com) has > its *.cache.html in the 368 KB ballpark, compressed with gzip -9 these > deflate down to ~106 KB. I create the *.cache.html.gz during the build and > let Jetty serve them as-is to clients. > > There's a fair chunk of functionality in Gerrit2. Everything you see is > built and rendered in the client using the GWT widgets. The server only > produces JSON for the client to parse and render as it wants to. Its not > search engine friendly, but my point is, even with all of the functionality > in the client, its still only 368 KB. > > GWT 1.6 will contain a feature to let you split up the application into > smaller chunks and load on demand the JavaScript segments necessary for > certain portions of the application. But that won't get you very much as > most of your core widgets will still be in the initial download, and thus > the initial download will still be pretty sizable. > > In Gerrit2 I plan on using this to segment out the administration screens > and the user preference screens. These aren't accessed often and their code > is very isolated, so taking them out of the initial download makes sense. > But overall I don't expect a very large reduction on the initial download, > as there is still quite a bit of shared code. > > On Fri, Jan 23, 2009 at 15:47, RamiK <[email protected]> wrote: > > > Hi, > > > I will be developing an enterprise product and am considering GWT and > > GXT as the technologies to base my webapp on. I already have an > > existing product based on an Applet and\or JSPs and I want to get rid > > of them. > > > I have already installed and played around with GWT and I have some > > concerns regarding the scalability of GWT. > > > It seems to me that, at the end of the day, GWT creates 1 large HTML > > file (per browser type) that contains all my code in Javascript. That > > works great in small scale but already at this stage, when I have > > hardly written anything, the html files are 500kb. > > > What will happen when I finish developing my product? Will I end up > > with a 10Mb HTML file? The load performance will be terrible, not to > > mention that there may be some size limitation in the browser for > > length of HTML file or ability to handle thousands of lines of > > javascript code (??). > > > Are my concerns founded? Is the GWT development team planning on > > addressing these issues in a future release? > > Did anybody already develop a massive GWT application? How large did > > the HTML file get? > > > Thanks! > > R --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
