Re: branches/extragear/graphics/kipi-plugins/gpssync2

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: branches/extragear/graphics/kipi-plugins/gpssync2

Johannes Wienke-2
Am 22.06.2010 20:57, schrieb Gabriel Voicu:
> SVN commit 1141413 by gvoicu:
>
> Deleted all unwanted kDebug

Did I ever mention that kDebug / qDebug is really weak compared to
loggers like log4cxx. There you would have simply assigned a tracing
level to these messages or used a different logger. So you would always
have the log messages on demand without recompiling. It's a pitty that
kDebug is not that flexible.

Johannes


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

signature.asc (268 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: branches/extragear/graphics/kipi-plugins/gpssync2

Bugzilla from andi.clemens@gmx.net
I only know log4j but this absolutely rocks.
Yes, it would be so much nicer to use a "real" logging system.

Maybe we can easily adopt to log4cxx? Nobody forces us to use kDebug :D


Andi Clemens
-----------------
www.digikam.org

On Tuesday 22 June 2010 21:09:03 Johannes Wienke wrote:

> Am 22.06.2010 20:57, schrieb Gabriel Voicu:
> > SVN commit 1141413 by gvoicu:
> >
> > Deleted all unwanted kDebug
>
> Did I ever mention that kDebug / qDebug is really weak compared to
> loggers like log4cxx. There you would have simply assigned a tracing
> level to these messages or used a different logger. So you would always
> have the log messages on demand without recompiling. It's a pitty that
> kDebug is not that flexible.
>
> Johannes
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: branches/extragear/graphics/kipi-plugins/gpssync2

Johannes Wienke-3
Am 23.06.2010 20:13 schrieb Andi Clemens:
> I only know log4j but this absolutely rocks.
> Yes, it would be so much nicer to use a "real" logging system.

log4cxx is a direct port to C++.

> Maybe we can easily adopt to log4cxx? Nobody forces us to use kDebug :D

log4cxx has heavy dependencies, e.g. on the complete Apache Portable
Runtime system (apr) and is bad to compile on windows. So this would be
a major decision. There are loggers with a similar interface that are
nearly as powerful but are self-contained. I forgot their names, but
should be easy to find on google.

Johannes


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

signature.asc (270 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: branches/extragear/graphics/kipi-plugins/gpssync2

Gabriel Voicu
Hello guys,

Thank you bringing in discussion this because, I was thinking these days if there isn't something more flexible than kDebug. I will search more info about log4cxx and log4j. 

On Wed, Jun 23, 2010 at 9:16 PM, Johannes Wienke <[hidden email]> wrote:
Am 23.06.2010 20:13 schrieb Andi Clemens:
> I only know log4j but this absolutely rocks.
> Yes, it would be so much nicer to use a "real" logging system.

log4cxx is a direct port to C++.

> Maybe we can easily adopt to log4cxx? Nobody forces us to use kDebug :D

log4cxx has heavy dependencies, e.g. on the complete Apache Portable
Runtime system (apr) and is bad to compile on windows. So this would be
a major decision. There are loggers with a similar interface that are
nearly as powerful but are self-contained. I forgot their names, but
should be easy to find on google.

Johannes


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel



_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel