[EMAIL PROTECTED] ha scritto: > So the talk wasn't enough to make any strong statements, but I was left > with the impression that unless you want to Grails for the sake of > Groovy, then there was little reason to consider anything but GWT or > Wicket (ie. Tapestry and Struts 2 got grounded). > > I'm not the best person to ask, but personally I am leaning a little > towards GWT, just because the code/template is less spread (just the > .java files, I don't have to update a template and recompile something > else). I think it may also make it easier to make something that doesn't > look really ugly.
Hum, with GWT you can develop in pure java and the compile just afterwards. The issue is, the compiler want to see all the UI. So this means, you may be able to split the UI code in more modules, but the moment you compile it, it's cast in stone. So you have to be in the build environment to decide which modules you want in the UI, and once is done, is done, there is no removing or adding. That's why I ended up discarding it the first round of evaluations. It may work, but we have to lower the barrier of what we want out of our UI. Also, with GWT I'm not sure how much we'd be able to leverage a web page designer work, that is, we probably can, but we'd end up looking at his templates and then try to replicate them in code, right? Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
