Re: [gwt-contrib] Re: Problem with JsInterop

2016-09-01 Thread Arnaud TOURNIER
Thanks a lot for your answer. I tried the solution with defender methods earlier but it did not work, as far as i remember the compiler refused @JsOverlay defender methods on the JsFunction. The @JsFunction documentation says that : "A JsFunction interface cannot have defender methods." I will

Re: [gwt-contrib] Re: Problem with JsInterop

2016-09-01 Thread 'Goktug Gokdogan' via GWT Contributors
The limitation around @JsFunction is basically driven from the limitations of being a function. I think there was an earlier discussion in the contibutor list where we explained this in more detail. Being said that, you can handle some overloading in JsFunction interfaces via defender methods

Re: Kendo UI GWT wrapper library

2016-09-01 Thread Transplant
On Wednesday, January 20, 2016 at 2:16:37 AM UTC-8, Aron Homberg wrote: > > Hi everyone, > > I'm wondering if there is any need for a Kendo UI wrapper library. Kendo > UI is, as some of you may know, an enterprise front-end web/mobile > JavaScript library. It is based on jQuery and comes with

[gwt-contrib] Re: Ext.form.field.File not working with gwt2.8.0-rc2 (with gwt2.8.0-beta1 it works)

2016-09-01 Thread Jens
> Do you pass --generateJsInteropExports to GWT? I think that's now required > for @JsFunction⋅s to be callable from JS. > You don't need --generateJsInteropExports to make @JsFunction work, that would be bad. Just verified it using RC2 and event listener on button element. But you need

[gwt-contrib] Re: Ext.form.field.File not working with gwt2.8.0-rc2 (with gwt2.8.0-beta1 it works)

2016-09-01 Thread Thomas Broyer
Do you pass --generateJsInteropExports to GWT? I think that's now required for @JsFunction⋅s to be callable from JS. On Thursday, September 1, 2016 at 5:59:41 PM UTC+2, Teletin Alin wrote: > > Hi all, > > I have a problem with an upload button which sends the selected file to a > servlet and

[gwt-contrib] Re: Documentation site on github

2016-09-01 Thread Hristo Stoyanov
How about using www.gitbook.com? Several OSS projets are doing it, their docs look great, for example: www.keycloak.org/documentation.html On Thursday, January 8, 2015 at 2:04:28 PM UTC-8, Julien Dramaix wrote: > > Dear GWT Community, > > In order to increase the number of contributions on the

[gwt-contrib] Ext.form.field.File not working with gwt2.8.0-rc2 (with gwt2.8.0-beta1 it works)

2016-09-01 Thread Teletin Alin
Hi all, I have a problem with an upload button which sends the selected file to a servlet and takes some action on servlet response. This is the code: //all ESExtXXX or ExtXXX from following code are wrapped javascript with jsinterop ESExtCreateParams *uploadPanelParams* = new

Re: synchronously waiting for a Promise

2016-09-01 Thread Jens
> Jens, my suggestion was to propagate the asyncs up the call stack to all > callers of the function, automatically changing each one to return a > promise, and use await on the calls to the async functions, which would > work fine except for losing the atomic synchonization of the functions

Re: CalenderUtil Date Math BUG - GWT 2.8 RC2

2016-09-01 Thread Michael Joyner
As we are not calling a "set" operation but an "addMonthsToDate" operation and as a result we find this behavior surprising - and a little non-intuitive. Calendar does not "skip" a month when using "add" month, the days are adjusted to the end of the next month to

Re: synchronously waiting for a Promise

2016-09-01 Thread Ian Preston
Jens, my suggestion was to propagate the asyncs up the call stack to all callers of the function, automatically changing each one to return a promise, and use await on the calls to the async functions, which would work fine except for losing the atomic synchonization of the functions effects

Re: synchronously waiting for a Promise

