On 19/05/14 15:39, "Ulf Hermann" wrote:
>> Please don't. quick1 is especially usefull on platforms without any
>>OpenGL.
>> And quick1 can be built without qtdeclarative. Most of the current
>> dependencies are optional, and even qtwebkit depending on qtdeclarative
>>is
>> artificial in qt.pro. q
On Thu, May 15, 2014 at 11:41 AM, Olivier Goffart wrote:
> On Monday 12 May 2014 11:48:21 Ulf Hermann wrote:
> > Hi,
> >
> > we currently have several implementations of the QML debug protocol used
> > to transmit data between a debugger or profiler and the application
> > being debugged or profi
> Please don't. quick1 is especially usefull on platforms without any OpenGL.
> And quick1 can be built without qtdeclarative. Most of the current
> dependencies are optional, and even qtwebkit depending on qtdeclarative is
> artificial in qt.pro. qtwebkit certainly builds and runs without it in Qt
On Thu, May 15, 2014 at 09:16:38AM -0700, Thiago Macieira wrote:
> Em qui 15 maio 2014, às 11:28:28, Oswald Buddenhagen escreveu:
> > > This code does not belong into Qt Base,
> >
> > if you accept that the library is an improvement over the 6 copies we
> > have all over the place, the question is
Em qui 15 maio 2014, às 11:28:28, Oswald Buddenhagen escreveu:
> > This code does not belong into Qt Base,
>
> if you accept that the library is an improvement over the 6 copies we
> have all over the place, the question is only where, not if.
> if you insist on making it a separate repository, we
On Thursday 15. May 2014 11.41.36 Olivier Goffart wrote:
> On Monday 12 May 2014 11:48:21 Ulf Hermann wrote:
> > Hi,
> >
> > we currently have several implementations of the QML debug protocol used
> > to transmit data between a debugger or profiler and the application
> > being debugged or profil
On Monday 12 May 2014 11:48:21 Ulf Hermann wrote:
> Hi,
>
> we currently have several implementations of the QML debug protocol used
> to transmit data between a debugger or profiler and the application
> being debugged or profiled. I'm proposing a generalized "debugsupport"
> module to address va
On Wed, May 14, 2014 at 11:20:10PM +0200, André Pönitz wrote:
> This code does not belong into Qt Base,
>
if you accept that the library is an improvement over the 6 copies we
have all over the place, the question is only where, not if.
if you insist on making it a separate repository, we'll have a
On Wed, May 14, 2014 at 11:37:45AM +0200, Milian Wolff wrote:
> On Tuesday 13 May 2014 21:58:29 André Pönitz wrote:
> > On Tue, May 13, 2014 at 05:30:43PM +0200, Ulf Hermann wrote:
> > > > Please create a new module. This doesn't need to be in qtbase.
> > >
> > > Is anyone opposed to keeping this
On Tuesday 13 May 2014 21:58:29 André Pönitz wrote:
> On Tue, May 13, 2014 at 05:30:43PM +0200, Ulf Hermann wrote:
> > > Please create a new module. This doesn't need to be in qtbase.
> >
> > Is anyone opposed to keeping this in a separate qtdebugsupport.git
> > repository, then?
>
> I am.
>
> A
On Tue, May 13, 2014 at 05:30:43PM +0200, Ulf Hermann wrote:
> > Please create a new module. This doesn't need to be in qtbase.
>
> Is anyone opposed to keeping this in a separate qtdebugsupport.git
> repository, then?
I am.
At the very least, this is still missing an explanation what actual
pr
>> Is anyone opposed to keeping this in a separate qtdebugsupport.git
>> repository, then?
>
> With what compatibility promises regarding code and protocol?
I would promise source and binary compatibility and backwards as well as
forward compatibility of the protocol. At the same time I would pub
Ulf Hermann:
> Is anyone opposed to keeping this in a separate qtdebugsupport.git
> repository, then?
With what compatibility promises regarding code and protocol?
Andre'
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.o
> Please create a new module. This doesn't need to be in qtbase.
Is anyone opposed to keeping this in a separate qtdebugsupport.git
repository, then?
regards,
Ulf
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailm
> One thing Andre raised though was whether we should continue running
> our own (albeit improved) proprietary protocol, or try to integrate
> into / implement TCF: http://wiki.eclipse.org/TCF
TCF has different messaging semantics. In particular it has message
types (Request, Response, Event) and
> -Original Message-
> From: André Pönitz [mailto:apoen...@t-online.de]
> [...]
> Consolidation of various incarnations of the code might make sense,
> exporting would need a good reason.
One of the reasons for the different incarnations of the client side of the
debug API
in Qt Creator &
Em seg 12 maio 2014, às 19:35:24, Oswald Buddenhagen escreveu:
> On Mon, May 12, 2014 at 08:39:37AM -0700, Thiago Macieira wrote:
> > Em seg 12 maio 2014, às 11:48:21, Ulf Hermann escreveu:
> > > The following changes create a debugsupport module with public API in
> >
> > > qtbase:
> > Please cre
On Mon, May 12, 2014 at 02:54:23PM +, Koehne Kai wrote:
> > -Original Message- From:
> > development-bounces+kai.koehne=digia@qt-project.org
> >
> > we currently have several implementations of the QML debug protocol
> > used to transmit data between a debugger or profiler and the
On Mon, May 12, 2014 at 08:39:37AM -0700, Thiago Macieira wrote:
> Em seg 12 maio 2014, às 11:48:21, Ulf Hermann escreveu:
> > The following changes create a debugsupport module with public API in
> > qtbase:
>
> Please create a new module. This doesn't need to be in qtbase.
>
given that the two
Em seg 12 maio 2014, às 11:48:21, Ulf Hermann escreveu:
> The following changes create a debugsupport module with public API in
> qtbase:
> https://codereview.qt-project.org/#change,85098
> https://codereview.qt-project.org/#change,85099
> https://codereview.qt-project.org/#change,85100
> https://
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
>
> we currently have several implementations of the QML debug protocol used
> to transmit data between a debugger or profiler and the application being
> debugged or profiled. I'm proposing a generalized
> I guess using a TCP connection would still be possible, but not be the defaut
> anymore for local debugging/profiling?
The QDebugServer so far supports four kinds of connections and it's
possible to add more. You can use local or tcp connections and both
allow you to establish them in either
+thomas.hartmann=digia@qt-project.org] on behalf of Ulf
Hermann [ulf.herm...@digia.com]
Sent: 12 May 2014 11:48
To: development@qt-project.org
Subject: [Development] new "debugsupport" module and API
Hi,
we currently have several implementations of the QML debug protocol used
to transmit data
Hi,
we currently have several implementations of the QML debug protocol used
to transmit data between a debugger or profiler and the application
being debugged or profiled. I'm proposing a generalized "debugsupport"
module to address various issues with those. In particular:
1. Code duplicati
24 matches
Mail list logo
