There is a demo: https://www.youtube.com/watch?v=wFMD1GXR2Tg and there should be somewhere a spec (have to look for the link)
On Tue, Dec 17, 2013 at 6:34 PM, Robert J. Carr <rjc...@gmail.com> wrote: > Thanks for the gwt-exporter suggestion (it was already on my radar) and > thanks for the alternative dart web toolkit. I didn't catch the conference > but that is very interesting about GWT 3.0. Do you have any white papers > on that specific topic? > > > On Tue, Dec 17, 2013 at 5:17 AM, Ümit Seren <uemit.se...@gmail.com> wrote: > >> Alterantively you could check out DWT (http://dartwebtoolkit.com/) which >> tries to mimic the GWT features in Dart. >> But I guess this would be more involved than using gwt-exporter. >> >> In case you missed the recent GWT.create conference. There are plans for >> GWT 3.0 to make the interoparability between JS and GWT much much easier >> and with web-components you can write JS code and then easily use it in >> GWT. >> >> >> >> On Tuesday, December 17, 2013 1:36:12 AM UTC+1, rjcarr wrote: >>> >>> I have a pretty large project that's over 7 years old that has used GWT >>> from the very early days and is nearly 100% GWT (i.e., there's very little >>> manually written javascript). However, we'd like to transition the client >>> to be written in javascript, but if possible, we'd like to retain the GWT >>> services (i.e., the serialization). >>> >>> Basically, we'd like to keep all of the RemoteService, >>> RemoteServiceAsync, and RemoteServiceServlet (and the accompanying >>> object serialization) but write the client / visualization portions >>> manually in javascript. >>> >>> Is there any way to divorce the data serialization from the >>> visualization without the messiness of JSNI? >>> >>> Note that we don't have any problem with GWT, it's actually been great >>> in most every way, but at this point we have many more javascript >>> developers that are uncomfortable with java and it's hard to get the level >>> of contribution we need to the project in its current state. >>> >>> Thanks! >>> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Google Web Toolkit" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/google-web-toolkit/r1_7U5uq7rs/unsubscribe >> . >> To unsubscribe from this group and all its topics, 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 http://groups.google.com/group/google-web-toolkit. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Google Web Toolkit" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-web-toolkit/r1_7U5uq7rs/unsubscribe > . > To unsubscribe from this group and all its topics, 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 http://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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+unsubscr...@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.
