sharpetronics/QGIS
1
0
Fork 0
mirror of https://github.com/qgis/QGIS.git synced 2025-08-11 00:03:56 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updated Plugin migration to QGIS 3 (markdown)

Etienne Trimaille 2018-01-11 15:53:58 +03:00
parent a2db0dc5d5
commit b8c3bae174
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Plugin-migration-to-QGIS-3.md

@ -1,8 +1,10 @@
QGIS 3 has entered code freeze. It's therefore time to port your plugin. 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 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 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.
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. 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 (running as a background task ...).
In QGIS 3, GeoPackage is much more present. Avoid creating shapefile in your plugin if possible and use the OGC standard GeoPackage format which can store both raster and vector in a single file: http://www.geopackage.org
## Minimal info ## Minimal info