From mikw at imagineersystems.com  Mon Jun  1 23:37:23 2015
From: mikw at imagineersystems.com (Mik Wells)
Date: Mon, 1 Jun 2015 22:37:23 +0100
Subject: [PySide] Significant news regarding Qt 5/PySide : VFX Reference
	Platform CY2016
Message-ID: <02a301d09cb3$25d8d230$718a7690$@imagineersystems.com>

News regarding Qt5 and Pyside:

 

"The Working Group behind the VFX Reference Platform, the target platform
for building software for VFX, has just announced the draft
of the Platform for next year: CY2016. This platform represents the set of
components that all major software releases are expected to be built against
from January 2016."

 

"The major change for CY2016 is a move to Qt5 which requires a port of
PySide and modifications to vanilla Qt to resolve issues that impact some
DCC tools. The Working Group's aim is for this modified Qt to be available
to anyone who wishes to target the CY2016 Platform, and for all major
software vendors to build their CY2016 releases against the same modified
Qt. More details will be shared in due course."

 

For further info see http://www.vfxplatform.com/

 

Regards,

 

Mik Wells

 

 





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150601/d5ce3cb4/attachment.html>

From jens.lindgren.vfx at gmail.com  Tue Jun  2 10:48:36 2015
From: jens.lindgren.vfx at gmail.com (Jens Lindgren)
Date: Tue, 2 Jun 2015 10:48:36 +0200
Subject: [PySide] Significant news regarding Qt 5/PySide : VFX Reference
 Platform CY2016
In-Reply-To: <02a301d09cb3$25d8d230$718a7690$@imagineersystems.com>
References: <02a301d09cb3$25d8d230$718a7690$@imagineersystems.com>
Message-ID: <CAJabFfPTRy=Rsm=6gHSAkiyvRzS1WCyuxS33V=30d2sY7ivqUw@mail.gmail.com>

This is great news!

On Mon, Jun 1, 2015 at 11:37 PM, Mik Wells <mikw at imagineersystems.com>
wrote:

> News regarding Qt5 and Pyside:
>
>
>
> “The Working Group behind the VFX Reference Platform, the target platform
> for building software for VFX, has just announced the draft
> of the Platform for next year: CY2016. This platform represents the set of
> components that all major software releases are expected to be built
> against from January 2016.”
>
>
>
> “The major change for CY2016 is a move to Qt5 *which requires a port of
> PySide and modifications to vanilla Qt* to resolve issues that impact
> some DCC tools. The Working Group's aim is for this modified Qt to be
> available to anyone who wishes to target the CY2016 Platform, and for all
> major software vendors to build their CY2016 releases against the same
> modified Qt. More details will be shared in due course.”
>
>
>
> For further info see http://www.vfxplatform.com/
>
>
>
> Regards,
>
>
>
> Mik Wells
>
>
>
>
>
>
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>


-- 
Jens Lindgren
------------------------------------
VFX Supervisor & Lead TD
Magoo 3D Studios <http://www.magoo3dstudios.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150602/94d5e910/attachment.html>

From sebastian at risefx.com  Tue Jun  2 11:24:33 2015
From: sebastian at risefx.com (Sebastian Elsner | RISE)
Date: Tue, 02 Jun 2015 11:24:33 +0200
Subject: [PySide] Significant news regarding Qt 5/PySide : VFX Reference
 Platform CY2016
In-Reply-To: <CAJabFfPTRy=Rsm=6gHSAkiyvRzS1WCyuxS33V=30d2sY7ivqUw@mail.gmail.com>
References: <02a301d09cb3$25d8d230$718a7690$@imagineersystems.com>
	<CAJabFfPTRy=Rsm=6gHSAkiyvRzS1WCyuxS33V=30d2sY7ivqUw@mail.gmail.com>
Message-ID: <556D7651.9000401@risefx.com>

Huh, we'll see how this goes. It took Autodesk roughly 10 year to switch 
from gcc 4.1 to gcc 4.4. Moving those massive Maya/Nuke apps to Qt5 is a 
huge task. I guess they will rather spend time on features that can be 
marketed...

