If you are loading them by default it doesn't make sense to keep them as a plugins better to just make them core. It doesn't really matter at the moment for 2.0 anyway but I'll chat about it more at the HF On 12/08/2013 6:02 PM, "Tim Sutton" <li...@linfiniti.com> wrote:
> Hi > > > On Mon, Aug 12, 2013 at 9:32 AM, Nathan Woodrow <madman...@gmail.com>wrote: > >> On Mon, Aug 12, 2013 at 5:13 PM, Marco Hugentobler < >> marco.hugentob...@sourcepole.ch> wrote: >> >>> Plugins are a sophisticated way of keeping things lean and separated. >> >> >> I have no issue with none core plugins, in fact that is something I >> always promote as a powerful feature. Core however plugins are a different >> story. While it makes sense to you and I it doesn't make sense to a normal >> user. Core plugins, while a feature, in fact make the program look >> incomplete or patchy. Some of the main problems with core plugins are: >> they don't have a Python C++ API, functions in them are separated by wall, >> users have to enable them in order to use them. >> >> Lets take a few examples: A question the other day on IRC was "can I >> create a heatmap with pyqgis" No is the answer which is confusing because >> the heatmap plugin is a core feature so why not have it as part of the API? >> The topology checker is another example of the features it has should be >> part of the core package and just baked in. This would allow tighter >> integration into the drawing tools and other core features. Can you imagine >> if snapping was a core plugin? or the composer? >> >> I do see the core plugin idea useful as a staging area for things we are >> not sure fully about just yet or still have issues. >> >> > I think this should be simple to address - maintain them as plugins but > load them automatically and transparently to the user. We could even have a > new class oc core plugins that do this and explcitly bypass the plugin > manager ui because they are always 'just on'. > > Regards > > Tim > > >> _______________________________________________ >> Qgis-developer mailing list >> Qgis-developer@lists.osgeo.org >> http://lists.osgeo.org/mailman/listinfo/qgis-developer >> >> > > > -- > Tim Sutton - QGIS Project Steering Committee Member (Release Manager) > ============================================== > Please do not email me off-list with technical > support questions. Using the lists will gain > more exposure for your issues and the knowledge > surrounding your issue will be shared with all. > > Irc: timlinux on #qgis at freenode.net > ============================================== >
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer