Andrea Aime wrote: >> It is too bad I was not able to quantify the difference in needs >> between GeoServer and uDig - it is mostly an "ease of use" thing - >> basically uDig requires a plug-in to work out of the box and provide >> errors/warnings in a form that do a casual user some good. > Hum, do you mean the exception error messages to be used as user > messages? That is part of it ... it really comes down to "ease of use"; uDig expects things to work out of the box, and perform at interactive speeds. If they do not providing error messages in a form a normal person can understand is a distance second priority. An error message about connection pools is not going to help for example, and error message that explains what went wrong and some steps you could consider when fixing it would.
In terms of specifics ...you know how GeoServer extends plugins a degree of trust (that the quality is good enough that you can handle the support emails?). uDig has the same tradeoff but our user community is different. In terms of measurable: oracle makes the cut for GeoServer but not for uDig. Cheers, Jody ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel