Re: [gwt-contrib] Re: GPE does not like GWT trunk SDK?

2015-06-30 Thread Jens
As of 2015 June 29, Eclipse 4.5 is available. Any updates about GPE on github ? https://github.com/gwt-plugins/gwt-eclipse-plugin This is an open source fork of the original GPE. -- J. -- You received this message because you are subscribed to the Google Groups GWT Contributors group.

Re: Roadmap Question for GWT 3.0

2015-06-30 Thread Jens
Is there any downside to Request Builder? Possible deprecation in GWT 3.0? Well the internally used XMLHttpRequest / Timer classes would need to be ported to JsInterop of course because they use JSNI. There are some general to consider with RequestBuilder as well: - It is quite low level -

Re: Roadmap Question for GWT 3.0

2015-06-30 Thread Ed
@jens Is there any downside to Request Builder? Possible deprecation in GWT 3.0? Best Regards Ed On Mon, Jun 29, 2015 at 1:43 PM, Ed ej19...@gmail.com wrote: Thanks Jens, Great response, gives our devs something to learn. On Mon, Jun 29, 2015 at 12:55 PM, Jens jens.nehlme...@gmail.com

Re: Roadmap Question for GWT 3.0

2015-06-30 Thread Ümit Seren
In addition to what Jens said: If possible, go Restful. it makes it much easier to later add non-GWT clients and also forces you to think about your domain model as resources (might lead to a clean API). I guess once Elemental 2.0 is released (AFAIK along the lines with GWT 3.0) you could

Re: Roadmap Question for GWT 3.0

2015-06-30 Thread Ed
@jens @umit Thank you very much for this insight. Best Regards Ed On Tue, Jun 30, 2015 at 9:44 AM, Ümit Seren uemit.se...@gmail.com wrote: In addition to what Jens said: If possible, go Restful. it makes it much easier to later add non-GWT clients and also forces you to think about your

[ANN] gwt-places: the PlaceHistoryMapper generator ported as an annotation processor

2015-06-30 Thread Thomas Broyer
Hi all, I just pushed out gwt-places to GitHub: https://github.com/tbroyer/gwt-places This is a port of the PlaceHistoryMapper generator as an annotation processor: I copied the code from GWT proper and replaced uses of com.google.gwt.core.ext. with javax.lang.model. and

Re: [gwt-contrib] Re: GPE does not like GWT trunk SDK?

2015-06-30 Thread Joel Handwell
That means 1. Google Plugin for Eclipse will change its name to GWT Eclipse Plugin? (then the name I think does not include features like App Engine SDK) or 2. Google Plugin for Eclipse will be continued to be closed source, and GWT Eclipse Plugin will be developed as fork independent from

Re: [gwt-contrib] Re: GPE does not like GWT trunk SDK?

2015-06-30 Thread Brandon Donnelson
The plugin has been forked although it still has the App Engine features. Although the Google login isn't working on the GWT plugin for Eclipse at the moment. Eventually we should see a Eclipse plugin that only has the Google features and the GWT features can live on there own, yet both will

Re: [gwt-contrib] Re: GPE does not like GWT trunk SDK?

2015-06-30 Thread Joel Handwell
@Brandon so GPE is going to be like Chrome, and gwt-eclipse-plugin will be like Chromium? On Tuesday, June 30, 2015 at 3:18:24 PM UTC-4, Brandon Donnelson wrote: The plugin has been forked although it still has the App Engine features. Although the Google login isn't working on the GWT

JsInterop question ...

2015-06-30 Thread Benjamin Tillman
Hey everyone, just a quick question regarding JsInterop: how is it proposed to manage javascript functions that can potentially take more than one type of parameter? For example, take the websocket interface http://www.w3.org/TR/websockets/#the-websocket-interface: @JsType(prototype =