Re: [Graphviz] building doc with Python3

On 2015-02-27 21:23 Robin Dunn <[email protected]> wrote:
> [email protected] wrote:
> > It is the first time I heard of etg command in the case of producing
> > docu.
> 
> Really?  That's not even the first time I mentioned it in this
> thread.

This isn't what I meant. Sorry for my bad english.
I asked about building the doc and somebody gave me the commands for
that. etg wasn't under them. Anyway...

> The docs for the modules in the wx.lib, wx.py and wx.tools packages. 
> Isn't that kinda obvious?

No it isn't.
wxPhoenix is (just) a wrapper for wxWidgets. So of course when I build
the docs the wxWidgets stuff should be involved. Without wxWidgets
there would be no doc. So I even don't understand why there are extra
wx-commands.
So when I build the doc without the wx-commands, what is then there?

You see my point of view?

> Especially since the build.py help says:

I know what it says. And your READEM.rst, too and I really stepped into
the build.py code, too.
But please keep in mind that you are the dev who created the
build-process. You know it. But for a foreigner it is really hard to
step into it.
And a plain text big README-file doesn't help with it. Because the
informations in it are kind of unstructured (no hypertext, no table of
content, unconcrete subjects, ...). The build process is nowhere
concrete and detailed described. Except in your mail now...
This informations you gave me here can not be found in the docu.
And code (even nice readable Python code) isn't docu.

>      c.addCppMethod('PyObject*', 'Get', '()', """\
>          return sipBuildResult(0, "(ii)", self->x, self->y);
>          """,
>          pyArgsString="() -> (x,y)",
>          briefDoc="Return the x and y properties as a tuple.")

Nice. But I even can not see where the description of the return type
come from.
But this doesn't matter anymore. Because someone fixed it. In the
current docu is the return value and type of Point.Get() and Size.Get()
well described. Thats what I wanted.
But I couldn't find the commit for that to see what causes the changes.
etg/gdicmn.h itself is around one year old.

Please keep in mind how important wxPython is. It is unhealthy for each
open source project if only one person can understand and handle the
build process.
Please don't keep this personal! This isn't my goal.
My goal is a successfull and long living wxPython project.

-- 
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.