jmiguel2902 / blur-dev

Automatically exported from code.google.com/p/blur-dev
0 stars 0 forks source link

Possibly switch to PySide in the future ? #22

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
With Nokia putting up their own python bindings that are also available as LGPL 
vs. GPL or commercial only i was wondering if there were any plans to migrate 
to PySide at some point?

In addition to licensing only differences it is currently pretty close to API 
compatibility (=easy migration) but aims to change things and move forward.

Just wondering if there are any thoughts on that issue

Original issue reported on code.google.com by instinctvfx@gmail.com on 9 May 2011 at 8:51

GoogleCodeExporter commented 9 years ago
We had discussed PySide at one point - and I think the idea was to let it 
mature a bit and then switch.

I'm not sure what the current plan is - there is no active goal to transition 
to it currently at any rate.

Original comment by eric.hul...@gmail.com on 9 May 2011 at 11:58

GoogleCodeExporter commented 9 years ago
Thanks for the input. For the record, nuke also ships with PySide bindings 
since recent builds, so it seems that PySide is pretty much there for 
production use.

Original comment by instinctvfx@gmail.com on 23 Nov 2011 at 8:48

GoogleCodeExporter commented 9 years ago
At this time we have no plan's to switch to PySide. Though Py3dsMax itself 
should support it as long as you can get the equivalent 
PyQt4.QtWinMigrate.QMfcApp.

Original comment by hen...@gmail.com on 4 Dec 2013 at 7:53