Hmm. I think that menu is likely to be used by standard users as well as developers. If I wanted to get a shapefile output, I would need to navigate this menu and I would only find SHAPE-ZIP, which someone may not know is a zipped shapefile. Okay maybe not the best example, but I still think it should be user facing if at all possible. (I know it's easy for me to say this since I won't be the one coding it!)
I can file a JIRA for this, and Those Who Implement can decide whether to fix or ignore? Thanks, Mike Pumphrey OpenGeo - http://opengeo.org Andrea Aime wrote: > Mike Pumphrey ha scritto: >> Thanks Andrea. Screenshots are very helpful for those who aren't >> ready to build their own trunk. :) >> >> Q: Are we going to replace the MIME types in that pull down list with >> more human-readable entries? Or perhaps have the MIME types in >> parentheses (or as tooltips?) > > Mumble, I'm a little torn on that one. That drop down is kind of the > "advanced" thing of that dropdown. To make for human readable names > we'd have to extend the output formats classes to provide a straight > name, or try to use the mime as an entry into the i18n files (not sure > mime types are valid property names thought). > Not sure which path to go, but the issue might be deeper than just the > UI page code. > > Cheers > Andrea > ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
