Am 03.09.2012 um 17:15 schrieb Thomas Broyer t.bro...@gmail.com:
On Mon, Sep 3, 2012 at 2:39 PM, John A. Tamplin j...@jaet.org wrote:
On Mon, Sep 3, 2012 at 4:44 AM, Thomas Broyer t.bro...@gmail.com wrote:
Also, while I understand the usefulness of the pings (I'll rollback my
changes in
On Monday, September 3, 2012 12:29:22 AM UTC+2, Ray Cromwell wrote:
The version pings are actually pretty important in terms of showing
Google management continued interest in GWT as well. Being able to
have a rough estimate on how many active monthly users we have is a
good way to argue
We are doing development on machines not connected to the internet and I
bet a lot of other GWT devs are in the same situation. So how can
management depend on such a feature to decide on usage ?
David
On Mon, Sep 3, 2012 at 10:44 AM, Thomas Broyer t.bro...@gmail.com wrote:
On Monday,
On Mon, Sep 3, 2012 at 10:51 AM, David david.no...@gmail.com wrote:
We are doing development on machines not connected to the internet
I feel your pain.
and I bet a lot of other GWT devs are in the same situation.
I sincerely hope they're not a lot. That's so 20th century!
So how can
On Mon, Sep 3, 2012 at 4:51 AM, David david.no...@gmail.com wrote:
We are doing development on machines not connected to the internet and I
bet a lot of other GWT devs are in the same situation. So how can
management depend on such a feature to decide on usage ?
You measure what you can and
On Mon, Sep 3, 2012 at 4:44 AM, Thomas Broyer t.bro...@gmail.com wrote:
Also, while I understand the usefulness of the pings (I'll rollback my
changes in the gwt-maven-plugin for the DevMode mojo), that doesn't answer
the question about the need for the JNI access to WinINet. It looks to me
On Sat, Sep 1, 2012 at 9:57 AM, Thomas Broyer t.bro...@gmail.com wrote:
As you all know, the we decided to move to Maven as the build system for
GWT. The first step is cleaning up dependencies.
Digging into the code, I stumbled upon a bit of JNI: GWT checks for
updates every day, and on
