From 660f3b69875a0117bdf645040b0f457feae98cbb Mon Sep 17 00:00:00 2001 From: Nyall Dawson Date: Tue, 16 Jan 2018 20:22:23 +1000 Subject: [PATCH] link to python docs for gui widgets instead of c++ docs --- Plugin-migration-to-QGIS-3.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Plugin-migration-to-QGIS-3.md b/Plugin-migration-to-QGIS-3.md index 8d7ca32..5b65a99 100644 --- a/Plugin-migration-to-QGIS-3.md +++ b/Plugin-migration-to-QGIS-3.md @@ -1,6 +1,6 @@ QGIS 3 has entered code freeze. It's, therefore, time to port your plugin. -While you are porting/rewriting your plugin, think about using QGIS native widgets. For instance, if you need a combobox providing a list of layers, use a `QgsMapLayerComboBox` instead of a `QComboBox`. There is also `QgsFieldComboBox` if you need to pick a field in a vector layer. The full list of widgets is here https://qgis.org/api/group__gui.html It's less code to write for you, and users will have the same user experience across plugins and QGIS Desktop. +While you are porting/rewriting your plugin, think about using QGIS native widgets. For instance, if you need a combobox providing a list of layers, use a `QgsMapLayerComboBox` instead of a `QComboBox`. There is also `QgsFieldComboBox` if you need to pick a field in a vector layer. The full list of widgets is here http://python.qgis.org/api/gui/index.html It's less code to write for you, and users will have the same user experience across plugins and QGIS Desktop. Also think about using the Processing framework. Your plugin can become its own Processing provider so your algorithms can be included in models and have the same UI as native algorithms. It's also less code to write, the UI is managed by QGIS. In QGIS 3, Processing has been refactored and is much more powerful than in QGIS 2.