Yeah, I think there is no other better solution for now. Will have to take up some of views been shared and try to figure out the best possible one. Thanks a lot guys. Its a pleasure having such a fine discussion with you all. Hopefully we have something coming up from GWt to fix such a issue in a easier manner..
On Sat, Mar 14, 2009 at 12:29 AM, Matías Costa <[email protected]>wrote: > On Fri, Mar 13, 2009 at 4:31 PM, Andreas Karlsson <[email protected]>wrote: > >> Therefor I don't think the dynamic addition of (at compile time >> unknown) modules is doable with the current (or future) versions of >> GWT. >> > > Yeah, you are right. > > I've talking with a colleague about the idea, its posible, with > restrictions, with a JSNI interface in both sides, the plugin and the app. > This is the way gwt-exporter works, you can see it in the timepedia blog: > > http://timepedia.blogspot.com/2009/03/gwt-exporter-205-released.html > > But the more simple solution, as you say, is compiling all plugins all at > once, and activate them in runtime. > > I consider myself satisfied with this. Josh, are you done? > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
