[QGIS-Developer] Best Practices in Plugin Development Workflows for Qt6/QGIS 4
Eithan Schonberg
eithan.schonberg at gmail.com
Sun Dec 21 02:26:36 PST 2025
Hi Everyone,
I am currently developing several internal plugins and looking to adapt my
workflow to work best with QGIS 4 and Qt6.
Looking at the current ecosystem, I’ve noticed that some staple tools
like *Plugin
Builder* and *pb_tool* haven't seen updates in several years. This makes it
difficult to establish a "best practice" workflow for new projects.
I have a few specific questions regarding the recommended direction for
plugin development:
1) UI Files: Pre-compiling vs. Dynamic Loading
With compiled resources being deprecated in Qt6, what is the current
consensus on .ui files? Should we continue to pre-compile them to Python
classes, or is move toward dynamic loading via `uic.loadUiType` preferred?
Note: I recently opened an issue (#64364) regarding problems with dynamic
loading when UI files contain full namespaces for all enums.
https://github.com/qgis/QGIS/issues/64364
2) Tools
qgis-plugin-ci is powerful and meant for web deployment and feels heavy for
local zipping and deploying. Since pb_tool seems unmaintained, are there
newer, lightweight alternatives that the community is adopting for building
and packaging plugins?
3) Documentation Updates
The PyQGIS Cookbook still suggests Plugin Builder and compiled resources.
Is there newer documentation I couldn't find or should I open an issue for
that too?
thank for all the help
Eithan Weiss Schonberg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20251221/2c16718d/attachment.htm>
More information about the QGIS-Developer
mailing list