On Monday 26 April 2010 09:37:01 Matti Airas wrote:
> On 23.04.2010 16:18, Airas Matti.P (Nokia-D/Tampere) wrote:
> > On 23.04.2010 15:37, ext Mark Summerfield wrote:
> >> Thanks, now I can do vim -d and see exactly what you changed (and I'm
> >> happy with what you've done). (However, I'd suggest moving from "If the
> >> need arises..." to "mapped to None)." to the end of the "No QString and
> >> almost no QVariant" section.
> > 
> > OK, did that. It's more logical now.
> > 
> > http://www.pyside.org/docs/pseps/psep-0101.html
> > http://www.pyside.org/docs/pseps/psep-0101.txt
> 
> Assuming there're no more pending changes/improvements to this, I'll
> mark this Accepted once I get an OK from the core dev team members.

Just some questions about the final version of this PSEP.

- QTextStream::bin, hex, etc wasn't removed?
- I don't really see the need for pyQtConfigure method;

IMO, integrate Qt properties with python is much more important.
For example, instead of write:

obj = QObject()
obj.setObjectName("foo")
print obj.objectName()

we just need to write:

obj = QObject()
obj.objectName = "foo"
print obj.objectName

This is not hard to implement and IMO represents a great gain to this abstract 
and subjective thing called by us "pythonic API".

Another point, this time regarding keyword arguments, I guess that we should 
follow Qt names, not the PyQt names, ok, I must admit that I'm saying this 
just because follow the Qt ones is easier to implement, hehehe, because the 
C++ parser knows  the Qt argument names, but not the PyQt ones. Anyway I guess 
that PyQt is using the Qt argument names.

> Cheers,
> 
> ma.
> _______________________________________________
> PySide mailing list
> [email protected]
> http://lists.openbossa.org/listinfo/pyside

-- 
Hugo Parente Lima
INdT - Instituto Nokia de Tecnologia

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside

Reply via email to