Building SOFEA Applications with GWT and Grails
Last night, I spoke at the Denver Java User Group meeting. The consulting panel with Matthew, Tim and Jim a lot of fun and I enjoyed delivering my Building SOFEA Applications with GWT and Grails presentation for the first time. The talk was mostly a story about how we enhanced Evite.com with GWT and Grails and what we did to make both frameworks scale. I don't believe the presentation reflects the story format that well, but it's not about the presentation, it's about the delivery of it.
If you'd like to hear the story about this successful SOFEA implementation at a high-volume site, I'd recommend attending the Rich Web Experience next month. If you attended last night's meeting and have any feedback on how this talk can be improved, I'd love to hear it.
Posted by Isaac López on November 12, 2009 at 05:40 PM MST #
Posted by Ryan Crumley on November 12, 2009 at 10:34 PM MST #
Posted by Matt Raible on November 13, 2009 at 12:25 AM MST #
Posted by Ryan Crumley on November 13, 2009 at 12:36 AM MST #
Posted by uberVU - social comments on November 13, 2009 at 01:43 AM MST #
Posted by Scott Ryan on November 13, 2009 at 03:30 PM MST #
I for one think that the client-side managed presentation flow forces one to reinvent something like Spring MVC or Grails Controllers/GSP inside some client technology like GWT.
Not that this is wrong, but dont expect your custom solution or any of the existing stuff (mvp4g, gwt-mvc, gwt-presenter) to be as mature as the existing serverside frameworks.
Posted by Sakuraba on November 13, 2009 at 06:46 PM MST #
Posted by Mandy on November 14, 2009 at 01:40 PM MST #
Matt at page 24 you say GWT widgets are great.
I have found this blog entry
http://www.cforcoding.com/2009/10/lost-in-translation-or-why-gwt-isnt.html
that say exactly the opposite.
I wonder if you can shortly say your motivation about GWT widgets being great
Posted by ivano on November 16, 2009 at 06:23 PM MST #
@Ivano - it is true that the native GWT widgets leave something to be desired. However, it was pretty easy for me to extend the SelectBox to create a Facebook-style autocomplete with GWT. The hardest part was figuring out the CSS.
When I saw "the widgets are great", I'm largely comparing GWT to other component-based frameworks. The thing I really like about GWT widgets/components is they're all-Java so you can easily extract them and use them in other applications. With Tapestry, JSF, etc., you usually need a Java file and a template to create a re-usable component.
Also, I've used GXT on my last couple projects. It's widgets are very slick, even if the library itself isn't very GWT-ish.
IMO, it's entirely possible that GWT works great for me, but it won't work well for others. It's all about what you like. After all, there is no "best" web framework.
Posted by Matt Raible on November 16, 2009 at 08:35 PM MST #
Posted by ivano on November 17, 2009 at 10:16 AM MST #