As I tried to write an introductory article for GWT newbies I feel that it 
is so difficult to jump into the development of GWT:
- Docs are outdated
- There are a lot of nice UI frameworks for GWT (domino-ui, gwtbootstrap3, 
gwtmaterialdesign, vue-gwt, etc.)

So before I write my article I started a GWT project to be able to start 
faster with all those nice UI frameworks in GWT. The idea of this project 
is taken from Spring Boot Starters (
https://github.com/spring-projects/spring-boot/tree/master/spring-boot-project/spring-boot-starters
).

I call the project GWT Boot and GWT Boot Starters (has nothing to do with 
Spring Boot but use the idea of easy start and "boot" a new project but 
still be scalable).

https://github.com/gwtboot

It is still in progress and I hope to be able to write an introduction 
article for GWT with the ease of Spring Boot.

Before I continue to support all the UI frameworks available in GWT (see my 
list: https://github.com/gwtboot/gwt-boot-modules), I would like to know, 
whether this result is easy enough for GWT newbies:

(1) With simple stand-alone integrated Jetty from GWT: 
https://github.com/gwtboot/gwt-boot-samples

(2) With Spring Boot to deliver the HTML host file: 
https://github.com/gwtboot/gwt-boot-samples/tree/master/gwt-boot-sample-basic-with-spring-boot

The next question would be, should I continue to add support for those UI 
frameworks as I mentioned here:
https://github.com/gwtboot/gwt-boot-modules

or should I try to exchange the module.gwt.xml with my Java config idea 
first?
https://gist.github.com/lofidewanto/2262441fe61f887158347f68418f04e3

Opinions are welcome! Thanks,
Lofi

-- 
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to