<div dir="ltr"><div>Table Manager helps renaming, reordering fields (not yet available) and while removing/deleting/reordering fields, you can preview how your table will look like.<br></div>I'm neither for enabling plugins by default but adding in Core such _basic_ features users look for will be an improvement<br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-12-03 23:10 GMT+01:00 Andreas Neumann <span dir="ltr"><<a href="mailto:a.neumann@carto.net" target="_blank">a.neumann@carto.net</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
But why?<br>
<br>
Most of the table manager functions are already in Core. It is
perfectly possible to add and remove columns without the table
manager.<br>
<br>
If some of the table manager functions are still missing in core, it
is better to bring the missing functionality into core, rather than
enabling Table manager by default.<br>
<br>
I am not a fan of having many Python plugins enabled by default,
because they slow down the loading of QGIS. Also, Python plugins are
a major source of additional bugs ...<span class="HOEnZb"><font color="#888888"><br>
<br>
Andreas</font></span><div><div class="h5"><br>
<br>
<div>On <a href="tel:03.12.2015%2023" value="+33312201523" target="_blank">03.12.2015 23</a>:02, DelazJ wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Agree with you, Bernd, that features like the ones provided
by "Table Manager" plugin should be in QGIS by default.
However, installing (and enabling) by default other dev's
plugins mean that QGIS dev team should somehow be responsible
of its stability; there are already Core plugins (Processing,
DBManager...) and I'm not sure they should have to do this
with other plugins.<br>
</div>
<div>+1 to have "Table Manager" features in Core but not really
in favour of activating plugins unless they integrate the Core
plugins schema.<br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-12-03 20:59 GMT+01:00 Bernd
Vogelgesang <span dir="ltr"><<a href="mailto:bernd.vogelgesang@gmx.de" target="_blank">bernd.vogelgesang@gmx.de</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>Am 03.12.2015, 20:14 Uhr, schrieb Paolo Cavallini
<<a href="mailto:cavallini@faunalia.it" target="_blank">cavallini@faunalia.it</a>>:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
I wonder what is the criterion to mark a plugin as
featured. There is<br>
even one featured plugin which is now deprecated.<br>
Perhaps we should have clear criteria for inclusion, and
keep the list<br>
updated?<br>
All the best.<br>
</blockquote>
<br>
</span>
With new users in mind, I wonder if the plugins page is
really the resource for picking a plugin, or if they just
search through the plugin manager for things they might
need, cause it does provide the exact same informations as
the website (minus those tags).<br>
<br>
More important for me would be the question, which plugins
are installed and enabled by default. And I ask the question
again (I never got an answer on that before): Why e.g. is
the Table Manager not installed and available by default? As
ESRI shape is the major output format, a novice starting to
use QGIS has no tool to alter the attribute table, which is
IMHO an unnecessary obstacle.<br>
I bet there are not few people fumbling around in the dbf
before realizing that there is a plugin available.<br>
<br>
Just my two cents<span><font color="#888888"><br>
Bernd<br>
<br>
<br>
-- <br>
Bernd Vogelgesang<br>
Siedlerstraße 2<br>
91083 Baiersdorf/Igelsdorf<br>
Tel: 09133-825374</font></span>
<div>
<div><br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a></div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Qgis-developer mailing list
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a>
List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br></blockquote></div><br></div>