Re: [Graphviz] building doc with Python3

On 2015-02-26 20:08 Robin Dunn <[email protected]> wrote:
> So you need to run the commands dox, etg, and sphinx, in that order.

It is the first time I heard of etg command in the case of producing
docu.

> If you also want
> to run wx.lib, wx.py and wx.tools through Sphinx

What would be the result of that compared to only "dox etc sphinx"?
Which parts of the docu whould be missing.

About the Point docu:
There is
ext/wxWidgets/interface/wx/gdicmn.h
declaring a 'class wxPoint' with C++ code.

I really understand the wrapping thing and why the docu is wxPhoenix
documentation is extracted form a lot of different places in different
formats from different tools.

But this doesn't help me. In the wxPhoenix docu is a 'Point.Get()'
function described. And of course it is not declared in the gdicmn.h
class because it return a python-tuple.

So what is the way here? Where does this html-file with Point.Get()
inside come from? I just need a file to edit to improve the
documentation of Point.
The etg- and src-directory doesn't contain 'Point'.

Of course I read README.rst but the build.py commands themselfs are not
documented. I currently don't know where Point.Get() comes from because
it is not in the C++ header file and I found no "tweaker" file about it.

-- 
You received this message because you are subscribed to the Google Groups "wxPython-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.