On Thu, Jun 15, 2017 at 5:21 AM, <[email protected]> wrote:

> I'll think on this some more. Whereas it's relatively easy to predict the
>> ways people will use the existing pyqtgraph components (and write
>> documentation/examples based on those), it's harder to predict all the ways
>> people might want to customize outside of those existing components.
>>
>
> This is the way I'm going now. I think that I have the basic layout now
> covered, and I'm trying to do this "custom building" from bottom up. The
> biggest nuisance in this is the lack of code/API documentation that
> includes all inherited functionality. I'm pretty sure there must be
> something like this for Python (I'm more a native C/C++).
>

Yes! I tried to make this work long ago. I'll bet something exists in
sphinx by now that could help.. at a minimum, it would be nice to
automatically link back to base classes and out to the Qt documentation.
I actually really like the way the built-in help() function formats
documentation--it shows all methods sorted by their position in the
inheritance hierarchy.


>
> BTW, I've started to write some "internal" documentation about the/my way
> into pyqtgraph. Still very rough and incomplete, but you might want to have
> a look. I'm not the only one in our group that is using pyqtgraph, and it
> seems that I'm set up to become the "go-to - expert".
>
> I'm not sure though, if it might be helpful to someone outside me or my
> group.
>

I'd love to see it (in any state), and I'm sure others would as well. If we
can clean it up then it might make a nice addition to the documentation or
an independent article of its own.


Luke

-- 
You received this message because you are subscribed to the Google Groups 
"pyqtgraph" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pyqtgraph/CACZXET8C%3DA_9oQ8wgg1vRukKV2dxgoLNL%3DM60DTvrJSb5gEf8Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to