Hi all, I didn't see any problems with new PyQt signal/slot implementation, but like I talked before I love the way the signal and slot works in C# implementation. And I think we can implement both only adding the operator "+=" and "-=" in slot and signal objects.
Another point is, we need take care of follow PyQt api, to no create a eternal link between PySide and PyQt. This can leave the users always wait for compatibilities, and this will make all this great ideas of PEP's unnecessary. Then we need keep clear, PySide not will be compatible with PyQt in the future. my 2 cents. On Wed, Oct 28, 2009 at 7:29 AM, Matti Airas <[email protected]> wrote: > ext Ville M. Vainio wrote: >> >> On Tue, Oct 27, 2009 at 6:45 PM, Mark Summerfield <[email protected]> >> wrote: >> >>> That will make it easy for users to migrate between the two >>> implementations and will reduce the learning curve. It will also make it >>> easier to document PySide (and easier for authors;-) >> >> Also, it makes this much-wanted feature of PyQt non-toxic, in that you >> can safely transition to it in your own projects without burning your >> bridges. That's good for the Qt-on-python world as a whole. >> > > > Thanks, Ville, Mark, Hugo. I'll whip up a quick PSEP to have the decision > confirmed and then put the implementation item in the core dev team's > backlog. > > Cheers, > > ma. > _______________________________________________ > PySide mailing list > [email protected] > http://lists.openbossa.org/listinfo/pyside > -- Renato Araujo Oliveira Filho Instituto Nokia de Tecnologia - INdT Mobile: +55 (81) 8704-2144 _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
