differentiate between built-in plugins and user plugins

[qgib]

Author Name: Olivier Dalang (@olivierdalang)
Original Redmine Issue: 9405

Redmine category:plugin_manager
Assignee: Borys Jurgiel

---

Hi !

I find it unclear for the user that user-installed plugins and built-in plugins are not differentiated at all.

Problems :

• hard for the user to understand why a plugin can be uninstalled why another can't
• it feels like someone already installed a lot of plugins when you may actually work on a fresh and clean install
• this is made even worse when some of the built-in plugins are invalid

Possible solutions:
A. (easy) : list the system plugins at the bottom of the list, with a separator between the user plugins and the system plugins
B. (medium) : add a "system plugins" tab alongside "All","Installed",etc. This would make sense since a built-in plugin is not actually "installed" (at least not by the user)

Thanks for the great plugin manager ;)

Olivier

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• fixed_version_id was configured as Future Release - Nice to have

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• easy_fix was configured as 0

[qgib]

Author Name: Borys Jurgiel (@borysiasty)

---

Fixed in 87d087b

As the number of core plugins is decreasing and we're going to remove them all some day (implementing as non-plugin core functions), I didn't create any new tabs. Instead, there is a color bar stating "This is a system plugin, so you can't uninstall it" on top of the plugin description (similarly to all those "This is a trusted plugin" etc.

---

• description was changed from Hi !

I find it unclear for the user that user-installed plugins and built-in plugins are not differentiated at all.

Problems :

• hard for the user to understand why a plugin can be uninstalled why another can't
• it feels like someone already installed a lot of plugins when you may actually work on a fresh and clean install
• this is made even worse when some of the built-in plugins are invalid

Possible solutions:
A. (easy) : list the system plugins at the bottom of the list, with a separator between the user plugins and the system plugins
B. (medium) : add a "system plugins" tab alongside "All","Installed",etc. This would make sense since a built-in plugin is not actually "installed" (at least not by the user)

Thanks for the great plugin manager ;)

Olivier to Hi !

I find it unclear for the user that user-installed plugins and built-in plugins are not differentiated at all.

Problems :

• hard for the user to understand why a plugin can be uninstalled why another can't
• it feels like someone already installed a lot of plugins when you may actually work on a fresh and clean install
• this is made even worse when some of the built-in plugins are invalid

Possible solutions:
A. (easy) : list the system plugins at the bottom of the list, with a separator between the user plugins and the system plugins
B. (medium) : add a "system plugins" tab alongside "All","Installed",etc. This would make sense since a built-in plugin is not actually "installed" (at least not by the user)

Thanks for the great plugin manager ;)

Olivier

• status_id was changed from Open to Closed
• resolution was changed from to fixed/implemented

[qgib]

Author Name: Harrissou Santanna (@DelazJ)

---

Borys, how about using "Core plugin" instead of "system plugin"? This is how they are called all over the documentation http://docs.qgis.org/testing/en/docs/user_manual/plugins/core_plugins.html.

[qgib]

Author Name: Borys Jurgiel (@borysiasty)

---

Harrissou Santanna wrote:

Borys, how about using "Core plugin" instead of "system plugin"? This is how they are called all over the documentation http://docs.qgis.org/testing/en/docs/user_manual/plugins/core_plugins.html.

Ah, thanks a lot! How could I forget the right term... Apparently I'm getting old :)
Fixed in 1c8803c
Btw. Any fixes to my wording are always welcome!