Hello Romain,
Thank you for the constructive answers. :)
>In a case like that, ask the maintainer(s). Usually, developers know the
>code of their program :) .
>Also, feel free to ask for help on IRC or through the bugzilla.
Sure, this can be done. But if every (possible) contributor asks the
mai
Le 27/09/2011 20:30, Ignat Semenov a écrit :
"[...] I once tried to trace down a Dolphin bug regarding previews. I
found like 5 tiers of abstraction, lots of processes, insanely complex
APIs and swore not to try to fix KDE bugs any more, at least in
Dolphin or the KIO subsystem."
In a case like t
Hi Myriam,
on Wednesday 28 September 2011 10:26:19 Myriam Schweingruber wrote:
> Hi Ignat,
>
> On Tue, Sep 27, 2011 at 20:30, Ignat Semenov wrote:
[...]
> > This means:
> >
> > 1)API docs up-to-date and with extensive examples.
>
> Since the API documentation is extracted automatically, I wo
On Wed, Sep 28, 2011 at 10:26 AM, Myriam Schweingruber wrote:
> Since the API documentation is extracted automatically, I would expect
> it to be rather up-to-date
Yes, but it's not always very extensive. Or to put it differently: API
documentation can only be extracted, but not be generated
auto
Hi Ignat,
On Tue, Sep 27, 2011 at 20:30, Ignat Semenov 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
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. :)
There was a recent blog post by Sebastian Trug (please forgive the
umlaut, got no idea how to
