Re: [Development] QLog ( Work on qDebug and friends)

Hi Wolfgang, how about making the category a distinct type instead? struct QMessageCategory { explicit QMessageCategory(const char *name); }; class QMessageLogger { void debug(const char *format, ...); void debug(QMessageCategory category, const char *format, ...); } ... QDebugCatego

[Development] QLog ( Work on qDebug and friends)

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

Re: [Development] Feature freeze and Alpha

On 7.2.2012 8.48, "simo.f...@nokia.com" wrote: > > >On 2/5/12 4:12 PM, "ext lars.kn...@nokia.com" >wrote: > >>We also need to now create a team that focuses on creating packages out >>of >>our source code that we can then release. For the Alpha I propose that we >>only do source packages (grea

Re: [Development] Feature freeze and Alpha

On 2/5/12 4:12 PM, "ext lars.kn...@nokia.com" wrote: >We also need to now create a team that focuses on creating packages out of >our source code that we can then release. For the Alpha I propose that we >only do source packages (great if we get binaries though), we will however >need to prepar

Re: [Development] Feature freeze and Alpha

Hi, can we have please a Qt 5 landing page where all this information cam be found or linked? It looks like the closest now is http://wiki.qt-project.org/5.0_Feature_Targets On 02/05/2012 06:12 AM, ext lars.kn...@nokia.com wrote: > We're now starting with our feature freeze ... > We will soon

Re: [Development] Feature freeze and Alpha

> >* Smaller API additions (a function) are still ok > I think QTBUG-7369 fits in this case (smaller API additions). Here is the patch: http://codereview.qt-project.org/#change,12312 Cheers, -- Luís Gabriel OpenBossa - INdT ___ Development mail

Re: [Development] Work on qDebug and friends

> From: David Faure > To: development@qt-project.org; Diego Iastrubni > Cc: > Sent: Sunday, February 5, 2012 5:54 PM > Subject: Re: [Development] Work on qDebug and friends > > On Sunday 05 February 2012 10:50:48 BRM wrote: >> > From: Diego Iastrubni >> > >> >On Fri, Feb 3, 2012 at 1:10 PM,

Re: [Development] Feature freeze and Alpha

Hi, On 02/05/2012 11:12 AM, lars.kn...@nokia.com wrote: > Is there anything that I have now forgotten that really *must* be in 5.0 > (i.e. it really can't be done in a BC/SC way for Qt 5.1)? If you have such > an item, please speak up, otherwise I'll consider the above exception list > as final.

Re: [Development] Feature freeze and Alpha

On Sunday 05 February 2012 14:12:48 lars.kn...@nokia.com wrote: > These items are still open and we'll need feedback on them: > * network authentication and SLL errors without stalling QNAM > (QTBUG-16251, QTBUG-19032) Peter did some of the work on this: http://codereview.qt-project.org/13834 I do

Re: [Development] Feature freeze and Alpha

On Monday, 6 de February de 2012 10.56.56, morten.sor...@nokia.com wrote: > Is there anything that I have now forgotten that really *must* be in 5.0 > (i.e. it really can't be done in a BC/SC way for Qt 5.1)? If you have such > an item, please speak up, otherwise I'll consider the above exception l

Re: [Development] Feature freeze and Alpha

On Feb 5, 2012, at 3:12 PM, ext lars.kn...@nokia.com wrote: These items are still open and we'll need feedback on them: * QPA interface for native dialogs (QTBUG-20086) This one is done. Some platform filling-in of the API still remains, but the API itself is in g

Re: [Development] Thread-safety on implicitly-shared classes

Hi Thiago, On Sunday February 5 2012, Thiago Macieira wrote: > However, in practice, many people have begun relying on an implementation > detail that read-only operations (the const methods) in those classes are > thread-safe. That is, a shared object can be accessed without mutex > protection pr

Re: [Development] NOTE: Gerrit going down for quick fix deployment (10:00 CET)

On 02/06/2012 09:01 AM, Sergio Ahumada wrote: > Hi, > > Gerrit will go down at 10:00 CET > today, for deployment of fixes. > > Fixes are: > > QTQAINFRA-220 > QTQAINFRA-348 > QTQAINFRA-355 > QTQAINFRA-372 > QTQAINFRA-375 > QTQAINFRA-381 > QTQAINFRA-411 > > It sho

[Development] JIRA bug management: users can't close their 'assigned' bugs.

Hi everyone, I have a number of "stale" bugs which need to be closed. When bugs are "Assigned", even to "Earth Domain", the original reporter is unable to close them. SO, for the purpose of removing bad data from our DB, I'm requesting help with the following bugs. I'm the reporter/creator of i

[Development] NOTE: Gerrit going down for quick fix deployment (10:00 CET)

Hi, Gerrit will go down at 10:00 CET today, for deployment of fixes. Fixes are: QTQAINFRA-220 QTQAINFRA-348 QTQAINFRA-355 QTQAINFRA-372 QTQAINFRA-375 QTQAINFRA-381 QTQAINFRA-411 It should only take a few minutes to deploy and restart the service, should no