Before I would do such a change I would check if there are other projects in QT
they install their own messaghandler.
I think they all need to change their code as well.
Maybe we should keep it as it is.
Cheers,
WB
-Original Message-
From: development-bounces+wolfgang.beck=nokia@qt
Hi guys,
QLogger is now available as a module:
git clone http://codereview.qt-project.org/p/playground/qlogger
At this moment %{category} syntax in MessagePattern can't be used because we
need to wait for a qtbase update.
Therefore we created a QLogger module that works with the current qtbase.
Hi guys,
I'm following the steps on
http://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
To get a playground project created for qlogger in place.
qlogger should be the previous discussed category logging mechanism on the
developer ML.
(see http://codereview.qt-project.org/#change,13
Hi guys,
A new patch is ready.
Logging into a file is now removed because of possible maintenance trouble.
http://codereview.qt-project.org/#change,13226
Cheers,
WB
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mai
Hi guys,
I need to have a vote on a implementation detail regarding filtering of
wildcards categories.
Let's say you have a category defined and a wildcard category as well.
A: Do you think the order in the configuration file plays an important rule or
B: If you set specific a category let's say
OK,
So we've now 2 options to set the config file.
1. QLOG_CONFIG_FILE environment variable
2. setDefaultConfigFile function.
What do you mean with:
... and to supplying a QIODevice*?
B.R.
WB
-Original Message-
From: development-bounces+wolfgang.beck=nokia@qt-projec
We had this discussion before in the ML to add cool stuff like
Log into local socked, syslog or whatever.
This can be done later in an AddOn for example.
Cheers,
WB
-Original Message-
From: development-bounces+wolfgang.beck=nokia@qt-project.org
[mailto:development-bounces
Why you want to use the categories somewhere else then QLog?
You want to reinvent a mechanism to filter the categories then?
If you don't filter what sense makes having the categories?
I mean you still have qDebug and you can write whatever you like.
Cheers,
WB
-Original Message-
From:
Yes David,
Absolutely right.
B.R.
WB
-Original Message-
From: ext David Faure [mailto:david.fa...@kdab.com]
Sent: Tuesday, February 21, 2012 8:08 PM
To: Koehne Kai (Nokia-MP/Berlin)
Cc: Beck Wolfgang (Nokia-MP/Brisbane); development@qt-project.org
Subject: Re: [Development] QLog ( Wor
> So how about adding another QtMsgType called QLogMsg, that qLog() uses? In
> contrast to qDebug/QtDebugMsg, qLog/QtLogMsg messages would not be processed
> by default, unless the configuration file (or an environment variable) says
> so ...
There is no need for this Kai.
The macro will not ev
QLOG ENABLED
I guess you misunderstood me.
QLog is enabled ONLY if a config file was found.
We have 3 ways to define the config file:
1. Default using application name configuration default path and organization
name for the path
2. Application developer can call the QLog function "setDefaultConf
please visit:
http://codereview.qt-project.org/13226
B.R.
WB
-Original Message-
From: development-bounces+wolfgang.beck=nokia@qt-project.org
[mailto:development-bounces+wolfgang.beck=nokia@qt-project.org] On Behalf
Of ext Thiago Macieira
Sent: Tuesday, February 21, 2012 3:18
file and change the category
values?
B.R.
WB
-Original Message-
From: development-bounces+wolfgang.beck=nokia@qt-project.org
[mailto:development-bounces+wolfgang.beck=nokia@qt-project.org] On Behalf
Of ext BRM
Sent: Tuesday, February 21, 2012 12:14 AM
To: developme
Yes I know and I've changed it.
No QSetting is used anymore.
B.R.
WB
-Original Message-
From: development-bounces+wolfgang.beck=nokia@qt-project.org
[mailto:development-bounces+wolfgang.beck=nokia@qt-project.org] On Behalf
Of ext Thiago Macieira
Sent: Monday, February 20,
ssible but still having the feature that you can activate it without
recompiling the code.
Cheers,
WB
-Original Message-
From: development-bounces+wolfgang.beck=nokia@qt-project.org
[mailto:development-bounces+wolfgang.beck=nokia@qt-project.org] On Behalf
Of ext David Faure
Se
Hi Kai,
I'm trying to use the QMessagePattern and I'm missing some documentation here.
Is the usage of the environment variable QT_MESSAGE_PATTERN even documented?
Cheers,
WB
___
Development mailing list
Development@qt-project.org
http://lists.qt-proje
and friends)
Already done.
I'm using
if (!global_enabled()) /*NOP*/; else QMessageLogger(__FILE__, __LINE__,
Q_FUNC_INFO).debug
Anyway I will make sure that qlog still works even with -DQT_NO_WARNING_OUTPUT
Cheers,
WB
-Original Message-
From: development-bounces+wolfgang.b
Already done.
I'm using
if (!global_enabled()) /*NOP*/; else QMessageLogger(__FILE__, __LINE__,
Q_FUNC_INFO).debug
Anyway I will make sure that qlog still works even with -DQT_NO_WARNING_OUTPUT
Cheers,
WB
-Original Message-
From: development-bounces+wolfgang.beck=nokia..
Well I think I can change the macro name very easy but we can't name it qDebug.
So maybe qDebugCat or somethink like this.
But I think the macro is very necessary special if you develop for devices they
don't have the capacity of a desktop machine.
Cheers,
WB
-Original Message-
Fro
QLog uses QMessageLogger.
Please check patch:
http://codereview.qt-project.org/#change,13226
B.R.
WB
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Hi Kai,
The controlling of the category will be done using a configuration file.
QLog contains a private class that creates a file watcher for the configuration
file.
So not only if you start the application but during runtime as well the
category filtering can be changed dynamically by changing
Hi Kai,
I think this was a very good idea so I've tried it but I've run into one
important problem.
If I use this trick I have to call the overloaded function in QMessageLogger:
e.g.
1. void debug(QMessageCategory category, const char *format, ...);
and
2. QDebug debug(QMessageCategory category)
I'm working to integrade category log with QMessageLogger & Co and
unfortunatelly we can not use
qDebg() << "my message" because there is already a debug(const char
*msg, ...) function
combining with the macro
#define qDebug QMessageLogger(__FILE__, __LINE__, Q_FUNC_INFO).debug.
So I use a new
e and maybe
environment variable but no recompiling neccessary.
--
wbeck
-Original Message-
From: development-bounces+wolfgang.beck=nokia@qt-project.org
[mailto:development-bounces+wolfgang.beck=nokia@qt-project.org] On Behalf
Of ext BRM
Sent: Friday, February 03, 2012 11:33
cool stuff like writing into sockets can be done in an addOn or even in a
plugin.
--
WB
-Original Message-
From: development-bounces+wolfgang.beck=nokia@qt-project.org
[mailto:development-bounces+wolfgang.beck=nokia@qt-project.org] On Behalf
Of ext Robin Burchell
Sent: Thursday
Hi there,
I'm finished to make a patch and created the documentation of QLog.
To be sure that all can read the document I've attached it to this EMail.
The main focus on this project is:
1. Logging in a file:
2. Enable or disable logging without recompiling your project.
3. Logging with categorie
Sorry, forgot the Subject
-Original Message-
From: Beck Wolfgang (Nokia-MP/Brisbane)
Sent: Monday, January 30, 2012 10:02 AM
To: development@qt-project.org
Cc: 'craig.sc...@csiro.au'
Subject: RE: Development Digest, Vol 4, Issue 94
>Date: Sun, 29 Jan 2012 01:55:54 +1100
>From:
>Subject:
>Date: Sun, 29 Jan 2012 01:55:54 +1100
>From:
>Subject: Re: [Development] Work on qDebug and friends
>To:
>Message-ID: <6219d4f4-6cd0-4c5f-9e82-3a4a722ed...@csiro.au>
>Content-Type: text/plain; charset="us-ascii"
>Sorry for the lack of context (dealing with digest emails while on leave :-P ).
>
I think QLog from QTopia was very good.
You define your category in your project and QLog will define a static bool for
each category e.g.
# define QLOG_ENABLE(dbgcat) \
class dbgcat##_QLog : public QLogBase { \
public: \
static inline bool enabled() { return 1; }\
};
29 matches
Mail list logo
