I can see why you would be frustrated ... and the GWT documentation is not
particularly good. For us superdev+browser debugging mode "just works" as
long as you do not change the linker. We don't have a massive app (~700K
lines of client-side java source code across 37 directory trees + lots
Well, let's name few problems here:
1) Source maps: I don't know why, but Chrome can't find them. I've tried
everything (I swear, I followed step by step every tutorial in earth - it
just wont work. It may be because our folder structure that is bit more
complex than those simple examples).
2)
Debugging of both the server and client code works great. I'm not sure why
it doesn't work for you. Client side debugging is done in the browser
console using source maps that are automatically generated by the GWT
compiler.
On Saturday, June 1, 2019 at 3:22:09 PM UTC-7, Edson Richter wrote:
>
On Sunday, June 2, 2019 at 1:19:40 AM UTC+3, Douglas de Oliveira Mendes
wrote:
>
> Ain't dead for me! Using it every day quite a lot. I still think it's a
> great option if you have tons of widgets, panels, tabs... I see GWT
> basically as an easier to distribute Java Web Start-like
On Saturday, June 1, 2019 at 10:51:55 PM UTC+3, Andrew Buck wrote:
>
> GWT is not dead! It's simply suffering from PR misunderstanding. People
> think that you have to use the old widget system to use GWT, but you don't.
> Just use Elemento instead of widgets and REST calls instead of RPC.
>
On Sunday, June 2, 2019 at 1:22:09 AM UTC+3, Edson Richter wrote:
>
> This is my opinion (from a person with more than 30 years of experience in
> software enginnering), and I respect every other persons opinion - I'll
> just not put my eggs on this basket for another 8 years "just to see if it
This is my opinion (from a person with more than 30 years of experience in
software enginnering), and I respect every other persons opinion - I'll
just not put my eggs on this basket for another 8 years "just to see if it
will get better".
Last year I had big issue with dates, because GWT has
Ain't dead for me! Using it every day quite a lot. I still think it's a
great option if you have tons of widgets, panels, tabs... I see GWT
basically as an easier to distribute Java Web Start-like plataform.
I'm sitcking with *RPC* because it maximizes client-server code reuse.
DTOs, Enums,
GWT is not dead! It's simply suffering from PR misunderstanding. People
think that you have to use the old widget system to use GWT, but you don't.
Just use Elemento instead of widgets and REST calls instead of RPC.
Regardless of what happens with GWT 3, using GWT 2.8 is future proof since
it
On Fri, May 31, 2019 at 10:44 AM Craig Mitchell
wrote:
> Off topic: I do wonder how web assembly (WASM) is going to impact GWT,
> especially if it gets garbage collection, and therefore makes Java to WASM
> compilation possible.
>
That is the biggest risk IMO. When we did our analysis to
Even though it is still working for us SDM works perfectly in large
projects long as your code isnt really too coupled, and regarding RPC you
might take a look here
https://www.slideshare.net/gwtcon/in-defense-of-gwtrpc-by-colin-alworth/
currently i am using domino-rest
Out of curiosity, what would prevent someone still build projects based on
current GWT 2.8.2 and keep using all the goodies? I think as of 2.8.2 it is
future proof especially with a shift to jsinteop included in current release
version? People even with current version took their own path and
Yep. Seems dead since we could not debug anymore. Superserver never worked -
and previous "classical" debug stopped working. Even Google is migrating
projects out of gwt.
Rpc is a nightmare in large apps.
So we are hiring developers to rewrite ui into Angular2+.
Hoping for a better future.
Just
I also posted a reply here for anyone reading this thread instead of the
other one
https://groups.google.com/d/msg/google-web-toolkit/-6KuZjHFD5c/yxouo-PHAwAJ
On Thursday, May 30, 2019 at 10:33:30 PM UTC+3, Bob Lacatena wrote:
>
> I just posted this elsewhere, but as this thread has more
This is one of the things that are preventing us from releasing 2.9
https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/VN4ATVrLrTA
any help here will be appreciated.
On Thursday, May 30, 2019 at 11:32:22 PM UTC+3, Michael Joyner wrote:
>
> Ideally, twice yearly release of
>
> With GWT getting old, this is becoming painful, because GWT did cool
> things, like animation and date pickers and rich text editors, by brute
> force back when that was necessary. Now, however, HTML5 and other things
> have evolved to offer better, cleaner solutions, but often it's
Ideally, twice yearly release of "stable", with most recent appropriate
patches applied, such as "2.201904" and "2.201910" or similar tagged
releases would definitely help there.
On 5/30/19 3:33 PM, Bob Lacatena wrote:
I just posted this elsewhere, but as this thread has more current
I just posted this elsewhere, but as this thread has more current
responses, I'm reposing it in the hopes that someone will read it:
GWT is suffering from a very serious publicity debacle. I'm actively doing
GWT development, and regretting every moment of it right now. Years ago I
loved
It would be good to have an approximate public release window for GWT 3.0 from
the community. Will it happen in 2019?
Also any plans to move release cadence for GWT to match Java’s 6-monthly cycles?
-Nick
> On 30 May 2019, at 10:54, Craig Mitchell wrote:
>
> Also, see here for more comments:
Also, see here for more comments:
https://groups.google.com/forum/#!topic/Google-Web-Toolkit/-6KuZjHFD5c
--
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
to
we had this question the other day but it was in the other form `Is GWT
dead`
TLDR: Yes it is still active and we made huge progress as a community
toward GTW 3.0, we now have a working j2cl maven plugin, and we have lots
of GWT2 ported modules working already in j2cl/gwt3. the ecosystem
hi guys,
i don't see or hear much about GWT.
Google has also come up with Flutter which I believe would compete with
React.
With all these new frameworks coming up and for which the community seems
quite active, is GWT still alive?
Is there any plan to release any new versions of GWT?
thanks!
ther, before posting my question.
Regards, Sam
On 19 February 2016 at 12:40, Lothar Kimmeringer <j...@kimmeringer.de> wrote:
> Am 19.02.2016 um 12:54 schrieb Sam Wootton:
>
> > Before posting my question, I just wanted to check that this
> > group was still active?
>
>
Am 19.02.2016 um 12:54 schrieb Sam Wootton:
> Before posting my question, I just wanted to check that this
> group was still active?
it is and before you ask you might check
https://groups.google.com/forum/#!forum/google-web-toolkit
if your question isn't already answered. ;-)
Cheers,
More than ever :)
On 19 Feb 2016 13:34, "Sam Wootton" <sam.woot...@gmail.com> wrote:
> Hello GWT Users,
>
> Before posting my question, I just wanted to check that this group was
> still active?
>
> Regards, Sam
>
> --
> You received this message beca
Hello GWT Users,
Before posting my question, I just wanted to check that this group was
still active?
Regards, Sam
--
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, sen
26 matches
Mail list logo
