Re: Roadmap Question for GWT 3.0

Thank you for your answer Jens. So much GWT solutions build on widget system so I think there will be a port/solution (thinking about the new GWT Material Project which was startend a view months ago...).

@Ed: so you use a REST service on backend? Seems also for us a good solution but debugging inside IDE will be lost.

Am Dienstag, 28. Juli 2015 12:22:11 UTC+2 schrieb Ed:
> It was process but we ported everything to  the low level RequestBuildner.and json. Now we have just one timer in the UI a huge reduction from the async nature of RPC.
>
>  In our situation we render everything out of a DataDictionary on the server side and use a Frame for the results,
>
> The GUI is pure GWT. Size of application rose from 182k to 1.5 meg including split points.  Without profiling it is noticeably faster without RPC.  I am guessing that there are less instantiations of classes on server and UI.
>
> All in all, we are ready for GWT 3.0 and look forward to the stable 2.8.
>
> Thanks for all your help!
>
> Best Regards
>
>
>
> On Tue, Jul 28, 2015 at 5:01 AM, Jens <jens.ne...@gmail.com> wrote:
>
>
> Where can I read that GWT RPC and widget system will be dropped with GWT 3.0? Is there a presentation / doc online?
>
>
>
> And what does it mean that GWT.create will be dropped?
>
>
>
> And: really dropped or set as deprecated?
>
>
>
>
> GWT 3.0 drops support for JSNI and GWT.create(). JSNI will be replaced with JsInterop and GWT.create() will be replaced with either annotation processors (generate-with case) or dependency injection/System.getProperty (replace-with case). So all library code of GWT which depends on those two features need to be ported to the new GWT compiler. 
>
>
> Widget is probably doable but GWT-RPC might be really difficult (if not impossible) because the current GWT-RPC generator asks questions like "give me all types that implement XYZ" which an annotation processor can only hardly answer (if at all). GWT-RPC might be portable if some refactoring in the app using GWT-RPC is acceptable (e.g. slapping annotations on DTOs instead of marking them with Serializable).
>
>
> You can see videos about that topic from the GWT 2015 meet up at https://www.youtube.com/playlist?list=PL1yReUCGwGvrqscLu1EAyYRPrr0ceEHLE
>
>
> Slides are linked in the playlist description.
>
>
> -- J.
>
>
>
>
> --
>
> 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-we...@googlegroups.com.
>
> Visit this group at http://groups.google.com/group/google-web-toolkit.
>
> For more options, visit https://groups.google.com/d/optout.

--
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/d/optout.