Re: [Development] Tracing Qt

2013-08-29 Thread achartier
Burchell; development@qt-project.org > > Cc: Poenitz Andre > > Subject: Re: [Development] Tracing Qt > > > > Hi Robin, > > > > I am not sure whether you are aware of > > http://qt.gitorious.org/qtplayground/qlogger > > > > It is pretty much what

Re: [Development] Tracing Qt

2013-08-26 Thread Koehne Kai
.org > Cc: Poenitz Andre > Subject: Re: [Development] Tracing Qt > > Hi Robin, > > I am not sure whether you are aware of > http://qt.gitorious.org/qtplayground/qlogger > > It is pretty much what you describe. It was even close to a merge into qtcore > already (only

Re: [Development] Tracing Qt

2013-08-26 Thread Philip Ashmore
On 26/08/13 07:41, Koehne Kai wrote: >> -Original Message- >> From: development-bounces+kai.koehne=digia@qt-project.org >> [...] >>> For a tracing system to be useful and stand a chance of being adopted >>> by the libraries used by Qt as well as Qt itself, it shouldn't be part of >>> Q

Re: [Development] Tracing Qt

2013-08-25 Thread Koehne Kai
> -Original Message- > From: development-bounces+kai.koehne=digia@qt-project.org > [...] > > For a tracing system to be useful and stand a chance of being adopted > > by the libraries used by Qt as well as Qt itself, it shouldn't be part of > > Qt. > [...] > The point of proposing a tr

Re: [Development] Tracing Qt

2013-08-23 Thread Philip Ashmore
gure build targets, the defaults are "debug" and "release". The point of proposing a tracing system/library that's not part of Qt is that it can be adopted by non-Qt libraries which Qt might eventually use. > Regards, > Philip Ashmore >> >>

Re: [Development] Tracing Qt

2013-08-23 Thread Philip Ashmore
t.org > [development-bounces+alexander.blasche=digia@qt-project.org] on behalf of > Robin Burchell [robin...@viroteck.net] > Sent: Friday, August 23, 2013 13:20 > To: development@qt-project.org > Cc: Poenitz Andre > Subject: [Development] Tracing Qt > > Hi, > >

Re: [Development] Tracing Qt

2013-08-23 Thread André Pönitz
On Fri, Aug 23, 2013 at 12:30:09PM +, Rutledge Shawn wrote: > > On 23 Aug 2013, at 1:20 PM, Robin Burchell wrote: > > Thoughts, flames, cookies? > > Yes I've been interested in doing something like that too, for debugging > touch and other types of events. The biggest problem with events is

Re: [Development] Tracing Qt

2013-08-23 Thread Rutledge Shawn
On 23 Aug 2013, at 1:20 PM, Robin Burchell wrote: > Thoughts, flames, cookies? Yes I've been interested in doing something like that too, for debugging touch and other types of events. The biggest problem with events is that they get converted into different types and queued multiple times, wh

Re: [Development] Tracing Qt

2013-08-23 Thread Blasche Alexander
To: development@qt-project.org Cc: Poenitz Andre Subject: [Development] Tracing Qt Hi, (apologies in advance for the wall of text) It's inevitable when working with Qt that sooner or later, you probably have a desire to work on tracing Qt - or at least part of it. Qt Creator's QML profi

[Development] Tracing Qt

2013-08-23 Thread Robin Burchell
Hi, (apologies in advance for the wall of text) It's inevitable when working with Qt that sooner or later, you probably have a desire to work on tracing Qt - or at least part of it. Qt Creator's QML profiler is one such very prominent example of an area where this may be useful, but there are man