On 06/02/2015 10:48 AM, Jens Lindgren wrote:
> This is great news!
>
> On Mon, Jun 1, 2015 at 11:37 PM, Mik Wells <mikw at imagineersystems.com 
> <mailto:mikw at imagineersystems.com>> wrote:
>
>     News regarding Qt5 and Pyside:
>
>     “The Working Group behind the VFX Reference Platform, the target
>     platform for building software for VFX, has just announced the draft
>     of the Platform for next year: CY2016. This platform represents
>     the set of components that all major software releases are
>     expected to be built against from January 2016.”
>
>     “The major change for CY2016 is a move to Qt5 *which requires a
>     port of PySide and modifications to vanilla Qt* to resolve issues
>     that impact some DCC tools. The Working Group's aim is for this
>     modified Qt to be available to anyone who wishes to target the
>     CY2016 Platform, and for all major software vendors to build their
>     CY2016 releases against the same modified Qt. More details will be
>     shared in due course.”
>
>     For further info see http://www.vfxplatform.com/
>
>     Regards,
>
>     Mik Wells
>
>
>
>
>     _______________________________________________
>     PySide mailing list
>     PySide at qt-project.org <mailto:PySide at qt-project.org>
>     http://lists.qt-project.org/mailman/listinfo/pyside
>
>
>
>
> -- 
> Jens Lindgren
> ------------------------------------
> VFX Supervisor & Lead TD
> Magoo 3D Studios <http://www.magoo3dstudios.com/>
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside

-- 

_*check out pointcloud9.com*_ <http://pointcloud9.com/>

**Sebastian Elsner - Pipeline Techincal Director - RISE*

t: +49 30 20180300 _sebastian at risefx.com _ <mailto:sebastian at risefx.com>
f: +49 30 61651074 _www.risefx.com_ <http://www.risefx.com/>*

*RISE FX GmbH*
*Schlesische Straße 28, 10997 Berlin
An der Schanz 1A, 50735 Köln
Büchsenstraße 20, 70174 Stuttgart
Gumpendorferstraße 55, 1060 Wien
Geschaeftsfuehrer: Sven Pannicke, Robert Pinnow
Handelsregister Berlin HRB 106667 B*

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150602/e43b2613/attachment.html>

From erik.johansson at fido.se  Tue Jun  2 11:39:47 2015
From: erik.johansson at fido.se (Erik Johansson)
Date: Tue, 2 Jun 2015 11:39:47 +0200
Subject: [PySide] Significant news regarding Qt 5/PySide : VFX Reference
 Platform CY2016
In-Reply-To: <556D7651.9000401@risefx.com>
References: <02a301d09cb3$25d8d230$718a7690$@imagineersystems.com>
	<CAJabFfPTRy=Rsm=6gHSAkiyvRzS1WCyuxS33V=30d2sY7ivqUw@mail.gmail.com>
	<556D7651.9000401@risefx.com>
Message-ID: <CAHE2vzv_aJEoS0_MirSyNOt3X-YkxLzGfOggyCuRPoFvetu3zQ@mail.gmail.com>

All involved companies take the VFX platform very seriously. I don't have
any doubts it will get implemented. Qt4 will also hit end of life and there
are a lot of advantages in Qt5.

On Tue, Jun 2, 2015 at 11:24 AM, Sebastian Elsner | RISE <
sebastian at risefx.com> wrote:

>  Huh, we'll see how this goes. It took Autodesk roughly 10 year to switch
> from gcc 4.1 to gcc 4.4. Moving those massive Maya/Nuke apps to Qt5 is a
> huge task. I guess they will rather spend time on features that can be
> marketed...
>
>
> On 06/02/2015 10:48 AM, Jens Lindgren wrote:
>
> This is great news!
>
> On Mon, Jun 1, 2015 at 11:37 PM, Mik Wells <mikw at imagineersystems.com>
> wrote:
>
>>  News regarding Qt5 and Pyside:
>>
>>
>>
>> “The Working Group behind the VFX Reference Platform, the target platform
>> for building software for VFX, has just announced the draft
>> of the Platform for next year: CY2016. This platform represents the set
>> of components that all major software releases are expected to be built
>> against from January 2016.”
>>
>>
>>
>> “The major change for CY2016 is a move to Qt5 *which requires a port of
>> PySide and modifications to vanilla Qt* to resolve issues that impact
>> some DCC tools. The Working Group's aim is for this modified Qt to be
>> available to anyone who wishes to target the CY2016 Platform, and for all
>> major software vendors to build their CY2016 releases against the same
>> modified Qt. More details will be shared in due course.”
>>
>>
>>
>> For further info see http://www.vfxplatform.com/
>>
>>
>>
>> Regards,
>>
>>
>>
>> Mik Wells
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>>
>
>
> --
>   Jens Lindgren
> ------------------------------------
> VFX Supervisor & Lead TD
> Magoo 3D Studios <http://www.magoo3dstudios.com/>
>
>
> _______________________________________________
> PySide mailing listPySide at qt-project.orghttp://lists.qt-project.org/mailman/listinfo/pyside
>
>
> --
>
>  *check out pointcloud9.com* <http://pointcloud9.com/>
>
>
>
>
> * Sebastian Elsner - Pipeline Techincal Director - RISE t: +49 30 20180300
> <%2B49%2030%2020180300> sebastian at risefx.com <sebastian at risefx.com> f: +49
> 30 61651074 <%2B49%2030%2061651074> www.risefx.com <http://www.risefx.com/>*
>
> *RISE FX GmbH*
>
>
>
>
>
> * Schlesische Straße 28, 10997 Berlin An der Schanz 1A, 50735 Köln
> Büchsenstraße 20, 70174 Stuttgart Gumpendorferstraße 55, 1060 Wien
> Geschaeftsfuehrer: Sven Pannicke, Robert Pinnow Handelsregister Berlin HRB
> 106667 B*
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>


