PySide migration

[douardda]

Hi,

shouldn't the "CompileOnUnix" wiki be updated? (and probably the others compilation pages, but I don't care about them )

David

[NormandC]

I updated the Debian/Ubuntu dependencies in CompileOnUnix. I don't know the package names in other distros, someone else will have to do it.

[wmayer]

From the todo list, these points are done:
- PartDesign scripts
- TemplatePyMod must be switched
- Spreadsheet module must be switched, but this might be a good opportunity to merge the C++ one...


The remaining points are:
- Ship must be switched (see with sanguinario joe)
- src/WindowsInstaller/LibPack.wxs contains references to PyQt4, don't know what to do there

[jriegel]

- src/WindowsInstaller/LibPack.wxs contains references to PyQt4, don't know what to do there

Dont bother with this one, I have a working NSIS installer (still ugly and lack some (new) features bug working). So WIX will die...

[chrisf]

When I saw this thread, I assumed it was about migration away from Pyside.

I'm a big fan of Pyside having used it for a number of projects but, as far as I can see, the outlook for the future isn't that good. There seems to be limited chances of Pyside for Qt5 or Python 3. I used to develop Qt apps for mobile and there, the open source python developers are moving to the lighter connection of pyotherside http://thpmaemo.blogspot.co.uk/2013/07/ ... -qt-5.html.

I understand the need to move away from PyQt4 but wonder what FreeCAD's dependence is on Pyside moving forward?

[wmayer]

Important is that PySide also works for Python3 and I think Qt4 will still be there for a long time. So, for the near future we don't have to worry about this.

[jriegel]

I agree with Werner, no rush to go either to Qt5 or Python 3.

We are after all a long standing desktop application, and I don't want to run in circles like the mobile world do....

[chrisf]

That's good to hear and I didn't mean to sound like a critic (love your work here BTW) just concerned that you might be moving to depend on something that you can't depend on.

Important is that PySide also works for Python3 and I think Qt4 will still be there for a long time. So, for the near future we don't have to worry about this.

I don't know a great deal about desktop development though I did spend a year working on Rosegarden including the end of the Qt3 to Qt4 migration. My concern was that with Qt4 to Qt5 migration being pretty trivial for a C++ or QML/javascript developer might lead to a fairly fast move on the desktop from Qt4 to Qt5. If you're confident that Qt4 will be around for a long time then that's good enough for me.

... I don't want to run in circles like the mobile world do....

So I guess you're not planning a QML migration any time soon?

[jriegel]

maybe we will use QML for special cases, but we will for sure not move the Gui code to QML. That would be a huge amount of work and for what?

[chrisf]

I wasn't seriously suggesting a QML migration.