[Qgis-developer] should core plugins not be available in plugin manager?

[Régis Haubourg]

Hi all,
just a reminder that we have a --noplugins startup option that will
deactivate plugins for testing purpose.
What would be then the intended behaviour with core python plugins like
processing?

On my side, I would keep an option to do that, and if possible not rename
it. So this is an argument to support the idea of naming them plugin
(because they are plugins from a code point of view).

Thinking loudly, maybe a CLI option to choose explicitly the list of
plugins to load could even be better. That way default behavior will always
have plugins loaded, but edge uses cases still have a way to avoid loading
some at all.
Opinions?
Régis

2016-12-13 9:01 GMT+01:00 Paolo Cavallini <cavallini at faunalia.it>:

> Il 13/12/2016 08:08, Neumann, Andreas ha scritto:
>
> > I do agree though that some core plugins could be removed or integrated
> > into the core. One example is the coordinate capture plugin, which could
> > be easily integrated in core, e.g. integrated in the identify tool or
> > status bar.
>
> big +1 from me
>
> > Probably the EVIS plugin is another candidate with lots of overlaps. If
> > we add the missing functionality the EVIS plugin provides to core, we
> > could get rid of it.
>
> also a big +1 (could be more work though.
> All the best.
>
> --
> Paolo Cavallini - www.faunalia.eu
> QGIS & PostGIS courses: http://www.faunalia.eu/training.html
> https://www.google.com/trends/explore?date=all&geo=IT&q=qgis,arcgis
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20161213/6a0ba60d/attachment.html>