On Apr 7, 2009, at 1:05 PM, Christopher Patterson wrote: > Consolidating feedback based on some discussion in #toppdzn : > > * Big +1 on having the MIME types in that dropdown be more human > readable. > * Rollie's been curating a set of GeoSilk icons for styler, which > includes icons to indicate vector-based / rasterized output. It'd be > nice to use these in the 'Type' column instead of the strings "Vector" > and "Raster". We could include tooltip text to clarify for newer users > via the "title" attribute.
The "GeoSilk" set, along with the canonical Silk set (http://www.famfamfam.com/lab/icons/silk/ ), are the ones used elsewhere throughout this new UI. You can find the most up-to-date version here: http://files.opengeo.org/geosilk/ > * Let's consolidate the "Workspace" and "Name" columns into Qualified > names > * Let's add "Title" as a column > * Both Qualified name and Title should link to GeoSearch pages > whenever those exist. Otherwise, let's leave the text unlinked. I think we also talked about making sure that the filter/search scraped the abstract and keyword metadata if it doesn't already. As Cholmes said, our UI should gently push people towards best practices. > I can turn these into a JIRA if that's best (I see that Mike created > GEOS-2836 for the human-readable dropdown text), but wanted to bring > these to the list for discussion first. > > Chris > > > On Apr 7, 2009, at 10:12 AM, 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 >> >> -- >> Andrea Aime >> OpenGeo - http://opengeo.org >> Expert service straight from the developers. >> >> ------------------------------------------------------------------------------ >> 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 > > > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
