On 28.04.2010 15:16, ext Hugo Parente Lima wrote:
- QTextStream::bin, hex, etc wasn't removed?
No, that topic is unrelated to this PSEP.
- I don't really see the need for pyQtConfigure method;
You might have a point there... I've been spending the last 20 minutes
trying to figure it out and finding uses for it but so far everything it
does would appear to be possible to be performed with more standard
ways, specifically QObject.setProperty (and .property).
Maybe someone with more hands-on experience on pyqtConfigure would like
to comment?
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".
I like that too, a lot, but that's definitely a topic of another PSEP.
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.
In my opinion following the Qt names would be a sensible default.
Cheers,
ma.
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
