On Tue, 8 Sep 2015, Jaroslaw Staniek wrote:
On 8 September 2015 at 21:31, Friedrich W. H. Kossebau wrote:
Am Samstag, 5. September 2015, 12:55:28 schrieb Jaroslaw Staniek:
With increasing modularity it's quite important
for our debugging needs to have logging categories.
Oh, and about the file names, looks like there's no real standard yet:
boud@linux:~/kf5/src/frameworks> find . -name \*Debug\*h
./kactivities/src/service/Debug.h
boud@linux:~/kf5/src/frameworks> find . -name \*debug\*h
./krunner/src/declarative/krunner_debug.h
./krunner/src/krunner_debug.h
On 14 September 2015 at 10:46, Boudewijn Rempt wrote:
> Oh, and about the file names, looks like there's no real standard yet:
>
Yes, no standards in kf5.
> boud@linux:~/kf5/src/frameworks> find . -name \*Debug\*h
> ./kactivities/src/service/Debug.h
>
Am Samstag, 5. September 2015, 12:55:28 schrieb Jaroslaw Staniek:
> With increasing modularity it's quite important
> for our debugging needs to have logging categories.
Agreed.
> A scheme could be like
> {libnamelowercase}{Debug|Warning|Critical}()
+1 for that scheme. Simply because that
On 8 September 2015 at 21:31, Friedrich W. H. Kossebau wrote:
> Am Samstag, 5. September 2015, 12:55:28 schrieb Jaroslaw Staniek:
>> With increasing modularity it's quite important
>> for our debugging needs to have logging categories.
>
> Agreed.
>
>> A scheme could be like
>>
On 5 September 2015 at 13:41, Boudewijn Rempt wrote:
> There is one more thing about logging using qCDebug and friends:
> the logging categories are supposed to be defined _per library_.
>
> Which is actually pretty useless and not really how we've been
> using categories in
There is one more thing about logging using qCDebug and friends:
the logging categories are supposed to be defined _per library_.
Which is actually pretty useless and not really how we've been
using categories in Calligra. Logging categories for file
handling, resource management or plugin