Hi Julien,
This generator will take GWT to the next level. Integrating GWT with existing
js libraries was always time-consuming and error-prone (using either JNSI or
jinterop).
What is the status of it (what is holding back the project from being
open-sourced)? Can we help in any way?
--
Hi, I have a large GWT app deployed too, and didn't notice any problem with
the new Chrome. Do you use any large GWT framework, such as Vaadin or GXT?
Or any framework/lib outside GWT on the client side? Or maybe any native
component?
On Wednesday, December 16, 2015 at 3:11:10 PM UTC-2, Joshb
It's easier to understand and accept the schedule from GWT project (or any
other Google or driven-by-Google-culture project) when you apply the Valve
time calendar to it. Yes, Valve is the pioneer (that's why the calendar
received their name), but a lot of companies and groups use that
Thank you Thomas and Colin for your replies.
Thomas, sorry for posting in the wrong place. I didn't even know there is a
gwt-maven-plugin users group... thanks for pointing that out!
Working with separated projects with GWT, Maven, Eclipse (and his friends -
the plugins!) and App Engine is
Hi,
I'm using GWT 2.6.0 with Maven, using the gwt-maven-plugin, and in my
project I have some auto generated classes (using the generated-with
directive on Module.gwt.xml). The generator is a subclass of
com.google.gwt.core.ext.Generator.
The problem is: every time I build my project, Maven
Hi,
I was wondering if you have considered using JIRA as issue tracker instead
of the suplied by google code. Many open source projects uses it (such as
JBoss Errai, at https://issues.jboss.org/browse/ERRAI ) and I think it is
far superior than the vanilla google code issue tracker - for the
Hi,
Most of the gwtproject.org links cannot be opened in a new tab (a 404 error
page is showed when doing so). For example, clicking on the Documentation
Latest Overview to open in a new tab results in 404. Should I open a bug
report for that? It is not really related to GWT itself, so I
I see the problem here: I don't consider GWT just a web framework (and
maybe I'm wrong about that). I consider it a platform on which web
frameworks are built (like Vaadin, GXT, Errai and so on). It involves
compiler, language, tooling *and* a web framework. And assuming it as a
platform, I
I rather prefer formal, concrete documents from the steering committee.
Keeping all the things just as informal make the project feels like a
school project, with no commitment to quality and deadlines. I can't take a
project seriously when a documents says there would be a release 02/DEC and
