Re: [QGIS-Developer] Python API for 3D
On Sat, 29 Sep 2018 at 09:36, Nyall Dawson wrote: > > On Sat, 29 Sep 2018 at 00:21, Martin Dobias wrote: > > > > > I think for the time being we should still treat the 3D library as > > having unstable API - so I wanted to check how others would feel about > > having Python API for qgis_3d that would be marked as unstable, i.e. > > there may be changes between 3.x releases? I think with big warnings > > in the docs that the API may change we can get others to experiment > > with 3D functionality while not offending anyone too much if we break > > it later. The idea is that the API would get frozen at some point > > later in 3.x release cycle or for QGIS 4. > > I don't see an issue with this -- there's other parts of code exposed > to PyQGIS which is also clearly marked as non-stable. Some processing > classes for instance. Note this touches on discussion at https://github.com/qgis/QGIS/pull/8054 too. Quoting: "Maybe we should do qt approach and have "technology preview" classes, before classes mature? We could even do this as a general rule - new classes are tech previews for 2 minor releases." Nyall ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Python API for 3D
On Sat, 29 Sep 2018 at 00:21, Martin Dobias wrote: > > I think for the time being we should still treat the 3D library as > having unstable API - so I wanted to check how others would feel about > having Python API for qgis_3d that would be marked as unstable, i.e. > there may be changes between 3.x releases? I think with big warnings > in the docs that the API may change we can get others to experiment > with 3D functionality while not offending anyone too much if we break > it later. The idea is that the API would get frozen at some point > later in 3.x release cycle or for QGIS 4. I don't see an issue with this -- there's other parts of code exposed to PyQGIS which is also clearly marked as non-stable. Some processing classes for instance. Nyall ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Python API for 3D
Hi Matthias On Fri, Sep 28, 2018 at 4:47 PM Matthias Kuhn wrote: > Hi Martin, > I think that's a good move. Having an experimental Python 3D API is better > than not having a Python 3D API. And if it's communicated clearly, it's > every developers choice to build something on top of an unstable API. > Just to ask, do you have clear plans for API changes or is it more a move > to keep the door for API modifications open in case it turns out it is > required? > I don't really have any concrete plans for API changes within the 3D library - I just feel that it may easily happen in the future as we will be adding more functionality or refactoring existing code :-) Anyway I would try to keep the changes in API break docs so that devs have some guidance in case there are some breaks. Cheers Martin ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [QGIS-Developer] Python API for 3D
On Fri, Sep 28, 2018 at 4:21 PM Martin Dobias wrote: > Hi all > > I have been thinking it would be good to finally have Python API also > for qgis_3d library. Until now I have kept the 3D library > intentionally without Python bindings so that it is possible to move > the code around without being blocked by the API stability > requirement. > > I think for the time being we should still treat the 3D library as > having unstable API - so I wanted to check how others would feel about > having Python API for qgis_3d that would be marked as unstable, i.e. > there may be changes between 3.x releases? I think with big warnings > in the docs that the API may change we can get others to experiment > with 3D functionality while not offending anyone too much if we break > it later. The idea is that the API would get frozen at some point > later in 3.x release cycle or for QGIS 4. > > Cheers > Martin > Hi Martin, I think it's a good idea! ... if the warning is big enough and not light gray over a white background ;) -- Alessandro Pasotti w3: www.itopen.it ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
[QGIS-Developer] Python API for 3D
Hi all I have been thinking it would be good to finally have Python API also for qgis_3d library. Until now I have kept the 3D library intentionally without Python bindings so that it is possible to move the code around without being blocked by the API stability requirement. I think for the time being we should still treat the 3D library as having unstable API - so I wanted to check how others would feel about having Python API for qgis_3d that would be marked as unstable, i.e. there may be changes between 3.x releases? I think with big warnings in the docs that the API may change we can get others to experiment with 3D functionality while not offending anyone too much if we break it later. The idea is that the API would get frozen at some point later in 3.x release cycle or for QGIS 4. Cheers Martin ___ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
