Re: How to Remote Logging without using RPC?

Thank you. -- 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

Re: How to Remote Logging without using RPC?

Remote logging example using request factory https://github.com/gwtproject/gwt/blob/master/samples/dynatablerf/src/main/java/com/google/gwt/sample/dynatablerf/client/DynaTableRf.java#L73 On Monday, June 29, 2015 at 9:27:59 PM UTC+2, Chak Lai wrote: > > In the GWT application that I am working on,

How to Remote Logging without using RPC?

In the GWT application that I am working on, it is setup to remote-logging with any uncaught exceptions via SerializableThrowable >> RPC >> StackTraceDeobfuscator ... Is there any documentation on how to do it without using RPC? I have search the Internet but is seems most of the documentatio

Re: Roadmap Question for GWT 3.0

Thanks Jens, Great response, gives our devs something to learn. On Mon, Jun 29, 2015 at 12:55 PM, Jens wrote: > > 1. GWT.create >> > > : Annotation processors > : Dagger 2.x + AutoFactory (assisted inject) for injection > and System.getProperty() to build the Dagger dependency graph based on you

Re: Roadmap Question for GWT 3.0

> 1. GWT.create > : Annotation processors : Dagger 2.x + AutoFactory (assisted inject) for injection and System.getProperty() to build the Dagger dependency graph based on your deferred binding properties. For Dagger I created a pull request that generates a dagger-gwt artifact including a G

Roadmap Question for GWT 3.0

If I wanted to start now for the the GWT 3.0 release, what would be the best mechanism to replace: 1. GWT.create 2. RPC We starting a refactor of existing code, and would like some foresight into this matter. Thanks Ed -- You received this message because you are subscribed to the Google Gro

Re: Important videos from GWT Meet-up 2015

On thing I'd like to see on GWT 3.0 and beyond is the reduction (or complete avoidance) of the "Not invented here syndrome" from Google: - Using a standard build tool which integrates well with Maven repositories - and don't force the end user to switch build tools just because - Us