Sorry,there is typing mistake in my question:the returning type of
reEmail() isn't boolean but String,and my code is:
private native String reEmail()/-*{
return
Today we are excited to announce the GWT 2.7.0 release. Thanks to everyone
who contributed to this release, especially our non-Google open source
contributors.
One major feature of this release is a new super fast compilation path in
Super Dev mode that replaces the old dev mode.
For a
Awesome!!
On 20 November 2014 07:59, Daniel Kurka danku...@google.com wrote:
Today we are excited to announce the GWT 2.7.0 release. Thanks to
everyone who contributed to this release, especially our non-Google open
source contributors.
One major feature of this release is a new super fast
Well done Daniel (and all the GWT developer community)!! Proud to have
met you in Firenze!
On Thu, Nov 20, 2014 at 12:11 PM, Juan Pablo Gardella
gardellajuanpa...@gmail.com wrote:
Awesome!!
On 20 November 2014 07:59, Daniel Kurka danku...@google.com wrote:
Today we are excited to announce
Waiting for Maven Central..
Il giorno giovedì 20 novembre 2014 11:59:06 UTC+1, Daniel Kurka ha scritto:
Today we are excited to announce the GWT 2.7.0 release. Thanks to
everyone who contributed to this release, especially our non-Google open
source contributors.
One major feature of
Waiting for Maven Central..
https://repo1.maven.org/maven2/com/google/gwt/gwt-user/2.7.0/
Maven search website just doesn't reveal it yet.
-- J.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and
Great!!! Excited to get to try JSInterop , albeit experimential
Am Donnerstag, 20. November 2014 11:59:06 UTC+1 schrieb Daniel Kurka:
Today we are excited to announce the GWT 2.7.0 release. Thanks to
everyone who contributed to this release, especially our non-Google open
source
Now it's there, when I tried Maven build failed.
Thank you, now I want to test all my projects :)
Il giorno giovedì 20 novembre 2014 13:40:39 UTC+1, Jens ha scritto:
Waiting for Maven Central..
https://repo1.maven.org/maven2/com/google/gwt/gwt-user/2.7.0/
Maven search website just
Thank you! Wov it really compiles fast after the first compilation. This
really makes a difference in development. In small change Sketchboard.io
used to take 5 - 6 seconds to compile and now it takes little bit over a 1
second, I am impressed.
Saiki
--
http://sketchboard.io - Make a complex
Fantástico!
On Thursday, 20 November 2014 11:59:06 UTC+1, Daniel Kurka wrote:
Today we are excited to announce the GWT 2.7.0 release. Thanks to
everyone who contributed to this release, especially our non-Google open
source contributors.
One major feature of this release is a new super
\s and \[ (among others) in a JS string are equivalent to s and [,
so you have to escape the backslash.
Also, your escape special characters is messing with your regexp, turning
your [0-9]{1,3} into \[0\-9\]\{1\,3\} (among others) which does not mean
the same thing at all.
Or maybe just use a
I've just updated to 2.7.0 through maven, and each time I run it, the
browser gets stuck on the 'Compiling [ModuleName]' screen. In chrome's
console, I see this error:
Uncaught ReferenceError: moduleName is not
defined :9876/ModuleName/ModuleName.recompile.nocache.js:349
I've tried stopping
Great news! We're going to switch to 2.7 in our next sprint
Great to see it compiles even faster in the super dev mode
On Thursday, November 20, 2014 11:59:06 AM UTC+1, Daniel Kurka wrote:
Today we are excited to announce the GWT 2.7.0 release. Thanks to
everyone who contributed to this
I'm in the process of Maven-izing my GWT 2.6.1 project (an intermediate
step to start using GWT 2.7.0), and as a first step want to switch to maven
style directory structure (as suggested by the Maven GWT Plugin
documentation
http://mojo.codehaus.org/gwt-maven-plugin/user-guide/project.html),
Hi,
I'm currently trying to establish a websocket connection in GWT 2.6 and 2.7
using gwt-ws.
*My question:*
the Google search points me to the gwt-ws project to implement websocket
connections. But the code examples there do not work with the jetty version
included in GWT 2.6 and 2.7
Is
It sounds like you have non-gwt-capable classes in packages meant for GWT -
is that deliberate? For example, test classes to make sure the various
server components in your project work, but they are in your .client or
.shared package?
If they are not, then GWT will totally ignore them, as no
I've been trying to understand the reasons GWT has not become a widespread
JS alternative. It has lost a great deal of mindshare; it's pretty much a
niche market now. Dart appears to be Google's second crack at the whip
(possibly learning from GWT's mistakes?).
There is very little discussion
I don't have an answer for you, but here's an interesting description of
how Google's Inbox uses Java as a base for building Android, web (via gwt)
and iOS (via j2objc) apps. Three separate native apps sharing about two
thirds of the source code.
Sounds like a bug or misconfiguration of the GPE. Is the project a Maven
project in Eclipse? There might be some hard-coded paths in the GPE
(because of limitations of Eclipse) that are only triggered in one or the
other mode (Maven vs. simple Eclipse project). E.g. /test being
excluded from
On Thursday, November 20, 2014 8:47:35 PM UTC+1, Colin Alworth wrote:
It sounds like you have non-gwt-capable classes in packages meant for GWT
- is that deliberate? For example, test classes to make sure the various
server components in your project work, but they are in your .client or
On Friday, November 21, 2014 8:18:19 AM UTC+1, Thomas Broyer wrote:
Sounds like a bug or misconfiguration of the GPE. Is the project a Maven
project in Eclipse? There might be some hard-coded paths in the GPE
(because of limitations of Eclipse) that are only triggered in one or the
other
Ok thanks so far.
Because the List.size() call is executed from GXT I don't have the
possibility to change that call.
I've rewritten my JsArrayListWrapper and it's not a JSO any more.
So I'm good to go.
Cheers,
Jan
Am Montag, 17. November 2014 20:22:29 UTC+1 schrieb John Stalcup:
A fix for
Hey guys,
we've a problem with logging since testing GWT 2.7.
We're using java.util.Logger() and with 2.7 any message trying to be logged
with WARN or lower doesn't end up in the browser console.
What I found out is that my Logger.info(String message) call is thrown away
by the GWT compiler?
GWT 2.7 changed property value gwt.logging.enabled from TRUE to
SEVERE (in Logging.gwt.xml) so by default app logs errors only.
To get back to pre-2.7 logging behavior, set this property to TRUE or
WARNING (if you want to log warnings and errors).
On Thursday, November 20, 2014 12:15:16 PM
see below,
-
GWT apps that inherit the com.google.gwt.logging.Logging module have
different default behavior for messages logged using the
java.util.logging package. The new default is to log messages at level
SEVERE and above to the browser's console. PopupLogHandler and
Though we do not make a promise to process GWT.create() of entry point
types before any other GWT.create() calls, it was easy to restore this
behavior in incremental, so I went ahead and did it (
https://gwt-review.googlesource.com/#/c/10410/).
You should probably find a way not to depend on this
Resurrecting this.
I talked with Roberto and then Ray yesterday and we think that this is a
good idea and this will both improve performance and simplify
jsinterop/compiler.
The general idea is to make the boxed types work similar to String so all
instance methods will be staticified and
27 matches
Mail list logo
