> -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 ter 13 maio 2014, às 06:01:00, Knoll Lars escreveu:
> Actually I was thinking about splitting a few more things out. In addition
> to the ones mentioned above, I believe we would benefit from splitting
> QtNetwork out into it’s own module. The reason is that QtNetwork is
> responsible for many o
> -Original Message-
> The Unified field is open two extra windows. Not very convenient.
Sorry, the standard Gerrit way was in use instead of our one page review. Fixed
now.
___
Development mailing list
Development@qt-project.org
http://lists.q
Kurt Pattyn [pattyn.k...@gmail.com]:
> This makes sense. Maybe the WebSockets module can be
> integrated into the network module in that case?
Is there something Network really needs out of Websockets?
Especially for security sensitive areas like network "nice to have"
is not a good reason for co
On 13/05/14 08:23, "Kalinowski Maurice"
wrote:
>> >The rest of the libraries in qtbase are really base stuff.
>>
>> Actually I was thinking about splitting a few more things out. In
>>addition to
>> the ones mentioned above, I believe we would benefit from splitting
>> QtNetwork out into it’s ow
> >The rest of the libraries in qtbase are really base stuff.
>
> Actually I was thinking about splitting a few more things out. In addition to
> the ones mentioned above, I believe we would benefit from splitting
> QtNetwork out into it’s own module. The reason is that QtNetwork is
> responsible
> On 13 May 2014, at 08:01, Knoll Lars wrote:
>
>> On 12/05/14 22:40, "Thiago Macieira" wrote:
>>
>>> 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 escrev
On 12/05/14 22:40, "Thiago Macieira" wrote:
>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 wi
Em seg 12 maio 2014, às 12:27:46, Oswald Buddenhagen escreveu:
> > >- Plugin loading where there are multiple versions on the same
> > >system.
> > >- File format validation.
> > >- Executing an already installed command line application where the
> > >behavior is dependent on t
>
> > >- Plugin loading where there are multiple versions on the same
> system.
> > >- File format validation.
> > >- Executing an already installed command line application where the
> > >behavior is dependent on the called application's version.
> > >- Performing software inst
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
Hi
The Unified field is open two extra windows. Not very convenient.
It would be nice to have the conflict feature of 2.9 too. ;-)
Otherwise the new gerrit it really nice.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.
When will the new Gerrit version be deployed to production?
--
Jake Petroules - jake.petroules at petroules.com
Chief Technology Officer - Petroules Corporation
On 2014-05-12, at 10:08 AM, Haataja Ismo wrote:
>> And to see/try all the changes in action, everything is deployed to
>> https://dev-
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
> And to see/try all the changes in action, everything is deployed to
> https://dev-codereview.qt-project.org for testing.
Sorry, my bad, just got informed this is not publicly available.
___
Development mailing list
Development@qt-project.org
http://lis
On Mon, May 12, 2014 at 01:57:16PM +, Haataja Ismo wrote:
> And to see/try all the changes in action, everything is deployed to
> https://dev-codereview.qt-project.org for testing.
>
that testing request applies only to digia employees due to the host
being firewalled.
___
Hi,
For upcoming Gerrit (Code Review) upgrade all the changes are pushed for review:
https://codereview.qt-project.org/#q,status:open+project:qtqa/gerrit+branch:v2.7.0-based,n,z
We'd like to call everybody to participate for reviewing. So, if interested,
you are very welcome to share your persona
When I compile my app for Android with 5.3.0 RC1, does it also request 5.3.0
RC1 libs via Ministro ?
(or how can I make it use 5.3.0 RC libs also on the Android device via
Ministro) ?
--
Best regards/Schöne Grüße
Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top post
On 10/05/14 19:20 , Christophe Thomas wrote:
> My understand reading the comment of the bug report that if we want to have
> a custom image we need to use a custom plist and define a different name
> for the image from the default one.
> Is my undertansding ok ? Is there another way to have a cu
On 11 May 2014, at 21:53, Tim Blechmann wrote:
>
> the 32bit versions seem to use the _debug suffix ... the difference does
> not occur in all frameworks, but only in:
> QtCore.framework
> QtMultimediaQuick_p.framework
> QtPrintSupport.framework
> QtScriptTools.framework
> QtSerialPort.framewor
> 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
On Sat, May 10, 2014 at 03:39:51PM -0700, Thiago Macieira wrote:
> Em sáb 10 maio 2014, às 22:04:26, Sune Vuorela escreveu:
> > On 2014-05-10, Thiago Macieira wrote:
> > > How do you make 5.3.0-rc1 compare less than 5.3.0?
> >
> > we call them 5.3.0~rc1.
>
> And how does "5.3.0~rc1" compare less
Hi,
I guess using a TCP connection would still be possible, but not be the defaut
anymore for local debugging/profiling?
Kind Regards,
Thomas Hartmann
From: development-bounces+thomas.hartmann=digia@qt-project.org
[development-bounces+thomas.hartmann
>> In the final RC the libegl binary files (*.lib, *.dll) are missing.
>> I did not have this problem with the previous snapshots.
> Hmm I don't think the _opengl variant is supposed to contain libegl
(angle) - I think only the angle variant is supposed to.
> Simon
Ok, I checked again and it
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
Hi,
Not sure what kind of custom mods you have but a module "claims" plugin
ownership via
MODULE_PLUGIN_TYPES = geoservices (see qtloation.pro)
The plugin declares its type via
PLUGIN_TYPE = geoservices (e.g. see src/plugins/geoservices/osm/osm.pro
And the system enforces this in mkspecs/fe
Hmm I don't think the _opengl variant is supposed to contain libegl (angle) - I
think only the angle variant is supposed to.
Simon
Opprinnelig melding
Fra: Helmut Mülner
Sendt: 09:39 mandag 12. mai 2014
Til: development@qt-project.org
Emne: [Development] qt-opensource-windows-x86-msvc2012_open
In the final RC the libegl binary files (*.lib, *.dll) are missing.
I did not have this problem with the previous snapshots.
Best regards
Helmut
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/develo
hi all,
not sure if this is a bug or a feature, or a problem or not, but it
occurred to me that the Info.plist files differ between 32bit and 64bit
frameworks:
> --- osx-clang-32/lib/QtMultimediaQuick_p.framework/Contents/Info.plist
> 2014-05-10 18:29:13.0 +0200
> +++ osx-clang-64
32 matches
Mail list logo