-- 


*Erik Johansson*
*Pipeline TD*
*Fido*Rosenlundsgatan 36
118 53 Stockholm, Sweden
www.fido.se
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150602/d67dd01c/attachment.html>

From ryan.r.grove at aero.org  Fri Jun  5 16:39:32 2015
From: ryan.r.grove at aero.org (Ryan R Grove)
Date: Fri, 5 Jun 2015 10:39:32 -0400
Subject: [PySide] QFileDialog Linux Problem
Message-ID: <OFEB8CD48A.E68400A7-ON85257E5B.00500C84-85257E5B.00508627@notes.aero.org>

Hello,

For a file located /home/rrg29876ArchID-14761_case0.out, all is well when 
I run the following code in Windows:

#Open a FileDialog to pull in supported data
        formats = ("R Output Files (*.out);;"
                    "Rc Output Files (*.out);;"
                    "A Average Files (*.avg);;"
                    "A Timestep Files (*.tim)")
        fileName, filtr = QFileDialog.getOpenFileName(self,
            "Select A Data File to Open", self.defdir, formats)
        self.defdir = path.split(fileName)[0]
        print "self.defdir: ",self.defdir
        print "fileName: ", fileName
        print "filtr: ", filtr

But in Linux I get:

self.defdir: /home/rrg29876/vice
fileName:  home/rrg29876/vice/De
filtr:  Rc Output

Can anyone help explain this truncation to me and/or suggest ways to 
fix/get around this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150605/44f78e5b/attachment.html>

From goswin-v-b at web.de  Thu Jun 11 12:22:40 2015
From: goswin-v-b at web.de (Goswin von Brederlow)
Date: Thu, 11 Jun 2015 12:22:40 +0200
Subject: [PySide] Is dual inheritance clearer?
In-Reply-To: <2076730.GdH5OTt5k3@supremo>
References: <2076730.GdH5OTt5k3@supremo>
Message-ID: <20150611102240.GB29184@frosties>

On Thu, Apr 04, 2013 at 04:02:06PM +1100, Algis Kabaila wrote:
> Hi,
> 
> I believe that PySide (and PyQt for that matter) are widely used for GUI 
> design.  There are two main "orderly" ways to start a GUI program, after 
> designing it in the Qt Creator: 
> 
> (1)
> With dual inheritance:
> class MainWindow(QMainWindow, Ui_MainWindow):
>     def __init__(self, parent=None):
>         super(MainWindow, self).__init__(parent)
>         self.setupUi(self)
> 
> (2)
> Without dual inheritance:
> class MainWindow(QMainWindow):
>     def __init__(self, parent=None):
>         super(MainWindow, self).__init__(parent)
>         self.ui = Ui_MainWindow
>         self.ui.setupUi(Ui_MainWindow(),self)
> 
> There have been some horror stories about the evils of multiple 
> inheritance.  What is the preferred method, (1) or (2)?  
> 
> Thank you in anticipation of your response.
> 
> Al.

The PyQt/PySide classes are realy not setup for multiple inheritance
and if you have those dual inheritance somewhere in the middle of your
inheritance, i.e. if you inherit MainWindow again (which makes more
sense for other widgets) then things break, constructors don't get
called and you end up with unusable objects.


I prefer (python3, seriously still using python2? :):

class Widget(QtGui.QWidget):
    def __init__(self, parent=None):
        super().__init__(parent)
        self.ui = loadUi("Widget.ui", self)


--- loadUi ---

I'm using the binding_helper.py (Copyright (c) 2011, Dirk Thomas,
Dorian Scholz, TU Darmstadt) which allows code to work with PyQt or
PySide automatically or selectively and provides loadUi for PySide.

