GWT React initial version

I have pushed the initial version of GWT React to Github It is still very much as work in progress, but I it is definitely a viable project. The API for React itself is pretty complete. Redux works for the basics but I need to test out middleware and store

[GTW 2.8] How to use JSON-like data with JSInterop

Hi all, How do I construct input for the following jQuery call: $('.ui.form') .form({ fields: { name : 'empty', gender : 'empty', username : 'empty', password : ['minLength[6]', 'empty'], skills : ['minCount[2]', 'empty'], terms : 'checked' } }) ; My current plan is to use

Re: [2.8-SNAPSHOT] Obscure stack traces

> > > > ... > > ... > > > Is that correct? > Yes thats correct. With the above you should see source maps applied to stack traces when using Chrome. But you do not have to set compiler.stackMode explicitly to native as native is the default. You can see this

Re: When is GWT 2.8 provide java.util.stream.IntStream emulation?

> ... i am working with the 4/20 snapshot and do not see it. > Its not yet pushed for review, so it could take some time until its available. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop

When is GWT 2.8 provide java.util.stream.IntStream emulation?

... i am working with the 4/20 snapshot and do not see it. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post

Re: [gwt-contrib] Lambda overhead

Meta: it would make my year if we could get one of these compiler discussions happening once a week on a public forum like this, both for better basic understanding about why some of these concepts are not trivial, and for better visibility into what else is going on in the process of continuing

Re: [2.8-SNAPSHOT] Obscure stack traces

Thanks Jens, I do see the Java sources in Chrome and can debug. Fort for the settings, I suppose you mean : ... ... Is that correct? And can you please point me to a documentation link for it... Thanks! On Friday, April 22, 2016 at 3:52:58 AM UTC-7, Jens

Re: SuperDevMode automatic recompile does not work with external server

Assuming the Mojo plugin and gwt:run-codeserver; you'll need to set the launcherDir property: https://gwt-maven-plugin.github.io/gwt-maven-plugin/run-codeserver-mojo.html#launcherDir If using gwt:run, then AFAICT it'd be hostedWebapp:

Re: GWT, Firefox, and focusout

This is not a GWT issue really, so let me GTFY: https://gist.github.com/nuxodin/9250e56a3ce6c0446efa On Thursday, April 21, 2016 at 1:16:00 PM UTC-7, N Troncoso wrote: > > I have an issue where an event isn't firing in Firefox, and it turns out > this is because Firefox doesn't currently

Re: SuperDevMode automatic recompile does not work with external server

Hmm. I just tried some options of the maven plugin but that did not work. But it's not important anyway. I integrated build step into our java server that copies over the nocache.js files of the gwt project into its assets folder. That works for both the superdevmode and the regular ones (when

Re: SuperDevMode automatic recompile does not work with external server

> SuperDevMode does not seem to respect gwt.war when compiling its > superdevmode.nocache.js. And that is the problem. The special > superdevmode.nocache.js gets created in the target folder of the > original gwt project. Our Java server knows nothing about it... > > Is there a good

Re: What needs to be done after a successful login

I think it is worth deciding what you want to happen when the users credentials timeout (or are lost) on the server side. Personally I hate it when Ajax/single page apps quietly fail when authentication has expired. Cheers Sam On Monday, April 11, 2016 at 3:10:53 PM UTC+1, Olar Andrei wrote:

Re: SuperDevMode automatic recompile does not work with external server

That did the trick. Now it's working... Thanks Jens! I did not know that there is a special SuperDevMode nocache.js file needed. Now things are a bit clearer. We used ../ninja/src/main/java/assets/gwt (aka gwt.war parameter) so that gwt compiled its js sources into the assets folder of our

Re: [2.8-SNAPSHOT] Obscure stack traces

Do you see source maps (and thus your java files) in your Chrome dev tools under the "sources" tab? If not, then Chrome has not loaded source maps for any reason. Also if your have inherited Logging.gwt.xml then the property compiler.stackMode must be set to native in order to see stack traces

Re: SuperDevMode automatic recompile does not work with external server

First start SDM, then deploy your war to your external server. SDM generates a special *.nocache.js file that enables automatic recompilation. You have to make sure that this special version is deployed. -- J. -- You received this message because you are subscribed to the Google Groups "GWT

SuperDevMode automatic recompile does not work with external server

Hi, I just ran into an interesting problem while upgrading a very old GWT app to GWT 2.8.0-beta1 and its SuperDevMode (using the codehaus maven plugin). Our setup is basically that we got two projects: A GWT project, and a Java Server that acts as restful json backend. If I compile stuff via