--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/i-43poug6ME/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
Nothing too fancy, lots of RPCs. JPA for the back-end but we scrub the hibernate collections with Dehydrator before putting them on the wire. There's some SVG on the front-end to draw some pretty pictures and easily make vector PDFshttp://www.vectomatic.org/libs/lib-gwt-svgWe use UiBinder a tiny bit but it feels like overkill when you have custom widgets.I keep looking at requestFactory, but it seems like more work writing bean+interface+factory+locator than to write bean+RPC. Is there some advantage there I'm not seeing?
On Thu, Feb 11, 2016 at 6:23 AM, salk31 <sal...@gmail.com> wrote:
Seems like a good choice to start with ;)Any idea what bits of GWT you are going to use and backend technology? GWT doesn't really tie you to anything apart from Java source and JavaScript runtime.
I'm a huge Widget/UiBinder/Editor/RequestFactory/JSR-303/JPA fan but lots of variations that people use and work fine.
On Wednesday, February 10, 2016 at 11:09:12 AM UTC, koffi jean françois koffi wrote:I am new GWT developper and I have to make an enterprise application with GWT so I hope that you will be prompt to help me ... Thks
--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/i-43poug6ME/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsub...@googlegroups.com.