QEP 29: QGIS 3.0 about qgis-enhancement-proposals HOT 14 CLOSED

@NathanW2 I've update this QEP proposal. Basically I've stripped out everything contentious (eg double-length development cycle) and left in two main points:

• after 2.14 we will release 3.0, which is an API break for Qt5/Python 3.0/PyQt5 requirements
• only low-risk/low-impact changes allowed for 2.14

This should allow us to pass this proposal quickly, and then further considerations (eg timing for 3.0 release - double cycle or not?) can be discussed as seperate issues. The important thing first is to determine that the next release after 2.14 will be 3.0...

from qgis-enhancement-proposals.

@NathanW2 in other words, this is ready for voting

from qgis-enhancement-proposals.

+1 from me - nice simple and clear roadmap. Just worried about what will happen without web views...many plugins out there probably rely on it too - for example InaSAFE (which I work on) uses them heavily in the UI and in composer.

from qgis-enhancement-proposals.

@timlinux yes, it's really unfortunate, and I'd really hoped Qt would have sorted this mess out now that Qt5 has been out a while. Painful, but totally out of our control and something we'll/our users will just have to live with.

from qgis-enhancement-proposals.

@NathanW2 I don't know Qt5 very much but are the current QWebView/QWebPage so different from Qt4's? http://doc.qt.io/qt-5/qwebview.html

from qgis-enhancement-proposals.

@giohappy see http://stackoverflow.com/questions/29055475/qwebview-or-qwebengineview - QWebView has also been deprecated and will be removed from Qt as of 5.6 (see https://wiki.qt.io/New_Features_in_Qt_5.6). We could use it temporarily, but can't rely on it being available on all our platforms/Qt versions. The future is QtWebEngine, which (currently) has no support for printing or rendering webpages. It's on their TODO list for 5.7 (see https://trello.com/c/JE5kosmC/72-printing-support), but given:

1. it's been continually pushed back since 5.4 - who knows when it will eventually land, and if it will be usable for our needs
2. we'll have to support Qt5 < 5.7 (or whenever it lands) for the forseeable future anyway, so can't rely on this.

In short - It's a huge mess, and it won't be sorted out by Qt/distros/etc before QGIS 3.0.

from qgis-enhancement-proposals.

Thanks @NathanW2 now it's clear. I see that a lot of improvements have been
made on 3D and OpenGL support: stop doing web dev and let's focus on 3D :D
Il 10/nov/2015 23:15, "Nyall Dawson" [email protected] ha scritto:

@giohappy https://github.com/giohappy see
http://stackoverflow.com/questions/29055475/qwebview-or-qwebengineview -
QWebView has also been deprecated and will be removed from Qt as of 5.6
(see https://wiki.qt.io/New_Features_in_Qt_5.6). We could use it
temporarily, but can't rely on it being available on all our platforms/Qt
versions. The future is QtWebEngine, which (currently) has no support for
printing or rendering webpages. It's on their TODO list for 5.7 (see
https://trello.com/c/JE5kosmC/72-printing-support), but given:

1. it's been continually pushed back since 5.4 - who knows when it will
   eventually land, and if it will be usable for our needs
2. we'll have to support Qt5 < 5.7 (or whenever it lands) for the
   forseeable future anyway, so can't rely on this.

In short - It's a huge mess, and it won't be sorted out by Qt/distros/etc
before QGIS 3.0.

—
Reply to this email directly or view it on GitHub
#29 (comment)
.

from qgis-enhancement-proposals.

• What would be the developpment / freeze time for 3.0? Same as the others or longer?
• Is there a list of proposed major changes / API break?
• For Qt5, does #2430 will be merged soon (in 2.14) so we can start building/testing with Qt5/Py3 now and make it a requirement for 3.0?

from qgis-enhancement-proposals.

What would be the developpment / freeze time for 3.0? Same as the others or longer?

That's been deliberately left out of scope for this QEP - the important thing to decide first is that we'll go 2.14 -> 3.0, and what that means. Timing can be discussed in a followup QEP, but I want to avoid this getting side tracked in other details.

Is there a list of proposed major changes / API break?

Same as above... (apart from the mentioned Qt5/Python 3.0 minimum version requirements)

For Qt5, does #2430 will be merged soon (in 2.14) so we can start building/testing with Qt5/Py3 now and make it a requirement for 3.0?

That's the plan

from qgis-enhancement-proposals.

makes sense to me, thanks for the clarification!

from qgis-enhancement-proposals.

@timlinux do you think we can make a vote thing for this?

Any comments from anyone else before we go to that step?

from qgis-enhancement-proposals.

@NathanW2 This should be rejected, right?

from qgis-enhancement-proposals.

Hi @nyalldawson

@NathanW2 This should be rejected, right?

Yes I think so - according to our plan, we will first release 2.16 with wrappers for Qt5 support and then deprecate Qt4 in the subsequent 3.0 release.

from qgis-enhancement-proposals.

Apparently this does not reflect the current roadmap anymore:

https://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule

from qgis-enhancement-proposals.