I don't think so. There are more important questions to think about, like:
How will GWT 3 look like? Which features will carry over? Who ports what?
When to start porting, given that JsInterop 1.0 and a beta of
jsinterop.base is available? Do we create a new repository for GWT 3 to
give it a
Thanks Rogelio. That's helpful.
Can you share an example or code sample? The documentation on Editor
framework is very limited and hard to follow.
Also, I would love to use Errai data binding. But for declarative data
binding using Errai, I would have to use Errai IOC, and it doesn't
Dissenting opinion, mostly for the sake of discussion (though I'll admit to
being an RPC fanboy too):
This came up in discussion in ##gwt today, from the other perspective - the
stockwatcher app uses JsonpRequestBuilder, which is incompatible with
JsType without some seriously fugly casts (as
Should we start thinking about removing GWT-RPC from our sample app? (and
probably tutorial on the web site)
What would we replace it with though? I'd suggest plain old HTTP with JSON
and JsInterop; but what about the server? Using HTTP POST with
manually-encoded
Hi,
where can I init or dispose the server side objects that have to be there
for whole time the server is running?
--
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
On Tuesday, April 18, 2017 at 6:03:29 PM UTC+2, Magnus wrote:
>
> Hello,
>
> after moving my projects to Maven, I am at a point where everything works
> again, with the help of the people in this group.
> However, when concentrating on the actual work again, I notice that the
> development
I have long been able to successfully debug with sourcemaps in Chrome. We
are seeing an issue specific to Microsoft Edge in our application so I
would like to debug there. We are using GWT 2.8.0 and the Eclipse IDE.
(1) The application is compiled with *safari* in the *user.agent; *is
that
1. Sure, you will just need to implement an Editor interface in your
component using your *Element.
2. I can think of one way of doing this; you would still bind an input
element to each type, and then display only the one you want to use/handle
(if you can live with that). Not sure I see the
Hi Pavlo!
I have similar projects structure and do next:
> - start my-app and code server for my-app. In my case I use jetty maven
> plugin to start application and gwt plugin to start code server
> - do your changes in my-lib and mvn install after that. It should be very
> fast because there
Check the flag
четверг, 20 апреля 2017 г., 6:07:41 UTC+7 пользователь Tharpa Roberts
написал:
>
> I am maintaining a legacy application, which uses GWT 2.6.1. I am trying
> to run it in Eclipse. I have added the line
>
>
>
> to my Acme.gwt.xml file. I am selecting, "Debug As GWT
10 matches
Mail list logo
