On Friday, October 17, 2014 11:59:02 AM UTC+2, Ralf Klemmer wrote: > > First, thanks for all your replies! > > If I understand Thomas right, it is possible to use RF as a single > endpoint for GWT-Clients and Rest-Clients. Well that's great to know. >
All you need is to use RequestFactorySource.create() instead of GWT.create(), and provide a RequestTransport (there's a UrlRequestTransport using java.net.URL and HttpURLConnection but it's not really meant to be used in production (you'd prefer using Apache HttpClient or OkHttp). > Are there any plans to increase the documentation coverage in RF? > Not really actually. If you want something to be documented (or better documented), feel free to file requests in the issue tracker; or even better contribute a patch to the documentation. > Also my questions wasn't exclusively meant to be technical. > > A GWT beginner does the following learning steps (of course not complete): > 1. learn RPC > 2. application and objects grow and you look for alternatives: > RequestFactory to the rescue! > 3. highly motivated you start learning > 4. two weeks later you might ask yourself if this was a good idea, of > course you made it work, but you had to struggle a lot. And your gut > feeling stays: Is this really the best solution? > It's not. It has many benefits over GWT-RPC, but it's clearly not the "best solution" out there. We're still searching for the "best solution", and we'd like to have something better in a future version of GWT that could replace both GWT-RPC and RequestFactory, hopefully next year. > That was partly my personal experience. Then I found RestyGWT and after 4 > hours all worked as expected and I had removed hundreds lines of code - > great feeling for me! > > If RestyGWT is not an option to replace RF, then RF has to provide dead > simple and understandable official tutorials, sample projects and good > documentation! If no one knows what RF can do for you, then it's like being > non existent. > And in the context of the myth that "GWT is dead", GWT should as easy and > fun to learn as it was years ago. That should be one of the main goals for > the steering committee. If you look at the official site and see articles > from 2009, that's not what you would expect from a modern framework! Help > the GWT community to grow by bringing the learning and programming fun back. > > What are your thoughts? > With 2.7 and SDM, we're focusing on the "programming fun" ;-) and would be glad to receive contributions to the docs from the community. People who need the doc are in the best position to improve it when they had to look things up elsewhere. When you know something really well, you can answer questions, but it's hard to know upfront what people need to know and how to teach them. So don't be shy and head to Gerrit or the issue tracker ;-) -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
