Justin Deoliveira wrote: > An example off the top of my head would be integrating geoserver with > another components... say for instance we wanted to bundle up Geonetwork > as a geoServer extension. (This is hypathetical yes). But it already has > its own tools and methods for configuration, so i don't see much point > in redoing it in the GeoServer user interface. > Fair example; could we ask for a small user interface contribution - a simple link to the GeoServer UI showing up once a administrator has signed in? > Anyways, I agree that a user interface is important for any extension... but > not as important as keeping a low entry barrier imho. The last thing I want > to tell a developer who is willing to spend time to maintain a contribution > that they have to learn wicket and build a pretty user interface before we > accept it. > I understand and respect your concern here; if this was a developer facing product like GeoTools I would be in agreement, I view GeoServer as moving out of research mode and into product mode for GeoServer 2.x series - as such I like to stick to my guns on this one. The user interface is the application; and if a customer is paying me to bring a module in as a geoserver extensions I could not honestly expect them to take me seriously if the functionality did not show up in the user interface.
Jody ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
