Re: [Development] Platform Look and feel

On 2/9/12 11:02 PM, "ext Alan Alpert" wrote: >On Fri, 10 Feb 2012 03:37:44 ext Thiago Lacerda wrote: >> Hi, >> >> Is there a way, on Qt5, to get the platform look and feel, without the >> dependency of QtWidgets using QStyle? >> Or this is a feature that needs to be discussed about or done (for

[Development] QLog ( Work on qDebug and friends)

QLog uses QMessageLogger. Please check patch: http://codereview.qt-project.org/#change,13226 B.R. WB ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] RFC: The Future of QDoc

Op 10-2-2012 8:07, Andre Somers schreef: > Op 9-2-2012 19:13, marius.storm-ol...@nokia.com schreef: >> On 09/02/2012 10:33, ext Manuel Nickschas wrote: >>> On Thursday 09 February 2012 15:36:09 ext Olivier Goffart wrote: > I am working on QDoc part-time and we have been discussing some > ch

Re: [Development] RFC: The Future of QDoc

Op 9-2-2012 19:13, marius.storm-ol...@nokia.com schreef: > On 09/02/2012 10:33, ext Manuel Nickschas wrote: >> On Thursday 09 February 2012 15:36:09 ext Olivier Goffart wrote: I am working on QDoc part-time and we have been discussing some changes that we would like to implement to make q

[Development] Proposing Sergey Dubitskiy for Approver Status

Hi, I hereby propose Sergey Dubitskiy for the role of approver. Sergey has previously worked for some months on the Multimedia Framework and has now turned his attention to Qt3D. Br, Martin. Sarah Smith Team Lead Qt3D Email: sarah.j.sm...@nokia.com Ph: +614482834

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

Hi Kai, The controlling of the category will be done using a configuration file. QLog contains a private class that creates a file watcher for the configuration file. So not only if you start the application but during runtime as well the category filtering can be changed dynamically by changing

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

On 02/10/2012 01:16 AM, ext BRM wrote: > That said, there may be a place for having a compile time option to > entirely disable it too - e.g. for distributions and commercial > (Digia) binary releases to be able to completely disable it on > release builds. Removing the logging statement entirely

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

On 02/09/2012 07:05 PM, ext kai.koe...@nokia.com wrote: > I see. You'll indeed need something like that if you want to define > which category to log or not with the help of the macro expander. The point here is that a disabled category adds very minimal runtime overhead. We must get to the "do n

Re: [Development] Feature freeze and Alpha

On quinta-feira, 9 de fevereiro de 2012 20.00.40, John Layt wrote: > 1) Change QLocale date/time format API to match ICU/CLDR features. This is > by necessity a source-incompatible change. > > 2) Change the date/time format codes to match ICU/CLDR codes. This is by > necessity a source and behav

Re: [Development] Feature freeze and Alpha

Dear Lars, On Thursday 09 February 2012, 21:00:40 John Layt wrote: > On Sunday 05 Feb 2012 14:12:48 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, p

Re: [Development] Changes to the Jira roles and workflow

On Thu, 9 Feb 2012 12:58:40 ext marius.storm-ol...@nokia.com wrote: > Hi, > > ... > > > There is some discussion over if we should burden maintainers with Release > Management work. > > There is a suggestion of a new workflow "Nokia Engineer" - no privileges in > Gerrit only in Jira. That role

Re: [Development] Platform Look and feel

On Fri, 10 Feb 2012 03:37:44 ext Thiago Lacerda wrote: > Hi, > > Is there a way, on Qt5, to get the platform look and feel, without the > dependency of QtWidgets using QStyle? > Or this is a feature that needs to be discussed about or done (for 5.1 > maybe?)? > The plan I'm aware of for getting

Re: [Development] RFC: The Future of QDoc

> From: "casper.vandonde...@nokia.com" >Just to add what I think to Marius' comments: >1. Doxygen would need some extra features, the major one being QML, but also >being able to use index files to easily link for instance the Creator docs to >the Qt docs. Why would Doxygen need QML itself? O

Re: [Development] Feature freeze and Alpha

On Sunday 05 Feb 2012 14:12:48 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] Importing sahumada: Can you import http://gitorious.org/qserialdevice/qserialdevice (the 2.0 branch) into playground/QtSerialPort

