Re: some questions about gtk-doc

[Stefan Kost <ensonic hora-obscura de>]

Hi Thomas,
> Hi everyone,
>
> I've been delving a bit deeper into gtk-doc recently because I wanted to
> add documentation for plugins and elements in GStreamer.
>
> While doing so I've come across a few things I wanted to ask:
...
> c) I have a hard time hacking on gtk-doc because I tend to have to copy
> the tools from /usr to my local dir, tweak my build setup, and remove a
> bunch of commented prints to see what's going on.  Would it make sense
> to do this more nicely by checking an env var and outputting this debug
> info if the env var is set ?
>
I don't know how much it hurts the preformance of gtk-doc, if we leave all the 
trace prints in there in for realeses. Apart this sounds good. I do it the same way.
The doc utile are generatet at configure time (inserts the path to the perl 
binary). I don't know if we can use this step to toggle between a nop-debug-log 
and a working one.
>
...
> Thanks,
> Thomas
>
> P.S.: anyone ever considered redoing gtk-doc in, say, python ?

What would we gain? IMHO the 'ugliness' of gtk-doc is not tha facts is written 
in perl. Its more that the developer needs to maintain several files which have 
redundant information. But hey, that what we are addressing step-by-step ;)

Stefan