On Sat, Apr 5, 2014 at 1:13 PM, Etienne Tourigny <[email protected]>wrote:
> > > > On Sat, Apr 5, 2014 at 1:00 AM, Nathan Woodrow <[email protected]>wrote: > >> 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. >> > > the processing/sextante plugin is both in core and also can be updated. > Same thing for ftools and gdaltools. > > >> >> 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. >> >> Something like the value tool could easily be integrated into the >> identify tool for instance. >> > > I agree, more or less - I thought about integrating it into the main > identify tool, but as it works with raster layers only, how would you > display raster and vector layers? > I have implemented most features of the Identify Tool plugin to the main identify map tool in master, here is the pull request. https://github.com/qgis/QGIS/pull/1293 > > >> 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. >> >> So +1 for adding the functions but -1 for just bringing the plugins into >> core. >> > > Not sure they would make it into core then, as development cost fof > integrating into core is much higher than adding them as core python > modules. For instance, the openlayer plugin would probably need quite a lot > of work to be ported to c++. > > On the other hand, anything that relies on qwt would be better handled. > Butanthing that uses python plotting libraries would obviously not work. > > cheers > Etienne > > >> >> - Nathan >> >> >> On Sat, Apr 5, 2014 at 1:22 PM, AntonioLocandro < >> [email protected]> wrote: >> >>> I think it's a great idea, I was actually thinking about this the other >>> day >>> and glad you brought the topic. >>> >>> Although we can install plugins certainly it becomes evident when a >>> plugin >>> should really become a core feature, example the Openlayers Plugin, I bet >>> almost all people using QGIS downloads it before doing anything with >>> QGIS. >>> Plugins extend QGIS functionality beyond what initially was thought but >>> in >>> many cases plugins become a must to be able to work efficiently >>> >>> If the plugins are added to core I would vote for blending the functions >>> coherently with the rest of the interface in the appropriate menus. A >>> good >>> example would be CAD tools which I would say be called Advanced Editing >>> or >>> something. >>> >>> I would add >>> >>> http://plugins.qgis.org/plugins/zoomtocoordinates/ >>> http://plugins.qgis.org/plugins/numericalDigitize/ - needs to add case >>> for >>> geographic coordinates >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://osgeo-org.1560.x6.nabble.com/Adding-plugins-to-core-tp5133202p5133245.html >>> Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. >>> _______________________________________________ >>> Qgis-developer mailing list >>> [email protected] >>> http://lists.osgeo.org/mailman/listinfo/qgis-developer >>> >> >> >> _______________________________________________ >> Qgis-developer mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/qgis-developer >> > >
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