On 09/02/2012 13:26, ext Denis Shienkov wrote: > Hi Marius. > > I have a few more questions (or offers): > > 1) Perhaps, instead of: >> ... >> and start pushing to refs/for/2.0 to the Gerrit repo. >> ... > done refs/for/master? Because for the main branch is gerrit master, > and not 2.0 (or am I mi

Re: [Development] Importing sahumada: Can you import http://gitorious.org/qserialdevice/qserialdevice (the 2.0 branch) into playground/QtSerialPort

Hi Marius. I have a few more questions (or offers): 1) Perhaps, instead of: >... > and start pushing to refs/for/2.0 to the Gerrit repo. >... done refs/for/master? Because for the main branch is gerrit master, and not 2.0 (or am I misunderstanding something?). 2) It may be worth in the current

Re: [Development] RFC: The Future of QDoc

On 09/02/2012 12:13, ext marius.storm-ol...@nokia.com wrote: > On 09/02/2012 10:33, ext Manuel Nickschas wrote: >> I'd be happy to see Qt use or at least support more standard >> solutions over homegrown ones. Since that failed for localization, >> maybe we can at least get it for documentation :)

Re: [Development] RFC: The Future of QDoc

> On 09/02/2012 10:33, ext Manuel Nickschas wrote: > > On Thursday 09 February 2012 15:36:09 ext Olivier Goffart wrote: I am working on QDoc part-time and we have been discussing some changes that we would like to implement to make qdoc more future proof. I have created a short list

Re: [Development] RFC: The Future of QDoc

