[PySide] Contributing to documentation?

Sean Fisk sean at seanfisk.com
Thu Oct 2 00:00:29 CEST 2014

Hi Eric,

A while ago, I wrote a script to generate the PySide documentation
<https://github.com/seanfisk/pyside-docs>. It’s intensely complex because
it requires a qdoc3 executable from Qt 4.6.4 for XML output support (if my
memory serves). That repository might be a place to start.

For what it’s worth, I usually just use the C++ documentation and prior
knowledge of porting patterns to write my PySide code. I realize that’s not
really an answer, but it’s worked for me thus far.

Good luck,

Sean Fisk

On Mon, Sep 1, 2014 at 5:08 PM, Eric Thomson <thomson.eric at gmail.com> wrote:

> As I learn PySide, the online documentation is my lifeline, but there
> are quite a few gaps. For instance, at
> http://pyside.github.io/docs/pyside/PySide/QtCore/QMimeData.html, we
> have the following:
> "There are three approaches for storing custom data in a
> PySide.QtCore.QMimeData object:  "
> And then...nothing. It does not list the three approaches, which are
> described at the Qt documentation in some detail
> (http://doc.qt.digia.com/4.6/qmimedata.html). There it is obviously
> for C++ users, obviously.
> I would really like to help translate some of this stuff into Python,
> where I can, but am not sure how to go about helping, or if such work
> would even last. For instance, would such contributions be lost when
> documentation is automatically updated?
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20141001/9ef23271/attachment.html>

More information about the PySide mailing list