Hugo Parente Lima wrote: > My opinion about those enhancement suggestions: > > > [1] http://bugs.openbossa.org/show_bug.cgi?id=606 > > Better than a toTuple method is to add the possibility to create tuples from > those objects, e.g.: > > p = QPoint(1, 2) > t = tuple(p) # (1,2) > > It's better because it doesn't add any "visible" method to the API, besides > being beauty IMO =]
Yes -- do note that conversion through tuple() can only be implemented by making QPoint iterable. > > [2] http://bugs.openbossa.org/show_bug.cgi?id=607 > > It's something that you can use on your projects but not necessarily need to > be on PySide itself, IMO your attempt to simplify the code failed, not by > your > bad, but because the original code is already too simple. Wouldn't it be plain beauty to be able to write a one-line hello world? with QtGui.QApplication: QtGui.QLabel("Hello world!").show() :-) It's not going to halve the number of lines of code of your projects, but it makes PySide easier and plain more fun to use. It's a bit like the lack of qmake project files in Python compared to C++: in the grand scheme of things, it's not much (you could write a 2-line project file), but it makes Python that much more enjoyable to work with as you can write a tiny app from scratch in no time. > > [3] http://bugs.openbossa.org/show_bug.cgi?id=615 > > I agree with Matti, there's no need to add yet another incompatibility with > PyQt for basically no gain at all. But the API clearly makes no sense. Why should any API defined by PyQt have to be cast in stone and never be improved, especially here where there are no backward-compatibility issues? Cheers, Farsmo _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
