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 plataform. >
I agree specially when you have lots of java developer in your workplace, it is easier for them to start with gwt than other framworks, > > I'm sitcking with *RPC* because it maximizes client-server code reuse. > DTOs, Enums, Exceptions, utility classes... We have Java and Groovy on the > server side. I believe RPC maximizes the strenghts of this setup. Some > colleagues dislike the calls being serialized. But I think if that's the > problem they'd just go after replacing the serialization of the RPC > mecanism to a JSON based one (maybe this "jackson" thing someone > mentioned?) instead of rewriting the RPCs into anything else. The server > side is ours, we write it in Java so let's stick with RPC, don't you think? > > I would like to use *validation* on the DTOs keeping them as POJOs (or > something like, closest to pure Java), but the GWT website scared me off > regarding that [1]. Another desire I have is avoiding interfaces having to > extend "RemoteSevice". Should be enough to write some XML or whatever to > tell which services are exposed, hence keeping the interfaces with no > dependencies to GWT. > I think you should take a look at domino-rest <https://github.com/DominoKit/domino-rest> and i promise you wont regret it, it is JaxRs compatible, works flawlessly in both gwt2 and gwt3/j2cl, you can use the same generated client in both client and server, interfaces are very clean, serialization is based on dominon-jackson <https://github.com/DominoKit/domino-jackson> so you can use DTOs with enums, collections, arrays ..etc. and i know that @Frank already used it to completely replace restyGwt from one of his apps. > > As for *widgets*, we mostly use Sencha GXT's components. > if you use lots of widgets i suggest you take a look at domino-ui <https://dominokit.github.io/domino-ui-demo/index.html?theme=indigo#home> you wont regret it i promise again:-). > I'm not sure if *default methods* in interfaces are already available. > Would be nice to have. > Java8 syntax is supported in gwt-2.8.2, i use default methods in interfaces all the time and they are pretty useful. > > I also miss *debugging* but I'm not sure if GWT should take any blame or > just my laziness for setting it back up. > > [1] "CAUTION: Validation API is unmaintained and will be moved out of GWT > SDK into a separate project after GWT 2.8." > http://www.gwtproject.org/doc/latest/DevGuideValidation.html > Next in my new libs queue is domino-validation stay tuned for it. :-) > > > Douglas > > > On Sat, Jun 1, 2019 at 4:52 PM Andrew Buck <[email protected] <javascript:>> > 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. >> Regardless of what happens with GWT 3, using GWT 2.8 is future proof since >> it supports JsInterop. GWT remains the most robust system to develop web >> apps with. Also, combined with J2ObjC, it remains the only way to write >> 100% native apps for web, iOS, and Android and share 70% of the code >> between all platforms. Other systems that let you share code don't produce >> truly native apps. >> >> >> >> On Friday, May 31, 2019 at 8:27:45 PM UTC-7, Peter Donald wrote: >>> >>> On Fri, May 31, 2019 at 10:44 AM Craig Mitchell < >>> [email protected]> 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 decide on >>> whether to commit to J2CL/GWT3.x for the next 10 years or not this was the >>> only real risk that we found (or that Typescript gets a lot better backend). >>> >>> WebAssembly is still a way off but projects like >>> https://github.com/i-net-software/JWebAssembly do seem to be something >>> to watch >>> >>> >>> -- >>> Cheers, >>> >>> Peter Donald >>> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/google-web-toolkit/dfe83c33-bdee-4dd8-ba78-7db137a81333%40googlegroups.com >> >> <https://groups.google.com/d/msgid/google-web-toolkit/dfe83c33-bdee-4dd8-ba78-7db137a81333%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/672a73e0-eb2a-4cee-a9ee-c028cf46c880%40googlegroups.com.
