Thomas gets it all correct. I just want to add one thing: If you are happy
with the current GWT stack (uibinder + widget ...), stay with it. As I
mentioned during the key notes, the GWT 2.8 will be a long maintenance
release and you have now everything you need to do a great web app.
Don't try to
On Monday, 16 November 2015 12:34:51 UTC, Thomas Broyer wrote:
>
>
>
> On Monday, November 16, 2015 at 11:29:14 AM UTC+1, Robert Stone wrote:
>>
>>
>>
>> On Sunday, 15 November 2015 15:37:29 UTC, Stephen Haberman wrote:
>>>
>>>
>>> My worry about "just pick a mainstream JS framework and use it
On Monday, 16 November 2015 12:51:35 UTC, Thomas Broyer wrote:
>
>
>
> On Monday, November 16, 2015 at 1:28:16 PM UTC+1, stuckagain wrote:
>>
>> Thanks for all the feedback. But it does not put my mind at rest right
>> now.
>>
>> It would have been much better if GWT 2.8 would have provided
On Monday, November 16, 2015 at 11:29:14 AM UTC+1, Robert Stone wrote:
>
>
>
> On Sunday, 15 November 2015 15:37:29 UTC, Stephen Haberman wrote:
>>
>>
>> My worry about "just pick a mainstream JS framework and use it via
>> JSInterop" is that if you're a) coupled to a JS environment for unit
On Monday, November 16, 2015 at 1:28:16 PM UTC+1, stuckagain wrote:
>
> Thanks for all the feedback. But it does not put my mind at rest right
> now.
>
> It would have been much better if GWT 2.8 would have provided at least the
> basis for the future of GUI development - because that was
David Chandler from Sencha answered a question about widgets and GWT 3.0:
https://www.sencha.com/forum/showthread.php?306057-GWT-3.0-Sencha-GXT-and-the-future-of-the-widget-eco-system-
"Thanks for the kinds words about GXT. We still don't have any more info on
GWT 3 than what has been
Ok, I think the issue regarding setLabels(String[] labels) is my fault.
Previously I had an interface that was annotated with @JsType and a class
that was implementing it and when I switched to the latest JS_RC JsInterop
I re-created the implementing class from scratch but with empty
Thanks for all the feedback. But it does not put my mind at rest right now.
It would have been much better if GWT 2.8 would have provided at least the
basis for the future of GUI development - because that was one of its main
selling points for me.
I understand why element/widget/uibinder are
> I'm not talking about a re-write here, I'm talking about new projects. For
> new projects, I can't see a compelling reason for picking GWT, if the devs
> are going to have to understand JS to use GWT then it is better to invest
> up front time in getting them familiar enough with JS to use
Hi
I am trying to write a test case for
https://github.com/gwtproject/gwt/issues/7247
There was an old test in
https://github.com/gwtproject/gwt/issues/7247#issue-87058425 that
reproduces the problem.
I am trying to narrow it down and implement it as part of the existing
I would also like a tip on how to run that testcase alone.
Right now I am doing this:
(cd user && ant test -Dtest.emma.selenium.disable=true
-Dtest.draft.htmlunit.disable=true -Dtest.coverage.htmlunit.disable=true
-Dtest.nometa.htmlunit.disable=true -Dtest.nongwt.disable=true
> I guess I will be trying UiBinder with GQuery and not rely on Widget for
> my project. The UiBinder might disappear, but we are using mostly plain
> HTML and Bootstrap styles. So we are only interested in binding events. The
> UiBinder templates will be easy to migrate later on.
>
FWIW this is
Errai UI ?
On 17 Nov 2015 00:41, "Stephen Haberman" wrote:
>
>
>> I guess I will be trying UiBinder with GQuery and not rely on Widget for
>> my project. The UiBinder might disappear, but we are using mostly plain
>> HTML and Bootstrap styles. So we are only
My hope would be that some enterprising individuals will start porting
pieces of GWT generators to annotation processors in the future. Some of
them are definitely doable without much effort
(CssResource/ClientBundle/etc) Some of them will require more work, but are
still possible (UiBinder with
On Sunday, 15 November 2015 15:37:29 UTC, Stephen Haberman wrote:
>
>
> My worry about "just pick a mainstream JS framework and use it via
> JSInterop" is that if you're a) coupled to a JS environment for unit
> testing and b) interfacing with a framework that is inherently
> dynamic/untyped,
Thanks for the info.
AFAIK JSNI syntax will go away at some point. I guess I would then rely on
a utility class to do that.
One more question:
Are there any restrictions regarding @JsProperty fields and Arrays ?
somehow following thing dosn't work (it's not set on the object , stays
On Mon, Nov 16, 2015 at 2:59 AM, Ümit Seren wrote:
> Thanks for the info.
>
> AFAIK JSNI syntax will go away at some point. I guess I would then rely on
> a utility class to do that.
>
>
There is going to be a replacement for JSNI by supplying supplementary js
files. So if
17 matches
Mail list logo