Hi Richard,
Thanks for the feedback, very interesting.
We have been working on a plugin qgis2compat [1] that aims at being a
legacy layer, so you have to maintain only a single plugin.
1. Migrate to QGIS 3
2. Add some code to load the compatibility layer
3. Add missing compatibility fixes in the
On 31-10-16 23:15, Nyall Dawson wrote:
> Given that you're probably the first to go through this process, I'm
> very keen to hear any further feedback you have on the porting
> process. What did you find hardest? Is the available api break
> documentation useful? Could we make it better? Do you hav
How does one change 2.99 to 3.00 in the development version obtained
from GitHub because obviously there is a big break between 2.xx and
3.xx?
I believe the 3.00 version necessary for plugin development with Python
3.5.2 and Qt5.7. Or is that a mis-impression? Something that only
happens to
On 1 November 2016 at 07:37, Richard Duivenvoorde wrote:
> Hi (plugin-) devs,
>
> after upgrading my QGIS 2.18 plugin, I thought to try what I had to do
> to make it a QGIS3 version.
>
> - running scripts/2to3 on the plugin
> - tweaking and fixing untill it worked :-)
>
> it was more work then I h
Hi (plugin-) devs,
after upgrading my QGIS 2.18 plugin, I thought to try what I had to do
to make it a QGIS3 version.
- running scripts/2to3 on the plugin
- tweaking and fixing untill it worked :-)
it was more work then I hoped, but after setting
qgisMinimumVersion=2.99
qgisMaximumVersion=3.0
