[gwt-contrib] Re: Comment on CodeSplitting in google-web-toolkit
Comment by pclog...@gmail.com: The best poker blog http://poker-blogs-see.blogspot.com Best PokerStars blog http://pokerstars-blogs.blogspot.com Sexy, hot girls imagehttp://china-sexy-girl-images.blogspot.com/ For more information: http://code.google.com/p/google-web-toolkit/wiki/CodeSplitting -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Comment on CodeSplitting in google-web-toolkit
Comment by mohanam...@gmail.com: I believe GWT Team deserves a lot of credit for their contributions to the AJAX toolset. When we standardized on GWT, my vision/hope was that GWT would emerge as the #1 (top) toolset for AJAX development. Are we there yet? We designed our own frameworks on top of GWT for modular development and dynamic registration at onModuleLoad. But the initial download and the login screen takes about 40 seconds depending on the network bandwidth. Unless we supply some toys to play with, this is not acceptable performance. We have been looking for ways to optimize the initialization. The code spliting feature did sound promising, iniitally. I went through its documentation and examples for several times. I could be missing something here. But something does not look right. The GWT code splitting feature does not easily work our modular design. Too invasive - requiring insertion of GWT.runAsync calls in the code. (Hacking?) In my experience, well-designed features are highly intutive and extremely flexible. Unfortunately, the GWT Code Splitting is not even close. For example, can I simply designate an EntryPoint in module.gwt.xml to be loaded on demand? A simple onDemand=true/false in the entry-point tag could have been very elegant solution. Some people believe in simplicity. Any thoughts please? For more information: http://code.google.com/p/google-web-toolkit/wiki/CodeSplitting -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Comment on CodeSplitting in google-web-toolkit
Comment by boj...@gmail.com: However philosophically we speak, the fact is software will be modular. GWT promotes building huge monolithic apps with no inherent plugability. If you don't realize and fix this sooner, GWT will be on its death bed. OSGi is getting so much focus that it would be childish to ignore these concerns. For more information: http://code.google.com/p/google-web-toolkit/wiki/CodeSplitting -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Comment on CodeSplitting in google-web-toolkit
Comment by alyxandorjames: Note to everyone reading this, This guide is somewhat dated. FOR UP TO DATE GUIDELINES, GO TO http://code.google.com/webtoolkit/doc/latest/DevGuideCodeSplitting.html For more information: http://code.google.com/p/google-web-toolkit/wiki/CodeSplitting -- http://groups.google.com/group/Google-Web-Toolkit-Contributors To unsubscribe from this group, send email to google-web-toolkit-contributors+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[gwt-contrib] Re: Comment on CodeSplitting in google-web-toolkit
Comment by ivance...@gmail.com: I wonder if GWT.runAsync could be used as some sort of worker thread to invokd a long running computations which update certain UI values that are not currently visible on the view(thus, doesn't need immediate update),who's value and computation depend on the UI object in focused which would invoke the long running script on the onblur event, so as minimize unresponsiveness of the UI currently on focused thus increasing application responsiveness. --ivanceras For more information: http://code.google.com/p/google-web-toolkit/wiki/CodeSplitting -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Comment on CodeSplitting in google-web-toolkit
Comment by federico.monaldi: i have a problem with codeSplitting when i combine this with a command pattern to make calls to the server. I have a single RemoteService that expose an api like this: R extends Result R execute(ActionR action) throws ActionException; the remote serviceAsync impl is reachable from the initial entrypoint but this force all the possibli serializable Actions and Results to be include in the initial code fragment. I'm really tryng to avoid this because each client module define it's own Actions and Results and i'd like this classes being downloaded only when the module that defines it will became reachable. For more information: http://code.google.com/p/google-web-toolkit/wiki/CodeSplitting -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Comment on CodeSplitting in google-web-toolkit
Comment by tristan@gmail.com: @Evelyne24 If you haven't come across this yet, it may be of help using GIN and CodeSplit. http://code.google.com/p/google-gin/issues/detail?id=61 For more information: http://code.google.com/p/google-web-toolkit/wiki/CodeSplitting -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] Re: Comment on CodeSplitting in google-web-toolkit
Ah, yes, I understand the larger issue(s) now. I wasn't thinking about all of the name-munging issues that would arise between separately compiled modules. Having been to DLL hell and back in my career, I have no interest in returning. -Brett On Jul 7, 7:33 am, codesite-nore...@google.com wrote: Comment by hbrucejohnson: @brett: What Ray said. Also, we don't want to create the web equivalent of DLL Hell, which is a very easy situation to get into. Finally, and most importantly, runtime modularity simply has a really high performance cost because HTTP round-trips over the internet are inevitably slow and so we strive to encourage architectures that avoid them. All that said, I think there are a few things we'll do before long (e.g. making it easy to expose JS-callable APIs from GWT modules, like Ray's gwt-exporter) could go a long way toward providing some amount of dynamic pluggability without sacrficing too much in the way of performance. For more information:http://code.google.com/p/google-web-toolkit/wiki/CodeSplitting --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
