Note sure if this will gelp you much - we're a Gradle user, and don't use
intellij. But the basic principles are the same.
When we migrated to the latest GWT we also updated our top level gradle
build file to have a gwtSuperDev task which does all the heavy lifting for
us:
task
As noted in the post - we didn't get around to trying Domino REST. By the
time we discovered it, we'd already made the decision to stick with GWT-RPC
and move on to other work. It's possible we'd revisit that, but we'd
probably want to see some worked examples of how to transition from GWT-RPC
We got to a similar point. Looked in depth at moving the GWT front end to a
REST API - but found two big drawbacks:
1. none of the frameworks we could find had async callback handling
similar to GWT-RPC, with common interface classes client server side AND
support JAX-RS
I can't comment on the Eclipse plugin side of things, because we don't use
those. But I can confirm that basic GWT 2.9/2.10 compilation works fine
under Java 11 - that's our main Java platform now. I do recall some
migration notes in the GWT 2.9 or 2.10 release notes we had to take care
over,
Interesting stuff. Have looked at Vaadin and WebSwing (commercial) in the
past - but yours is an interesting take/approach. Will be good to see how
it progresses.
On Wednesday, 9 November 2022 at 12:39:48 UTC Jonathan Franchesco Torres
Bca wrote:
> Hi,
>
> And what about JFC Swing which is
Nice - actually proved a very decent little library for us, and easy to
embed on the 2 panels where we wanted context sensitive coloring. We even
got syntax error markers in the margins working - our server code already
parsed and reported lines in error, so it was just a case of figuring the
>From memory, I think we took the easy way around and fell back to the
non-module version of the underlying JS, which fortunately were available
for the lib we were using. Those then just got added to the other JS files
we include direct on our app's base HTML.
On Wednesday, 21 April 2021 at
BAD experience with their support, we paid the fee for
> years, and in the last times we got a very LIMITED support!
>
> In any case, we are using GXT 4.0.2 and GWT 2.9.0 for a long time without
> any issue, but we never tested it under Java 11...
>
>
> On 25 Feb 2021, at 07:56
Not sure how many of you also use GXT, but just spotted an announcement
from Sencha that GXT 4.1 is out, with support for GWT 2.9.0 and Java 11
(although the latter is marked as a "should support").
In the middle of some othe rwork, so have yet to try it in our setup. Will
report back once we
Similar decision process for us. After a lot of research into Vue, React
etc we decided the switch over and learning curve just didn't pay back. Our
app scaffold in GWT is actually really solid, and it's easier for us to add
more modern approaches like a JSON based REST API and newer layouts
Our web front end is on 15 years with GWT as of this year, and we're
expecting 5 more with luck. So we'll hit the 20 year mark if all goes well
On Tuesday, 19 January 2021 at 10:46:44 UTC aka...@gmail.com wrote:
> I wonder if that will actually last for the next 10 years.
>
> On Tuesday,
Thomas has very kindly posted an answer to the above SO thread. So I think
I'm good!
On Monday, 2 November 2020 at 10:26:56 UTC RobW wrote:
> Just re-posting a Q I put on SO today in case anyone here has insights:
>
>
>
Just re-posting a Q I put on SO today in case anyone here has insights:
https://stackoverflow.com/questions/64643227/javascript-module-function-in-gwt-with-jsinterop
Basically, battling to figure how to integrate a library that is
implemented as a Javascript export function using JS modules
13 matches
Mail list logo
