Hi all<br><br>+1 for optionnal additionnal column, as it will be consistent for all use cases, and leave the choice to the user.<br><br>Michael<br><br><div class="gmail_quote">2012/5/22 Etienne Tourigny <span dir="ltr"><<a href="mailto:etourigny.dev@gmail.com" target="_blank">etourigny.dev@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, May 22, 2012 at 4:10 AM, Giovanni Manghi<br>
<<a href="mailto:giovanni.manghi@faunalia.pt">giovanni.manghi@faunalia.pt</a>> wrote:<br>
</div><div class="im">> Hi,<br>
><br>
>> I think the discussion on <a href="http://hub.qgis.org/issues/5621" target="_blank">http://hub.qgis.org/issues/5621</a> deserves more general<br>
>> discussion on this ML. Opinions? Could reporters make a short resume for us?<br>
><br>
<br>
</div>I guess the consesus in the issue is that the browser should display<br>
extension names, and that there should be an *optional* indication in<br>
the legends layer as to the provenance.<br>
<br>
However, any other display/tool (drop to DB manager and PG/spatialite<br>
in browser) should not use the extension.<br>
<br>
It was also mentioned that drop from browser should be consistent with<br>
"Add Layers" dialog (and also from the commandline). It is not<br>
currently in the case of vector layers.<br>
<br>
These alternatives have been presented, perhaps needing a user option:<br>
<br>
1) Always adding the extension and stripping it where necessary<br>
2) Never adding the extension and adding it in the legend<br>
3) Never adding the extension<br>
4) the legend could have an optional (for experts) additional column<br>
with data source format.<br>
<br>
1) and 2) deal more with a technical aspect in that the display name<br>
is set in QgsDataItem (by the QgsDirectoryItem in the browser case),<br>
so selectively changing that name based on the destination requires<br>
some consideration on the source (probably the uri + provider would be<br>
sufficient).<br>
<br>
Consensus on having the extension in the browser means that the<br>
QgsDataItem name must have the extension, but this must be removed<br>
when doing most D&D operations, which means more complexity.<br>
The alternative is to add the extension in the Browser (and possibly<br>
legend) based on the URI or perhaps a new member variable.<br>
<br>
Radim's solution to have an additional column specifying the<br>
datasource format (TIF, SHP, PG, etc.) is interesting, but might add<br>
clutter?<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
><br>
> I originally asked to avoid leave the extension while dragging and<br>
> dropping from the browser, mainly because when dropping into DB Manager<br>
> it is annoying to have to manually remove that ".shp" (example) from the<br>
> suggested table name.<br>
><br>
> On the other hand seeing the datatype in the TOC is useful and a thing<br>
> that many users have asked in the past.<br>
><br>
> Real life projects tend to be large, with many layers from many<br>
> datasources/types. Vectors are not just vectors, and rasters are not<br>
> just rasters: there are vectors that cannot be edited (lack of<br>
> permission or because gdal does not allow it), layers that cannot be<br>
> used as input by standard qgis tools (GRASS rasters), etc.<br>
><br>
> Sometimes the users have even layers with the same name but of different<br>
> type.<br>
><br>
> So, seeing the format in the TOC is a step forward in usability, and in<br>
> the ticket were suggested a few ways to get it.<br>
><br>
> cheers!<br>
><br>
> -- Giovanni --<br>
><br>
><br>
> _______________________________________________<br>
> Qgis-developer mailing list<br>
> <a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</div></div></blockquote></div><br>