From d335dcf1077812dc7656120b66a58b050da6d574 Mon Sep 17 00:00:00 2001 From: Etienne Trimaille Date: Tue, 9 Jan 2018 16:19:39 +0300 Subject: [PATCH] Updated Plugin migration to QGIS 3 (markdown) --- Plugin-migration-to-QGIS-3.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Plugin-migration-to-QGIS-3.md b/Plugin-migration-to-QGIS-3.md index 4dd5509..55a2d03 100644 --- a/Plugin-migration-to-QGIS-3.md +++ b/Plugin-migration-to-QGIS-3.md @@ -8,6 +8,10 @@ Among the necessary info: When completed, we need to put out a call for plugin authors to start porting. +While you are porting/rewriting your plugin, think about using QGIS native widgets. For instance, if you need a combobox with 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 + +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 created by QGIS. + ## Minimal info - `pip install future`