Why should I add the extra step of generating python code form UI
files when I can just load the UI file directly? An extra benefit is
that one can edit UI files for subwindows or dialogs at runtime and
the changes appear the next time the subwindow or dialog is opened.

MfG
	Goswin


From goswin-v-b at web.de  Thu Jun 11 12:59:06 2015
From: goswin-v-b at web.de (Goswin von Brederlow)
Date: Thu, 11 Jun 2015 12:59:06 +0200
Subject: [PySide] QModelIndex does not keep the internalPointer alive
Message-ID: <20150611105906.GC29184@frosties>

Hi,

I have an QAbstractItemModel that realy is abstract. The model does
not have persistant objects for every row since data for the model is
stored sparse in 3 tables in mysql:

Users Table: id, name, real name, email, info
Roles Table: id, name, description
Users2Roles: id, user_id, role_id

Users can be assigned to roles by adding a pair of user id and role id
in the Users2Roles table. A user belongs to all the roles for which
such a pair exist and doesn't belong to any other roles.

>From that I'm building a tree that has all the users as top level
items and each user has all the roles as children. The
QtCore.Qt.CheckStateRole then shows if the user belongs to the rules
or not. Setting the QtCore.Qt.ItemIsUserCheckable flag also allows
(only for admins) assigning roles to users with a simple click.

Now to the problem:
-------------------

As said the model is abstract and doesn't have one object per row.
That would require user * roles many objects and most users don't have
(many) roles and only one user is ever shown in the view at any one
time (using QDataWidgetMapper to map the selected user). Due to that I
wanted to store the relevant user_id and role_id in the QModelIndexes
internalPointer and then lookup the required informations in the 3
database tables as needed.

So for the top level items (users) the index is created as:

     self.createIndex(row, column, [user_id])

and for the children (roles):

     self.createIndex(row, column, [user_id, role_id])

And there starts the problem. The generated QModelIndexes are
emidiatly corrupted. Right after the createIndex call the internal
pointer points to a list containing [..., b'\n'] (actual print()
output, not my abreviation). Later accessing the list elements in the
models data() method causes a segfault.

My guess is that the QModelIndex does not register the python object
with the GC when it stores it in the underlying c++ class and the
object gets trashed by the GC.

So my question is:

How can I store non persistant python objects in a QModelIndex?

MfG
	Goswin


From v.kajen at yahoo.com  Thu Jun 18 08:54:11 2015
From: v.kajen at yahoo.com (Velummaylum Kajenthiran)
Date: Thu, 18 Jun 2015 06:54:11 +0000 (UTC)
Subject: [PySide] Using PySide for closed source proprietary softwares
Message-ID: <724834087.1157810.1434610451612.JavaMail.yahoo@mail.yahoo.com>

Dear Sir/Madam,I'm using PySide to develop proprietary software application. I haven't done any modification in PySide library. I want to sell my application as closed source to my clients. For this, I plan to use PyInstaller  as a freezing tool.Here I can use --onefile option to ship as one executable. 
Is it violating the licensing terms of PySide? What procedures that I have to follow in order to adhere the legal terms of PySide? 
I have following concerns as well. According to LGPL terms, what's the meaning of dynamic linking in python? as my understanding, it's just an interpreter and everything is linked dynamically. If I use PyInstaller to freeze my application, Is it dynamic linking or static linking? Please clear me the one file option as well. Because if I don't use onefile option, users still can replace the shared Qt libraries by themselves in order to run my application with different versions of Qt/PySide. If I freeze my application as one file exe, users can not replace the so/dll files in order to run my application with different versions of PySide libraries.
I have asked this question in stackoverflow and python mailing list as well. Everyone advised me to contact pyside mailing list for real explanation. Can I get a clear idea about using PySide for my python GUI application? According to license, I should dynamically link to the library to obey the legal terms (Same as Qt). In this case, how do I link dynamically? 

Thank You.Best Regards,Kajenthiran V
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20150618/7854e5f2/attachment.html>

From germanocarella.list at gmail.com  Tue Jun 30 14:10:03 2015
From: germanocarella.list at gmail.com (germano carella)
Date: Tue, 30 Jun 2015 14:10:03 +0200
Subject: [PySide] PySide accessibility, is possible?
Message-ID: <5592871B.8090609@gmail.com>

Hi,
I downloaded and installed PySide on my windows 8.1.
I tried to run some examples, such as application example, and other.
I seen there are accessibility plugins for QT 4.8, but examples are 
inaccessible to screen readers.
There is a way to enable accessibility in pySide?
Some tutorial or document?
Thannks!
Germano