<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>I agree completely with what you have written specially "+1 for adding the functions but -1 for just bringing the plugins into core." Maybe start with some of the easier ones like the value tool you mention<br> <BR><div><hr id="stopSpelling">From: madmanwoo@gmail.com<br>Date: Sat, 5 Apr 2014 14:00:41 +1000<br>Subject: Re: [Qgis-developer] Adding plugins to core?<br>To: antoniolocandro@hotmail.com<br>CC: qgis-developer@lists.osgeo.org<br><br><div dir="ltr">I agree that adding the plugins to core would be a good idea however I don't feel that we should just add them in their current state. The plugin repository has the benefit of of being able to update things faster then the release of QGIS itself if you find bugs, etc, you can also add features for older QGIS versions.<div>
<br></div><div>I think these features in the plugins are great but we should really integrate them into the core project itself as new features rather then just a plugin. Having Python plugins in core can also raise issue for users because they still look like normal plugins but you can't update them because they are no longer in the repository. Having to enable handy features also feels a bit hap hazard to me. </div>
<div><br></div><div>Something like the value tool could easily be integrated into the identify tool for instance. There are also some other concepts floating around the idea of bring CAD functions into core so I think it's best to just focus on making those stronger.</div>
<div><br></div><div>So +1 for adding the functions but -1 for just bringing the plugins into core.</div><div><br></div><div>- Nathan</div></div><div class="ecxgmail_extra"><br><br><div class="ecxgmail_quote">On Sat, Apr 5, 2014 at 1:22 PM, AntonioLocandro <span dir="ltr"><<a href="mailto:antoniolocandro@hotmail.com" target="_blank">antoniolocandro@hotmail.com</a>></span> wrote:<br>
<blockquote class="ecxgmail_quote" style="padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;">I think it's a great idea, I was actually thinking about this the other day<br>
and glad you brought the topic.<br>
<br>
Although we can install plugins certainly it becomes evident when a plugin<br>
should really become a core feature, example the Openlayers Plugin, I bet<br>
almost all people using QGIS downloads it before doing anything with QGIS.<br>
Plugins extend QGIS functionality beyond what initially was thought but in<br>
many cases plugins become a must to be able to work efficiently<br>
<br>
If the plugins are added to core I would vote for blending the functions<br>
coherently with the rest of the interface in the appropriate menus. A good<br>
example would be CAD tools which I would say be called Advanced Editing or<br>
something.<br>
<br>
I would add<br>
<br>
<a href="http://plugins.qgis.org/plugins/zoomtocoordinates/" target="_blank">http://plugins.qgis.org/plugins/zoomtocoordinates/</a><br>
<a href="http://plugins.qgis.org/plugins/numericalDigitize/" target="_blank">http://plugins.qgis.org/plugins/numericalDigitize/</a> - needs to add case for<br>
geographic coordinates<br>
<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://osgeo-org.1560.x6.nabble.com/Adding-plugins-to-core-tp5133202p5133245.html" target="_blank">http://osgeo-org.1560.x6.nabble.com/Adding-plugins-to-core-tp5133202p5133245.html</a><br>
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.<br>
<div class="ecxHOEnZb"><div class="h5">_______________________________________________<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></div></div> </div></body>
</html>