2016-09-01 Thread Thomas Broyer
On Thursday, September 1, 2016 at 4:19:02 PM UTC+2, Thomas Broyer wrote: > > > > On Thursday, September 1, 2016 at 4:10:12 PM UTC+2, Jens wrote: >> >> >> var _symbol$bar = Symbol("Foo.bar"); >>> class Foo { >>> async getBar() { // Note: transformed to 'async', no 'synchronized' >>> if

Re: synchronously waiting for a Promise

2016-09-01 Thread Jens
> I think this isn't even correct, because "async getBar()" does return a > promise simply because its marked async. Given that you can only call await > inside async functions I think its nearly impossible to map that to a > synchronous Java function while keeping the correct return type or

Re: synchronously waiting for a Promise

2016-09-01 Thread Thomas Broyer
On Thursday, September 1, 2016 at 4:10:12 PM UTC+2, Jens wrote: > > > var _symbol$bar = Symbol("Foo.bar"); >> class Foo { >> async getBar() { // Note: transformed to 'async', no 'synchronized' >> if (this[_symbol$bar] == null) { >> var realBar = …; >> this[_symbol$bar] = await

Re: synchronously waiting for a Promise

2016-09-01 Thread Jens
> var _symbol$bar = Symbol("Foo.bar"); > class Foo { > async getBar() { // Note: transformed to 'async', no 'synchronized' > if (this[_symbol$bar] == null) { > var realBar = …; > this[_symbol$bar] = await realBar.get(); // transformed to await > } > return

Re: synchronously waiting for a Promise

2016-09-01 Thread Steve Hannah
If you require synchronous code you may want to check out TeaVm. It supports full Java thread semantics in the browser. On Thursday, 1 September 2016, Ian Preston wrote: > Cool example. You are right. > > We are migrating our code to asynchronous. :-) > > > > On Thursday,

Re: synchronously waiting for a Promise

2016-09-01 Thread Ian Preston
Cool example. You are right. We are migrating our code to asynchronous. :-) On Thursday, 1 September 2016 13:59:45 UTC+1, Thomas Broyer wrote: > > Consider the following code: > > class Foo { > String bar; > > synchronized String getBar() { > if (bar == null) { // OK, we all know this

Re: CalenderUtil Date Math BUG - GWT 2.8 RC2

2016-09-01 Thread Paul Robinson
git tells me CalendarUtil.java is the same in 2.7 and 2.8RC2. So yes, the code should behave the same. But the above behaviour is not wrong because it's standard Java behaviour. Whether you use Date.setMonth(n) or Calendar.set(Calendar.MONTH, n) Java behaves the same way. That is, if you start

Re: synchronously waiting for a Promise

2016-09-01 Thread Thomas Broyer
Consider the following code: class Foo { String bar; synchronized String getBar() { if (bar == null) { // OK, we all know this is bad in the Java world, just bear with me for this sample code Future realBar = …; // make a call that returns a CompletableFuture bar =

Re: synchronously waiting for a Promise

2016-09-01 Thread Ian Preston
Interesting question, Thomas. I believe it should still work. Consider the following: 1. A 'thread' comes into a method and obtains a lock on A. 2. whilst holding the lock, it makes an async call to CompletableFuture.get() 3. Somewhere down the call stack some state which is guarded by the

Re: Public and war folders in the maven project layout (tbroyer plugin)?

2016-09-01 Thread Thomas Broyer
On Thursday, September 1, 2016 at 11:33:53 AM UTC+2, Bruno Salmon wrote: > > Hi, > > The GWT documentation > > > describes the project layout using Eclipse, but I have a couple of > questions when

Public and war folders in the maven project layout (tbroyer plugin)?

2016-09-01 Thread Bruno Salmon
Hi, The GWT documentation describes the project layout using Eclipse, but I have a couple of questions when transposing it into the maven project layout (using the tbroyer plugin): - where is the public

Re: synchronously waiting for a Promise

2016-09-01 Thread Thomas Broyer
On Wednesday, August 31, 2016 at 11:58:51 PM UTC+2, Ian Preston wrote: > > One idea, which would be awesome from a user perspective, is the following: > > Emulate CompletableFuture with native Promises. Then if the synchronous > cf.get() call is used, then translate that to await, and make the

Re: CalenderUtil Date Math BUG - GWT 2.8 RC2

2016-09-01 Thread Daniel Kurka
Does this code do the same thing in 2.7? On Wed, Aug 31, 2016 at 11:41 PM Paul Robinson wrote: > You don't say what part of this you think is a bug. I presume it's the > fact that Aug 31 plus one month is Oct 1. If so, this is not a bug. > > Adding one month should do