On Thursday 09 February 2012 19:13:54 Storm-Olsen Marius (Nokia-MP/Austin) wrote: > > Or at least make QDoc be able to parse doxygen-style comments (which > > also means it should not ignore headers, as documenting public API > > in a header file is much more common at least outside Qt than doing

Re: [Development] RFC: The Future of QDoc

Hi, > > > I nice ability QDoc would have is to support other output formats > > > like XML or JSON, the old QDoc had this feature but it was deprecated > > > and not documented at all. > > > > > > The PySide documentation is generated using the XML output of qdoc3, > > > but the current version of

Re: [Development] RFC: The Future of QDoc

On 09/02/2012 10:33, ext Manuel Nickschas wrote: > On Thursday 09 February 2012 15:36:09 ext Olivier Goffart wrote: >>> I am working on QDoc part-time and we have been discussing some >>> changes that we would like to implement to make qdoc more future >>> proof. I have created a short list of the

Re: [Development] RFC: The Future of QDoc

On Thursday 09 February 2012 17:56:12 marius.storm-ol...@nokia.com wrote: > On 09/02/2012 10:16, ext Hugo Parente Lima wrote: > > On Thursday 09 February 2012 14:30:20 Matt Williams wrote: > >> On 9 February 2012 14:15, Keno Fischer wrote: > Implement a new C++ parser > >>> > >>> Any plans o

Re: [Development] RFC: The Future of QDoc

On 09/02/2012 10:16, ext Hugo Parente Lima wrote: > On Thursday 09 February 2012 14:30:20 Matt Williams wrote: >> On 9 February 2012 14:15, Keno Fischer wrote: Implement a new C++ parser >>> >>> Any plans on using Clang a parser? The wiki page mentioned Qt >>> Creator's AST, but it seems like

Re: [Development] Platform Look and feel

On Thursday, 9 de February de 2012 14.37.44, Thiago Lacerda wrote: > Hi, > > Is there a way, on Qt5, to get the platform look and feel, without the > dependency of QtWidgets using QStyle? > Or this is a feature that needs to be discussed about or done (for 5.1 > maybe?)? The platform look and feel

[Development] Platform Look and feel

Hi, Is there a way, on Qt5, to get the platform look and feel, without the dependency of QtWidgets using QStyle? Or this is a feature that needs to be discussed about or done (for 5.1 maybe?)? Cheers -- Thiago de Barros Lacerda OpenBossa - INdT ___ De

Re: [Development] RFC: The Future of QDoc

On Thursday 09 February 2012 14:30:20 Matt Williams wrote: > On 9 February 2012 14:15, Keno Fischer wrote: > >> Implement a new C++ parser > > > > Any plans on using Clang a parser? The wiki page mentioned Qt Creator's > > AST, but it seems like Qt Creator will be moving away from its own > > imp

Re: [Development] RFC: The Future of QDoc

On Thursday 09 February 2012 15:36:09 ext Olivier Goffart wrote: > > I am working on QDoc part-time and we have been discussing some changes > > that we would like to implement to make qdoc more future proof. I have > > created a short list of the things we would like to do: > > http://developer.q

Re: [Development] Removal of "Trolltech" usages inside Qt

On Thursday, 9 de February de 2012 16.04.07, lars.kn...@nokia.com wrote: > I'm uncertain about some identifiers in e.g. the qtdbus module, as I don't > know how this will affect interoperability between Qt 4 and Qt 5. I'd say we're ok to change, as the default names will change already due to QWid

Re: [Development] Removal of "Trolltech" usages inside Qt

On 2/9/12 4:56 PM, "ext Giuseppe D'Angelo" wrote: >One of the blockers of [1] ("Larger changes for Qt 5") is the clean up >of Trolltech strings/namespaces/etc. inside Qt, which is actually >tracked by several bug reports [2]. Btw, same thing is true for 'nokia' strings and namespaces. > >That's

[Development] Removal of "Trolltech" usages inside Qt

One of the blockers of [1] ("Larger changes for Qt 5") is the clean up of Trolltech strings/namespaces/etc. inside Qt, which is actually tracked by several bug reports [2]. That's fine, but was any consensus reached about what to change those strings to? "qt-project.org"? Should any logic for fall

Re: [Development] QMetaTypeId and QMetaTypeId2

> From: Olivier Goffart > On Thursday 09 February 2012 10:42:07 Thiago Macieira wrote: >>  On Thursday, 9 de February de 2012 10.07.16, Jedrzej Nowacki wrote: >>  > Hi, >>  > >>  >   Does anybody know why we have separation between QMetaTypeId and >>  > >>  > QMetaTypeId2 classes? >> >>  Becaus

Re: [Development] QMetaTypeId and QMetaTypeId2

On Thursday, 9 de February de 2012 12.39.54, Stephen Kelly wrote: > I always thought they were split so that Qt could add new built-in metatypes > without breaking user code. That's not why it was added. > Eg, if you merge them, any user code doing: > > Q_DECLARE_METATYPE(QModelIndex) Most types

Re: [Development] QMetaTypeId and QMetaTypeId2

On Thursday, 9 de February de 2012 14.11.17, André Somers wrote: > Not hindered by any knowledge of the internals of these classes: > Would it be possible to make such a statement a no-op then if the type > is already registered? If you can find a way to do that, great. The problem is we haven't

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

> From: "kai.koe...@nokia.com" >> -Original Message- >> From: Beck Wolfgang (Nokia-MP/Brisbane) >> I think this was a very good idea so I've tried it but I've run into one >> important >> problem. >> If I use this trick I have to call the overloaded function in QMessageLogger: >> e.g. >>

Re: [Development] RFC: The Future of QDoc

On Thursday 09 February 2012 14:00:53 casper.vandonde...@nokia.com wrote: > Hello, > > I am working on QDoc part-time and we have been discussing some changes that > we would like to implement to make qdoc more future proof. I have created a > short list of the things we would like to do: > http:/

Re: [Development] RFC: The Future of QDoc

On 9 February 2012 14:15, Keno Fischer wrote: >> Implement a new C++ parser > > Any plans on using Clang a parser? The wiki page mentioned Qt Creator's AST, > but it seems like Qt Creator will be moving away from its own implementation > in the future, so I think that might be something to conside

Re: [Development] RFC: The Future of QDoc

On 2/9/12 3:15 PM, "ext Keno Fischer" wrote: >> Implement a new C++ parser > >Any plans on using Clang a parser? The wiki page mentioned Qt Creator's >AST, >but it seems like Qt Creator will be moving away from its own >implementation >in the future, so I think that might be something to consider

Re: [Development] RFC: The Future of QDoc

> Implement a new C++ parser Any plans on using Clang a parser? The wiki page mentioned Qt Creator's AST, but it seems like Qt Creator will be moving away from its own implementation in the future, so I think that might be something to consider. Also, since the necessary work on Clang is being don

[Development] RFC: The Future of QDoc

Hello, I am working on QDoc part-time and we have been discussing some changes that we would like to implement to make qdoc more future proof. I have created a short list of the things we would like to do: http://developer.qt.nokia.com/wiki/Category:Tools::QDoc It comes down to: Implement a new

Re: [Development] QMetaTypeId and QMetaTypeId2

Op 9-2-2012 12:39, Stephen Kelly schreef: > Can I merge QMetaTypeId and QMetaTypeId2? I always thought they were split so that Qt could add new built-in metatypes without breaking user code. Eg, if you merge them, any user code doing: Q_DECLARE_METATYPE(QModelIndex) will no longer compile

Re: [Development] QMetaTypeId and QMetaTypeId2

On Thursday 09 February 2012 10:42:07 Thiago Macieira wrote: > On Thursday, 9 de February de 2012 10.07.16, Jedrzej Nowacki wrote: > > Hi, > > > > Does anybody know why we have separation between QMetaTypeId and > > > > QMetaTypeId2 classes? > > Because the original QMetaTypeId that existed in

Re: [Development] Changes to the Jira roles and workflow

It's easy to make a report on your personal dashboard to show issues reported on a given (set of) component(s). It means polling rather than email notification, but the email notifications have poor signal:noise ratio. > -Original Message- > From: development-bounces+shane.kearns=accentu

Re: [Development] Changes to the Jira roles and workflow

Storm-Olsen Marius wrote: > Thiago Macieira wrote: > > Agreed. As a Maintainer, I really don't want tons of tasks assigned > > to me and in idle state. It would make my life difficult because I > > can't find the tasks I want to work on. And it would get people > > screaming at me for not looking a

Re: [Development] Changes to the Jira roles and workflow

On 09/02/2012 05:41, Goddard Michael (Nokia-MP/Brisbane) wrote: >> Assigning new tasks "unassigned" will not notify the maintainer >> about issues in the modules that have come up, and the maintainer >> will not by notified when someone takes a task and starts working >> on it. > > Surely this is s

Re: [Development] Changes to the Jira roles and workflow

Howdy, >Assigning new tasks "unassigned" will not notify the maintainer about >issues in the modules that have come up, and the maintainer will not by >notified when someone takes a task and starts working on it. Surely this is something that JIRA could support? Watching a component or similar?

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

On 06/02/2012 03:04, ext Rick Stockton wrote: > 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 wi

Re: [Development] QMetaTypeId and QMetaTypeId2

On Thursday, February 09, 2012 10:07:16 Jedrzej Nowacki wrote: > Hi, > > Does anybody know why we have separation between QMetaTypeId and > QMetaTypeId2 classes? > > QMetaTypeId2 delegates all operations to QMetaTypeId by default and > qMetaTypeId() function is calling QMetaTypeId2. To make i

Re: [Development] Changes to the Jira roles and workflow

On 09/02/2012 04:33, ext Thiago Macieira wrote: > On Thursday, 9 de February de 2012 10.20.47, bradley.hug...@nokia.com > wrote: >>> There is call for discussion around default assignee – is it the >>> module maintainer? Which tasks are up for grabs if everything new >>> goes to the maintainer? >>

Re: [Development] Changes to the Jira roles and workflow

> > Default Assignee > > > > There is call for discussion around default assignee – is it the module > > maintainer? Which tasks are up for grabs if everything new goes to the > > maintainer? > > Unassigned should be the default. When someone picks up the task, they > should assign it to themselv

Re: [Development] Changes to the Jira roles and workflow

On Thursday, 9 de February de 2012 10.20.47, bradley.hug...@nokia.com wrote: > > There is call for discussion around default assignee – is it the module > > maintainer? Which tasks are up for grabs if everything new goes to the > > maintainer? > Unassigned should be the default. When someone picks

Re: [Development] Changes to the Jira roles and workflow

On 09 Feb, 2012, at 03:58 , ext marius.storm-ol...@nokia.com wrote: > Jira changes recommendations [snip] > Transfer ownership of issues > Early on there was a suggestion that a Module attribute was created to map > directly to maintainers. Later discussions implied that this is not necessary

Re: [Development] QMetaTypeId and QMetaTypeId2

On Thursday, 9 de February de 2012 10.07.16, Jedrzej Nowacki wrote: > Hi, > > Does anybody know why we have separation between QMetaTypeId and > QMetaTypeId2 classes? Because the original QMetaTypeId that existed in Qt 4.0 lacked one important feature, which Harald fixed in 4.2 or 4.3. Before h

[Development] QMetaTypeId and QMetaTypeId2

Hi, Does anybody know why we have separation between QMetaTypeId and QMetaTypeId2 classes? QMetaTypeId2 delegates all operations to QMetaTypeId by default and qMetaTypeId() function is calling QMetaTypeId2. To make it more complex Q_DECLARE_METATYPE is specializing QMetaTypeId but Q_DECLA

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

> -Original Message- > From: Beck Wolfgang (Nokia-MP/Brisbane) > Sent: Thursday, February 09, 2012 8:11 AM > To: Koehne Kai (Nokia-MP/Berlin); development@qt-project.org > Subject: RE: QLog ( Work on qDebug and friends) > > Hi Kai, Hi Wolfgang, > I think this was a very good idea so I'v