[PySide] Let's get serious for Pyside to support Qt5

[pankaj pandey]

Its good to see revival of Qt5 support interest.

On Thu, Dec 11, 2014 at 9:27 PM, Tony Barbieri <greatrgb at gmail.com> wrote:
> I work in Visual Effects and there are many different applications using Qt
> these days with PySide bundled.  This year the VES (Visual Effects Society)
> has started a push for companies to start following their platform
> guidelines for which versions of libraries should be supported within a
> given year.  For example in 2015, Qt 4.8.x and PySide 1.2.x are still the
> versions they are targeting.  If in 2016 Qt 5.x.x is selected then I would
> imagine the various software companies will want to have a PySide version
> that supports it.
>
> More information about the VES platform can be found here:
> http://www.vfxplatform.com/
>
> A few companies using Qt in Visual Effects software are Autodesk, The
> Foundry and Side Fx.  It would be great if they could lend some development
> support to help continue to push PySide forward.

Yes, it would be really helpful if some entities interested in PySide can get
together and decide to do something. Its not something which a few
volunteers or a single company can do.

I know John Ehresman started some experiments on way of simplifying
shiboken bindings generation in April
( https://bitbucket.org/jpe/experimental-pyshiboken ), and probably hasn't
got time for that since.
I also experimented with smoke based dynamic bindings last year
( https://github.com/pankajp/pysmoke ), but again free time is scarce.

I think all of us who can contribute via code should put up a plan
and get something started.
It is easier to contribute to existing work than start afresh,
we we might even gather new contributors.
With some initial progress visible, it might also be easier to pitch in
a plan for pyside using companies to sponsor the work.


> On Thu, Dec 11, 2014 at 10:49 AM, Todd Rme <toddrme2178 at gmail.com> wrote:
>>
>> Taking a bit of a step back, what is currently holding Qt 5.x back
>> from allowing completely dynamic bindings?  Has anyone talked to the
>> Qt devs to see if these pieces could be implemented?
>>
>> If it would be possible to avoid the binding generation step and just
>> go straight to dynamic bindings, that would reduce the work needed to
>> maintain PySide significantly, and would help all of the other
>> bindings communities in the process.
>>
>> This might be something to look into before investing too much time or
>> effort in creating new static bindings.
>> On Thu, Dec 11, 2014 at 4:40 PM, Steve Payne <gliblib247 at gmail.com> wrote:
>> > I think we need to have two different conversations that are related.
>> >
>> > 1. What needs to be changed in PySide and shiboken to support Qt5?
>> > 2. What are the options for long term support?
>> >
>> > I agree that the prospect of having corporate backing for the project
>> > would
>> > be nice but unstable and probably unlikely so if we want it we need to
>> > do
>> > it. I use PySide constantly in a professional environment and although I
>> > cannot get my company to allow me to officially work to develop PySide,
>> > it
>> > is in my professional interest to keep it alive. There have been a
>> > number of
>> > pings to the list since Qt5 came out about migrating PySide that usually
>> > disappear and the impending obsolescence of Qt4 really pushes this to be
>> > serious.
>> >
>> > - Steve
>> >
>> > On Dec 10, 2014, at 12:04 PM, William Ferreira
>> > <williamgeraldo at gmail.com>
>> > wrote:
>> >
>> > John Ehresman, I was analyzing the commits the time and saw that you did
>> > much.
>> >
>> > I did a little post here just wondering what we can do to help this
>> > process.
>> >
>> > If you can guide us believe that many would like to help.
>> >
>> > 2014-12-10 14:56 GMT-02:00 John Ehresman <jpe at wingware.com>:
>> >>
>> >> On 12/10/14, 11:38 AM, Florian Bruhin wrote:
>> >> > * Stany MARCEL <stanypub at gmail.com> [2014-12-10 17:31:44 +0100]:
>> >> >> Hello
>> >> >>
>> >> >> Maybe a crowd funding to hire a full time developer should be a good
>> >> >> idea.
>> >> >> VLC association have done a kickstarter to fund the dev of VLC
>> >> >> windows
>> >> >> 8
>> >> >> support.
>> >> >
>> >> > I'd be in!
>> >> >
>> >> >> Is pyside currently only community driven or is there any
>> >> >> association
>> >> >> or
>> >> >> company behind, that could organize that.
>> >> >
>> >> > According to the Wikipedia page it was released by Nokia, so probably
>> >> > Digia / The Qt Company would be the one to contact nowadays.
>> >>
>> >> PySide is in the Qt repository but its development is substantially
>> >> community driven at this point.  I am the somewhat reluctant maintainer
>> >> that hasn't been able to find much time to work on PySide recently.
>> >>
>> >> I don't think the VLC kickstarter is a good model for funding PySide
>> >> development because VLC is a consumer application with many times the
>> >> number of users as direct users of PySide (the developers using PySide,
>> >> not the users of applications built with it).
>> >>
>> >> John
>> >>
>> >> _______________________________________________
>> >> PySide mailing list
>> >> PySide at qt-project.org
>> >> http://lists.qt-project.org/mailman/listinfo/pyside
>> >
>> >
>> >
>> >
>> > --
>> > William Ferreira
>> >
>> >
>> > _______________________________________________
>> > PySide mailing list
>> > PySide at qt-project.org
>> > http://lists.qt-project.org/mailman/listinfo/pyside
>> >
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
>
>
> --
> Tony
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>