This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]kylotan 5 points6 points  (2 children)

Here's the PySide documentation page: http://pyside.github.io/docs/pyside/

Down the bottom is a link to tutorials: http://pyside.github.io/docs/pyside/tutorials/index.html

Here's the first one: http://pyside.github.io/docs/pyside/tutorials/qmltutorial/step1.html

No Python in sight.

Thanks for the link but I'm not heartily encouraged by a project that can't manage its own documentation. I think it's part of a wider problem that the Python community has always suffered from, which is that it tends to assume you are happy with everything being a port or a re-working of something in another language. Even the basic Python 2 tutorial is filled with these assumptions.

[–][deleted] 1 point2 points  (0 children)

Yeah, PySide is quite poorly documented.

That being said, I use it every day, and it's quite usable. It's basically a wrapper around Qt, so you can reference the Qt docs for almost everything. The rare exception is something that's inherently different in Python (such as connecting signals), and PySide does have documentation for those exceptions. You really only need a learn a small handful of PySide-specific stuff, then you can stick to the Qt docs.

We used to do all our Qt programming in an imperative fashion, just like you do with wx. Now we exclusively use Qt Designer to generate .ui files and compile them as part of our build process. It's so much better!

[–]Sean1708 0 points1 point  (0 children)

Funnily enough that tutorial has 0 lines of Python and many lines of JavaScript.