Fwd: gtk+ documentation wikified



A way to overcome that, would be to put a warning on the wiki page
whenever the documentation for a function is updated, so that the
users could see the updated comment in the code and update the
documentation accordingly.


P.S. Sorry for sending the message twice

2009/2/19 Dominic Lachowicz <domlachowicz gmail com>:
> Yes. The most common example I can think of is when a function is deprecated.
>
> On Thu, Feb 19, 2009 at 10:52 AM, Eugene Gorodinsky
> <e gorodinsky gmail com> wrote:
>> Have there been cases where documentation for some function was
>> changed after that function appeared in the stable version?
>>
>> 2009/2/19 Dominic Lachowicz <domlachowicz gmail com>:
>>> That's hard-ish to do today. GTK+'s documentation is generated in
>>> large part by scanning comments in C code, which a program then turns
>>> into HTML. Any proposal would require a way to keep the Wiki and the C
>>> comments in-sync.
>>>
>>> On Thu, Feb 19, 2009 at 10:28 AM, Eugene Gorodinsky
>>> <e gorodinsky gmail com> wrote:
>>>> Hi all
>>>>
>>>> Since you guys are discussing the redesign of the gtk+ website, I'd
>>>> like to propose an idea that I have. I've seen quite a lot of comments
>>>> saying gtk+ documentation isn't as good as qt's. What do you think of
>>>> having a wiki that documents all of gtk+ api?
>>>> _______________________________________________
>>>> gtk-devel-list mailing list
>>>> gtk-devel-list gnome org
>>>> http://mail.gnome.org/mailman/listinfo/gtk-devel-list
>>>>
>>>
>>>
>>>
>>> --
>>> Counting bodies like sheep to the rhythm of the war drums.
>>>
>>
>
>
>
> --
> Counting bodies like sheep to the rhythm of the war drums.
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]