Thursday, October 24, 2013

Re: On extension strategies for GWT applications

We really need something like this too. We've developed a workbench UI, that has plugins - all currently compile time. Would be nice to be able to have those as runtime plugins, even if they are self contained GWT apps. As you pointed out "you can not just simply pass those objects between the GWT applications since the same Java class does not generate the identically named JS class".

Maybe in the future a base application during compilation could export a symbol table of names, for classes with the correct annotations, that the other GWT applications can compile against. This would then allow each GWT application to read/write the same java objects, without requiring a GWT -> JS <- GWT bridge.

Mark

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment