+1 by me If it is a core plugin/functionality, means that it is of interest for most users, makes no sense to turn it off.
This will solve a few common issues for newcomers. Nathan Woodrow <madman...@gmail.com> escreveu no dia segunda, 12/12/2016 às 11:21: > +++++1 > > Yes please. if it's core (plugin or not) it shouldn't be optional and > should be enabled always. > It's just confusing for people and honestly doesn't feel right having core > parts disabled/enabled, imagine if > the style dock or atlas stuff, etc was optional. Messy and confusing. > > The other issue is when some of us don't run with all core plugins enabled > all the time it's hard to judge the > full state of things as a complete package e.g I see tons of screenshots > with the shortest path > plugin enabled and taking half the dock space when I bet most people would > never use it. > > So a massive +1 from me on this one. > > - Nathan > > > On Mon, Dec 12, 2016 at 9:05 PM, Victor Olaya <vola...@gmail.com> wrote: > > Hi > > This has been discussed in the past, but i think no decision was > taken, so I want to bring back the discussion. > > I think that core plugins should not be visible in the plugin manager, > and users should not be able to disable them. If they are core, they > should be active (the menus and buttons can be removed with the > "View/Customization..." functionality if the user wants to) > > Since we removed the ftools plugin and now have the corresponding > functionality from Processing, some users are confused for not finding > the usual tools there. We have kept the same menus, for those that are > used to them and dont want to use the toolbox. However, if users do > not have Processing enabled, they won't see those menus. And it is not > obvious that they have to enable Processing to get something that > previously was a different plugin.. > > I think this is an interesting discussion, so if you have ideas or > think that this might have disadvantages, let's talk about it in here. > > > Thanks! > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer -- Alexandre Neto --------------------- @AlexNetoGeo http://sigsemgrilhetas.wordpress.com http://gisunchained.wordpress.com
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer