Re: Future of GWT

2018-05-17 Thread Mincong Huang
Recently, we also upgraded our application of 100k LOC from GWT 2.7.0 to GWT 2.8.2. Some key changes we faced are: 1. We uses super dev mode: It compiles correctly, same speed as the legacy dev mode. It also allows us the debug on the dev environment (requires some config). 2. The

Re: Testing native @JsType in GWT tests

2018-03-11 Thread Mincong Huang
at (can't test right now) > > ScriptInjector.fromString(js).setWindow(ScriptInjector.TOP_ > WINDOW).inject(); > > If you do this then you need to change your jsni test to > > var p = new $wnd.ns.Person(); > > Hope that helps. > > Vassilis > > > On Sun, Mar 11, 2018 at 3:44 PM

Testing native @JsType in GWT tests

2018-03-11 Thread Mincong Huang
public native String sayHello(); } } Note: The 2nd test method, `testJsni()`, runs successfully, so the JS should be injected correctly. I also have the flag `generateJsInteropExports` enabled in the Maven GWT plugin in the POM [2]. So what am I missing? I'm using GWT 2.8.2 and Maven GWT plugin 2

Re: Testing native @JsType in GWT tests

2018-03-12 Thread Mincong Huang
I suggest that you switch to net.ltgt.gwt.maven:gwt-maven-plugin as suggested at https://gwt-maven-plugin.github.io/gwt-maven-plugin/ ? you'll have fewer of such surprises –disclosure: I'm the author of that latter plugin, and former maintainer of Mojo's one) On Sunday, March 11, 2018 at 8:12:39 PM

Re: Testing native @JsType in GWT tests

2018-03-12 Thread Mincong Huang
nd "normal-test" for JsInterop, running in production mode. It works fine. On Mar 12, 2018 11:38, "Thomas Broyer" <t.bro...@gmail.com> wrote: > > On Monday, March 12, 2018 at 9:17:58 AM UTC+1, Mincong Huang wrote: >> >> Thanks, Thomas. Changing to produ

Re: [gwt-contrib] Re: Naming convention for ported GWT modules

2018-03-24 Thread Mincong Huang
On Sat, Mar 24, 2018 at 12:27 PM, Thomas Broyer <t.bro...@gmail.com> wrote: > > > On Saturday, March 24, 2018 at 10:30:10 AM UTC+1, Mincong Huang wrote: >> >> Hi, >> >> I'd like to have a clarification about the naming convention for ported >> GWT

[gwt-contrib] Re: How can I contribute to GWT?

2018-03-21 Thread Mincong Huang
>important, it is a very clear way to show how live GWT is and that it is >still has a community behind it, it brings more audience. > > > finally, its been less than 2 years since i joined the community and i am > proud of the level i reached and still believe there

[gwt-contrib] How can I contribute to GWT?

2018-03-21 Thread Mincong Huang
ated to Java compilation, type, and test. Before joining Nuxeo, I participated to Google Summer of Code 2016. I contributed to Hibernate Search, a layer on top of Hibernate ORM for search, by adding module `jsr352` for batch indexing data [5]. Cheers, Mincong HUANG [1]: https://github.com/gwtprojec

[gwt-contrib] Naming convention for ported GWT modules

2018-03-24 Thread Mincong Huang
wt-` + module name as artifact id. There're several benefits. It helps people to find all the artifacts via the same group id. It also keeps consistency for the generated JAR files: each of them contains a "gwt-" prefix, thus they are GWT artifacts. Cheers, Mincong Huang [1]: htt