Supporting Qt5

[ian.rees]

I think that Qt 5 and Python 3 are two separate questions, though maybe Python 3 would require a new PySide and so Qt 5 would need to come first/concurrently? From a quick look, it appears that PySide 2 does not require Python 3.

Agree that it would be nice if we could use Python 3 in FreeCAD, but to me it seems better to switch to treat the two upgrades as different projects. I've personally got a longer list of bugs/features that would be helped by a Qt upgrade than the Python upgrade, so would vote for doing Qt first . -Ian-

[yorik]

There is one little problem with py3 which is pivy. But yeah, let's separate the subjects... Indeed in principle they don't seem interdependent.

[peterl94]

anyone here keen to give it a try?

I am. I'll try it tonight, if I have the time.

[beluga]

Btw. the links in this need updating: http://www.freecadweb.org/wiki/index.ph ... dules#Pivy
All the stuff is now in https://bitbucket.org/Coin3D

Regarding Pivy & Qt5: https://groups.google.com/forum/#!topic ... BG5jmDm2o8
The topic starter is asking about a pull request making Quarter Qt5 compatible and saying that if it is accepted, he "will handle the Pivy/Qt5 integration and make a pull request". Unfortunately that was in Jan 2015 and the PR has still not been merged.

It seems community developer hasn't really taken off and the whole project is languishing.

Perhaps it would be best to directly contact the person who wanted to work on Qt5 support for Pivy.

[peterl94]

A little too soon. I was able to build shiboken2 after a simple change to a couple cmake files, but I havn't gotten PySide2 to compile yet. I guess I'll be the one to report the first issue...

[labsin]

Qt4 is no longer supported and probably won't get shipt with new releases of popular linux distro's.
So now it's probably the time to start porting.

[triplus]

Yes this was discussed in the past and the most likely scenario is FreeCAD will be removed from the latest/next Linux distribution repositories for a release or two. The plan is to support PySide 2 directly or by using wrapper library but the reality is PySide 2 isn't ready and it likely won't be available in latest/next Linux distribution repositories for a while. Therefore porting to PyQt5 would be needed if we want to stay in latest/next Linux distribution repositories but due to licence policy that likely won't happen.

Therefore i guess unless PySide 2 gets serious development/packaging boost and lands in latest/next (development) Linux distribution repositories "soon" the reality is we can't do much about it and Qt5 port won't be finished in time.

[beluga]

This wiki page tracks the progress of PySide for Qt 5.x development and provides further information concerning the effort: https://wiki.qt.io/PySide2

[Kunda1]

Is there 'Migration to Qt5' checklist somewhere ?
Some bugs on the tracker that I found related to Qt5 I've tagged accordingly: http://freecadweb.org/tracker/search.php?tag_string=Qt5

[jnxd]

A question, albeit slightly unrelated:

Pyside2 code and wiki refer to a certain "COIN". Is it the same COIN as the one used by Freecad for drawing the viewport? If so, why is it relevant for Qt? The bitbucket page of coin seems to indicate it is in maintenance mode now.