KDE Frameworks Documentation

[Myriam Schweingruber]

Hi Ignat,

On Tue, Sep 27, 2011 at 20:30, Ignat Semenov <ragnarokk91 at gmail.com> wrote:
> Hello KDE devs and users!
>
> You may remember me as that guy on IRC that's constantly building
> something, always finds bugs in the buildsystem and never gives back
> code. Well, for a reason, it turns out. :)

...

> 1)It was all split into many processes, and thus impossible to debug
> without black magic.
> 2)The API was similar to an onion, I think I did not remove all the
> layers, even after spending some time.
> 3)Qt meta-information, esp. signals and slots, gets in the way.
> 4)(Similar to #1) KIO or whatever it was turned out to be
> asynchronous, multi-process beast, and next to impossible to debug.
> YOu have to attach to multiple processes and watch them all, but to do
> that, you need to know where to attach and what to watch for.
>
> Thus, here's my proposal (one mroe blog post comment quote):
>
> "KDE Core Libs and Frameworks *do* need good up-to-date documentation

I am not a developer, but did you have a look here: http://api.kde.org/ ?

...

> This means:
>
> 1)API docs up-to-date and with extensive examples.

Since the API documentation is extracted automatically, I would expect
it to be rather up-to-date


Regards, Myriam

-- 
Protect your freedom and join the Fellowship of FSFE:
http://www.fsfe.org
Please don't send me proprietary file formats,
use ISO standard ODF instead (ISO/IEC 26300)