Re: Large no of gwt modules
Check out this talk by Max Barkley, towards the end - although he talks about Errai (which I highly recommend), the ideas with JsInterop project splitting might be applicable outside Errai as well : https://www.youtube.com/watch?v=KeCTj1oIKR0 http://redhat.slides.com/mbarkley/errai-40-roadmap-1#/ On Wednesday, January 27, 2016 at 1:19:29 AM UTC-8, Rajesh Gupta wrote: > > We have large no of gwt modules. > > Code splitting is not option for large no of GWT modules. See the issues > as clearly explained in turducken pattern. > > http://www.slideshare.net/RobertKeane1/turducken-divide-and-conquer-large-gwt-apps-with-multiple-teams > > Will 2.8 release or 3.0 release fix the full page refresh problem. Will > it have feature to use GWT modules with out full page refresh. > Will 2.8/3.0 have features to dynamically load/unload gwt modules. > > -Rajesh > > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Large no of gwt modules
Hello Christian, Looking forward to see some examples in the repo. It will be good asset for gwt developers who has developed many modules over the years and getting frustrated with full page refresh problems Rajesh. On Wednesday, February 3, 2016 at 7:28:42 PM UTC+5:30, Cristian Rinaldi wrote: > > In a couple days, I will be uploading an example in my repo... and I'll > update this post. > Greetings > > El martes, 2 de febrero de 2016, 0:49:00 (UTC-3), Rajesh Gupta escribió: >> >> Hello Christian, >> Thanks for the reply >> Do you have a public facing website that is using this pattern. I would >> be curious to see, the performance and the UI experience. >> How about the history? Too many changes required for history handling? >> >> Regards >> Rajesh >> >> On Sunday, January 31, 2016 at 9:26:12 PM UTC+5:30, Cristian Rinaldi >> wrote: >>> >>> Rajesh, >>> I implemented a large GWT application using turducken pattern, I do >>> not think that GWT need something specific to dynamically load modules, >>> remember that a GWT app is just a JS file, and can be externally charged by >>> a component that is responsible for this, with the particular logic, >>> according to your modular design and dependencies. >>> You must have a cross event bus that can receive and send messages, >>> then, every module, GWT or not, can translate addressing scheme, for >>> example, Activities and Places in a GWT module. >>> In each module, you can use code splitting, to increase efficiency. >>> >>> I hope help with this. >>> >>> Greetings..!! >>> >>> >>> El miércoles, 27 de enero de 2016, 6:19:29 (UTC-3), Rajesh Gupta >>> escribió: We have large no of gwt modules. Code splitting is not option for large no of GWT modules. See the issues as clearly explained in turducken pattern. http://www.slideshare.net/RobertKeane1/turducken-divide-and-conquer-large-gwt-apps-with-multiple-teams Will 2.8 release or 3.0 release fix the full page refresh problem. Will it have feature to use GWT modules with out full page refresh. Will 2.8/3.0 have features to dynamically load/unload gwt modules. -Rajesh -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Large no of gwt modules
In a couple days, I will be uploading an example in my repo... and I'll update this post. Greetings El martes, 2 de febrero de 2016, 0:49:00 (UTC-3), Rajesh Gupta escribió: > > Hello Christian, > Thanks for the reply > Do you have a public facing website that is using this pattern. I would > be curious to see, the performance and the UI experience. > How about the history? Too many changes required for history handling? > > Regards > Rajesh > > On Sunday, January 31, 2016 at 9:26:12 PM UTC+5:30, Cristian Rinaldi wrote: >> >> Rajesh, >> I implemented a large GWT application using turducken pattern, I do not >> think that GWT need something specific to dynamically load modules, >> remember that a GWT app is just a JS file, and can be externally charged by >> a component that is responsible for this, with the particular logic, >> according to your modular design and dependencies. >> You must have a cross event bus that can receive and send messages, >> then, every module, GWT or not, can translate addressing scheme, for >> example, Activities and Places in a GWT module. >> In each module, you can use code splitting, to increase efficiency. >> >> I hope help with this. >> >> Greetings..!! >> >> >> El miércoles, 27 de enero de 2016, 6:19:29 (UTC-3), Rajesh Gupta escribió: >>> >>> We have large no of gwt modules. >>> >>> Code splitting is not option for large no of GWT modules. See the >>> issues as clearly explained in turducken pattern. >>> >>> http://www.slideshare.net/RobertKeane1/turducken-divide-and-conquer-large-gwt-apps-with-multiple-teams >>> >>> Will 2.8 release or 3.0 release fix the full page refresh problem. Will >>> it have feature to use GWT modules with out full page refresh. >>> Will 2.8/3.0 have features to dynamically load/unload gwt modules. >>> >>> -Rajesh >>> >>> >>> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Large no of gwt modules
Hello Christian, Thanks for the reply Do you have a public facing website that is using this pattern. I would be curious to see, the performance and the UI experience. How about the history? Too many changes required for history handling? Regards Rajesh On Sunday, January 31, 2016 at 9:26:12 PM UTC+5:30, Cristian Rinaldi wrote: > > Rajesh, > I implemented a large GWT application using turducken pattern, I do not > think that GWT need something specific to dynamically load modules, > remember that a GWT app is just a JS file, and can be externally charged by > a component that is responsible for this, with the particular logic, > according to your modular design and dependencies. > You must have a cross event bus that can receive and send messages, > then, every module, GWT or not, can translate addressing scheme, for > example, Activities and Places in a GWT module. > In each module, you can use code splitting, to increase efficiency. > > I hope help with this. > > Greetings..!! > > > El miércoles, 27 de enero de 2016, 6:19:29 (UTC-3), Rajesh Gupta escribió: >> >> We have large no of gwt modules. >> >> Code splitting is not option for large no of GWT modules. See the issues >> as clearly explained in turducken pattern. >> >> http://www.slideshare.net/RobertKeane1/turducken-divide-and-conquer-large-gwt-apps-with-multiple-teams >> >> Will 2.8 release or 3.0 release fix the full page refresh problem. Will >> it have feature to use GWT modules with out full page refresh. >> Will 2.8/3.0 have features to dynamically load/unload gwt modules. >> >> -Rajesh >> >> >> -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
Re: Large no of gwt modules
Rajesh, I implemented a large GWT application using turducken pattern, I do not think that GWT need something specific to dynamically load modules, remember that a GWT app is just a JS file, and can be externally charged by a component that is responsible for this, with the particular logic, according to your modular design and dependencies. You must have a cross event bus that can receive and send messages, then, every module, GWT or not, can translate addressing scheme, for example, Activities and Places in a GWT module. In each module, you can use code splitting, to increase efficiency. I hope help with this. Greetings..!! El miércoles, 27 de enero de 2016, 6:19:29 (UTC-3), Rajesh Gupta escribió: > > We have large no of gwt modules. > > Code splitting is not option for large no of GWT modules. See the issues > as clearly explained in turducken pattern. > > http://www.slideshare.net/RobertKeane1/turducken-divide-and-conquer-large-gwt-apps-with-multiple-teams > > Will 2.8 release or 3.0 release fix the full page refresh problem. Will > it have feature to use GWT modules with out full page refresh. > Will 2.8/3.0 have features to dynamically load/unload gwt modules. > > -Rajesh > > > -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
