<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Nathan<br>
<br>
>Personally I find the core plugin concept unnecessary. If it's
core it shouldn't be a plugin and should just be part of the main
program. It can still be Python that is fine however >users
shouldn't have to turn them on and off they should just be there
and be transparent.<br>
<br>
I think the plugin concept is highly usefull for both
core/noncore, C++ and Python plugins. It helps to keep code well
separated and avoids bloating the size of the main executable for
things which are rarely used ( read for e.g. here why size _does_
matter:
<a class="moz-txt-link-freetext" href="https://www.webkit.org/blog/2826/unusual-speed-boost-size-matters/">https://www.webkit.org/blog/2826/unusual-speed-boost-size-matters/</a>
). Many people never use e.g. grass plugin, evis, georeferencer,
globe. Plugins are a sophisticated way of keeping things lean and
separated.<br>
<br>
>however users shouldn't have to turn them on<br>
<br>
That's the same thing for toolbars which are hidden by default or
the browser. Many people don't notice those features. However, Iwe
cannot clutter the interface with everything by default just to
save the user from doing a click or looking up things in the
documentation or with google.<br>
<br>
Regards,<br>
Marco<br>
<br>
<br>
<br>
On 10.08.2013 12:42, Nathan Woodrow wrote:<br>
</div>
<blockquote
cite="mid:CAAi8Yg-h=F-PdAhH=i7vtUZe1XY=-A89XY9U+=_dvAVgjd3KcA@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">+1 from me too.
<div><br>
</div>
<div>Personally I find the core plugin concept unnecessary. If
it's core it shouldn't be a plugin and should just be part of
the main program. It can still be Python that is fine however
users shouldn't have to turn them on and off they should just
be there and be transparent.</div>
<div><br>
</div>
<div>IMO we should aim to kill of all C++ core plugins in 2.1
and make them core features.Things like the geometry checking,
spatial join, georeferencer should all be core features and
have C++ and Python APIs that the user can use.</div>
<div><br>
</div>
<div>- Nathan</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Sat, Aug 10, 2013 at 4:37 PM,
MORREALE Jean Roc <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:jr.morreale@enoreth.net" target="_blank">jr.morreale@enoreth.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote">+1 here for dropping the
SEXTANTE name for the same reason we now have a Vector menu
instead of fTools.<br>
<br>
I would vote for a "processing" menu as sextante goes beyond
analysis
<div class="HOEnZb">
<div class="h5"><br>
<br>
_______________________________________________<br>
Qgis-developer mailing list<br>
<a moz-do-not-send="true"
href="mailto:Qgis-developer@lists.osgeo.org"
target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
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>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Qgis-developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Dr. Marco Hugentobler
Sourcepole - Linux & Open Source Solutions
Weberstrasse 5, CH-8004 Zürich, Switzerland
<a class="moz-txt-link-abbreviated" href="mailto:marco.hugentobler@sourcepole.ch">marco.hugentobler@sourcepole.ch</a> <a class="moz-txt-link-freetext" href="http://www.sourcepole.ch">http://www.sourcepole.ch</a>
Technical Advisor QGIS Project Steering Committee </pre>
</body>
</html>