On Jan 3, 2012, at 7:24 PM, ext BogDan wrote:
> Hi again,
>
> I forgot on item on my list, I hope is not too late :)
> A way to pause/resume the application (all QEventLoop(s)) from another thread.
> It is useful because Android tries to pause the application when it goes in
> background
>
>
Den 03. jan. 2012 15:51, skrev ext Kent Hansen:
>
> I created http://code.google.com/p/v8/issues/detail?id=1885 for the icc
> fix (note that I'm not allowed to submit patches :( ). Make sure to vote
> for it! ;) I'll import your patch into our tree for the time being.
The issue was merged into
ht
On 01/03/2012 01:07 PM, ext Thiago Macieira wrote:
> On Tuesday, 3 de January de 2012 09.53.41, Jonas M. Gastal wrote:
>> As for removing them entirely yes, it would require changes in the HTTP
>> socket engine and QAuthenticator. But given that both of them use
>> QHttpResponseHeader I see no rea
On 01/01/2012 04:51 PM, ext Andreas Aardal Hanssen wrote:
> (...)
> The other options I imagined were GnuTLS [*], and using native SSL support
> should that exist.
>
> Today the backend separation is still around but it only complicates the
> code unless there truly are other backends to support.
On Wednesday, 4 de January de 2012 11.00.35, Kent Hansen wrote:
> Den 03. jan. 2012 15:51, skrev ext Kent Hansen:
> > I created http://code.google.com/p/v8/issues/detail?id85 for the icc
> > fix (note that I'm not allowed to submit patches :( ). Make sure to vote
> > for it! ;) I'll import your pa
On Wednesday, 4 de January de 2012 06.32.52, martin.jo...@nokia.com wrote:
> 1. The capitalization of the first alpha character after the underscore is
> deliberate. Signal handlers are defined as being 'on' followed by a
> capital letter. Since underscore has no capital, it must be the first
> n
Thiago, et al.:
This is another one of those "don't play in the
grey areas of the language" things.
Even if identifiers are case-sensitive, one should
probably never depend upon that; why tempt fate?
Atlant
-Original Message-
From: development-bounces+a
Hi,
On Tue, Jan 3, 2012 at 7:16 PM, wrote:
> On 03/01/2012 12:01, ext Thiago Macieira wrote:
>> On Tuesday, 3 de January de 2012 18.19.47, Denis Dzyubenko wrote:
>>> That's the thing - it doesn't work in some cases - if you do
>>> in-source-tree build of the attached project. Well now thinking
>
Hi,
I've made a patch for syncqt to make it generate forward include
header (e.g. "include/QtCore/QObject" and "include/QtCore/qobject.h")
even if the class name doesn't have a "Q" prefix - in qtjsondb module
all classes have "JsonDb" prefix instead and that confused syncqt.
I made it configurabl
Den 03. jan. 2012 22:07, skrev ext lars.kn...@nokia.com:
> On 1/3/12 5:45 PM, "ext Oswald Buddenhagen"
> wrote:
>
>> On Tue, Jan 03, 2012 at 01:45:27PM -0200, ext Thiago Macieira wrote:
>>> Configure already sets a "default" mkspec symlink that matches the
>>> target
>>> mkspec. Making it also crea
On Wednesday, 4 de January de 2012 07.51.48, Atlant Schmidt wrote:
> Thiago, et al.:
>
> This is another one of those "don't play in the
> grey areas of the language" things.
>
> Even if identifiers are case-sensitive, one should
> probably never depend upon that; why tempt fate?
"You shou
On Wednesday, 4 de January de 2012 15.01.47, Denis Dzyubenko wrote:
> Hi,
>
> I've made a patch for syncqt to make it generate forward include
> header (e.g. "include/QtCore/QObject" and "include/QtCore/qobject.h")
> even if the class name doesn't have a "Q" prefix - in qtjsondb module
> all classe
Thiago:
Let me more-explicitly/completely state the rule
that I use:
1. Always use the canonical casing for an identifier.
2. Don't create any other identifiers that differ
from an existing canonical identifier only in
their casing.
At
Hi Thiago,
2012/1/4 Thiago Macieira :
>> I made it configurable via sync.profile -
>> http://codereview.qt-project.org/12128
>
> Have you checked what other stuff it creates on other modules?
>
> The Q-protection was intentional, since there are other helper structs and
> classes in Qt code.
I'v
On Wednesday, 4 de January de 2012 01.53.44, martin.jo...@nokia.com wrote:
> >From the QtDeclarative point of view, apart from having our tests pass, I'd
> >like to see some comparisons in QML load time, using photoviewer as a test
> >case, for example.
> Looks like performance was an important con
Hi, sorry for webmail top-posting.
June 28th - June 30th are the only dates available during June at the (amazing)
venue we are looking for in Berlin. Would that work for you?
Planning for bigger rooms, ok.
Limiting the participation to 200-250 would be a design decision: registration
by invit
On Wednesday, 4 de January de 2012 09.42.52, Atlant Schmidt wrote:
> Let me more-explicitly/completely state the rule
> that I use:
>
> 1. Always use the canonical casing for an identifier.
>
> 2. Don't create any other identifiers that differ
>from an existing canonical identif
On 04/01/2012 09:26, ext quim@nokia.com wrote:
> June 28th - June 30th are the only dates available during June at the
> (amazing) venue we are looking for in Berlin. Would that work for
> you?
Those dates work for me, but might be cutting it really close to summer
vacation for others?
> Pl
On Wednesday, 4 de January de 2012 15.26.06, quim@nokia.com wrote:
> Hi, sorry for webmail top-posting.
>
> June 28th - June 30th are the only dates available during June at the
> (amazing) venue we are looking for in Berlin. Would that work for you?
Non-starter. Collides with Akademy (Jun 30-
On 04/01/2012 09:54, ext Thiago Macieira wrote:
> On Wednesday, 4 de January de 2012 15.26.06, quim@nokia.com wrote:
>> Hi, sorry for webmail top-posting.
>>
>> June 28th - June 30th are the only dates available during June at the
>> (amazing) venue we are looking for in Berlin. Would that work
Hi,
On 04/01/2012, at 3:29 PM, ext Thiago Macieira wrote:
> On Wednesday, 4 de January de 2012 09.42.52, Atlant Schmidt wrote:
>> Let me more-explicitly/completely state the rule
>> that I use:
>>
>>1. Always use the canonical casing for an identifier.
>>
>>2. Don't create any other i
On 01/04/2012 07:59 AM, ext marius.storm-ol...@nokia.com wrote:
> On 04/01/2012 09:54, ext Thiago Macieira wrote:
>> On Wednesday, 4 de January de 2012 15.26.06, quim@nokia.com wrote:
>>> Hi, sorry for webmail top-posting.
>>>
>>> June 28th - June 30th are the only dates available during June a
On Wednesday, January 04, 2012 14:22:55 Friedemann Kleint wrote:
> Hi Stephen,
>
> A Happy New Year to you.
>
> > It failed because QFormBuilder is no longer available. Then I noticed
> > that the entire designer library and interface is no longer available.
> >
> > Why was that done and can it
Replying to myself to try and get the discussion going again.
A summary of API decisions so far:
- we only provide an asynchronous API
- we do not want a "manager" object (QNAM-style) to avoid users creating a
manager per lookup
- we want a single class to support different types of DNS reques
Le Jan 4, 2012 à 11:47 AM, Peter Hartmann a écrit :
> On 01/03/2012 01:07 PM, ext Thiago Macieira wrote:
>> On Tuesday, 3 de January de 2012 09.53.41, Jonas M. Gastal wrote:
>>> As for removing them entirely yes, it would require changes in the HTTP
>>> socket engine and QAuthenticator. But give
On Wed, Jan 4, 2012 at 2:47 PM, Denis Dzyubenko wrote:
> On Tue, Jan 3, 2012 at 7:16 PM, wrote:
>> On 03/01/2012 12:01, ext Thiago Macieira wrote:
>>> On Tuesday, 3 de January de 2012 18.19.47, Denis Dzyubenko wrote:
That's the thing - it doesn't work in some cases - if you do
in-sourc
On Wed, Jan 4, 2012 at 5:23 PM, Quim Gil wrote:
> On 01/04/2012 07:59 AM, ext marius.storm-ol...@nokia.com wrote:
> > On 04/01/2012 09:54, ext Thiago Macieira wrote:
> >> On Wednesday, 4 de January de 2012 15.26.06, quim@nokia.com wrote:
> >>> Hi, sorry for webmail top-posting.
> >>>
> >>> Ju
On 04/01/2012 10:48, ext Thiago Macieira wrote:
> Highlights:
>
> * EVERYTHING tested is faster
>(though unfortunately nothing reaches 1 robe)
For the uninitiated, 1 robe = 10x performance increase, since Roberto
has the uncanny ability to speed up his parser performance by 10x every
time he
On 4 January 2012 18:49, wrote:
> On 04/01/2012 10:48, ext Thiago Macieira wrote:
>> Highlights:
>>
>> * EVERYTHING tested is faster
>> (though unfortunately nothing reaches 1 robe)
>
> For the uninitiated, 1 robe = 10x performance increase, since Roberto
> has the uncanny ability to speed up
On Wednesday, 4 de January de 2012 08.23.12, Quim Gil wrote:
> More thoughts on combining the Qt Contributors Summit with aKademy in
> Tallinn? I have been there and it's not a bad city. I believe it has
> cheap flights from many European destination and maybe the prices are in
> average lower than
On Wednesday, 4 de January de 2012 19.10.39, Giuseppe D'Angelo wrote:
> On 4 January 2012 18:49, wrote:
> > On 04/01/2012 10:48, ext Thiago Macieira wrote:
> >> Highlights:
> >>
> >> * EVERYTHING tested is faster
> >>(though unfortunately nothing reaches 1 robe)
> >
> > For the uninitiated, 1
Great !
Is there any API to hide/show all app windows ?
Or I have to iterate all top level widgets and hide/show all of them ?
>
>
> On Jan 3, 2012, at 7:24 PM, ext BogDan wrote:
>
>> Hi again,
>>
>> I forgot on item on my list, I hope is not too late :)
>> A way to pause/resume the appl
On 05/01/2012, at 3:51 AM, Jeremy Lainé wrote:
> Replying to myself to try and get the discussion going again.
>
> A summary of API decisions so far:
>
> - we only provide an asynchronous API
>
> - we do not want a "manager" object (QNAM-style) to avoid users creating a
> manager per lookup
>
On Thursday, 5 de January de 2012 11.03.42, craig.sc...@csiro.au wrote:
> This could be perceived as creating a race condition. You'd have to connect
> a slot to the signal on the object returned, but what if the signal is
> emitted before you get a chance to do that?
It cannot happen if you make
On 05/01/2012, at 11:47 AM, Thiago Macieira wrote:
> On Thursday, 5 de January de 2012 11.03.42, craig.sc...@csiro.au wrote:
>> This could be perceived as creating a race condition. You'd have to connect
>> a slot to the signal on the object returned, but what if the signal is
>> emitted before y
On Thursday, 5 de January de 2012 12.07.37, craig.sc...@csiro.au wrote:
> On 05/01/2012, at 11:47 AM, Thiago Macieira wrote:
> > On Thursday, 5 de January de 2012 11.03.42, craig.sc...@csiro.au wrote:
> >> This could be perceived as creating a race condition. You'd have to
> >> connect
> >> a slot
On 05/01/2012, at 12:11 PM, Thiago Macieira wrote:
> On Thursday, 5 de January de 2012 12.07.37, craig.sc...@csiro.au wrote:
>> On 05/01/2012, at 11:47 AM, Thiago Macieira wrote:
>>> On Thursday, 5 de January de 2012 11.03.42, craig.sc...@csiro.au wrote:
This could be perceived as creating a
On Thursday, 5 de January de 2012 12.51.50, craig.sc...@csiro.au wrote:
> Ah, the reply object emits the signal in the same thread as the caller? I
> was assuming the signal is emitted from within the thread that is
> processing the reply. Yes, in that case connecting before returning to the
> even
On 01/05/2012 01:47 AM, Thiago Macieira wrote:
> On Thursday, 5 de January de 2012 11.03.42, craig.sc...@csiro.au wrote:
>> This could be perceived as creating a race condition. You'd have to connect
>> a slot to the signal on the object returned, but what if the signal is
>> emitted before you get
On 01/05/2012 01:03 AM, craig.sc...@csiro.au wrote:
>> Some notes about the implementation:
>>
>> - the actual lookup code is run in a thread, managed by a global threadpool
>> (QHostInfo-style)
> What happens if the client/user is also employing their own thread pool? Does
> your implementation
40 matches
Mail list logo
