Andrea Aime wrote: > 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. So what would we need to relax to use GWT? Probably the ability to "drop" more functionality into GeoServer in jar form.. leaving it as a build time only option. Andrea the origional model for dropping new functionality in was the WAR; is there any merit of the idea of separate WARs each done with GWT? I admit it bites off a whole whack of complexity (WARS sharing services via JNDI etc...) and is part of what Spring was designed to clean up... > 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? It is not completely clear cut like I first thought; a web designer can do a fair amount with style sheets on the generated result. But out of the box the basic layout is provided by the programmer.
Jody ------------------------------------------------------------------------- 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
