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

Hi all. Well, what with the Code Review? Who controls it? I prepared the first review here: http://codereview.qt-project.org/16042 1) Interested in the question about the type of macro QT_BEGIN_NAMESPACE_XXX, QT_END_NAMESPACE_XXX, etc. What a way to more correct: leave these macros (as in the e

Re: [Development] Schedule for Qt 4.8.1

On 13.2.2012 18.23, "Wolfgang Baron" wrote: >Hi Turunen Tuukka, > >could there please be an official VS 2010 64-bit binary release for >Microsoft Windows for Qt 4.8.1 onwards? In order to release such version, it should be included into the public CI system. I do not think it is there currently

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

Hi all. Yes, most likely LGPL + commercial. So, there is no reason to worry. Best regards, Denis 14.02.2012, 04:08, marius.storm-ol...@nokia.com: > Given that the QSerialDevice developers have accepted the CLA for the project > effective from start of the project, the project is now open for li

Re: [Development] Schedule for Qt 4.8.1

On 13.2.2012 18.32, "Thiago Macieira" wrote: >On segunda-feira, 13 de fevereiro de 2012 12.28.06, Turunen Tuukka wrote: >> Hi All, >> >> We would like to release next version of Qt Commercial 4.8 around >>mid-March. >> >> It would be really great if we can again sync the LGPL and Commercial >

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

Given that the QSerialDevice developers have accepted the CLA for the project effective from start of the project, the project is now open for licencing both under LGPL and commercial license; just like any other module in Qt. AFAIK, though IANAL. -- Sent from my Nokia N9 On 2/13/12 16:56 ext

Re: [Development] new QtNetwork maintainer

> Shane Kearns has however stepped up and is willing to take over the > position. I'm really happy that Shane is willing to take this job. He has > a lot of experience with QtNetwork, and has been heavily involved with Qt > development (actively working on the Symbian port) for quite a few years. >

[Development] Something is wrong in QFontEngineFT::loadGlyph

Hi, While using Qt's elidedText function http://developer.qt.nokia.com/doc/qt-4.8/qfontmetricsf.html#elidedText i noticed the function was dog slow. For just 1000 entries (each 250 chars) eliding them to 200px took about 190ms on windows and 100ms on linux. Using that for drawing is noticeable slo

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

Hi Denis, I have a question about the license for QSerialDevice. In gitorious it appears as GPLv3. I think it could be interesting to have a more permisive licensing option such as LGPL or BSD. This will allow to push forward this library compared with others such as QextSerialPort with not es

Re: [Development] new QtNetwork maintainer

On 2/13/12 4:17 PM, "ext Thiago Macieira" wrote: >On segunda-feira, 13 de fevereiro de 2012 14.05.36, marius.storm- >ol...@nokia.com wrote: >> On 02/13/2012 07:17 AM, ext lars.kn...@nokia.com wrote: >> > Shane Kearns has however stepped up and is willing to take over the >> > position. I'm reall

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

On 02/13/2012 01:27 PM, ext shane.kea...@accenture.com wrote: Maybe you're looking at a "triage" role, if the role is prioritizing and assigning of tasks among a team that is mostly funded by one company. Another role we need in JIRA is "contributor". This is

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

Maybe you're looking at a "triage" role, if the role is prioritizing and assigning of tasks among a team that is mostly funded by one company. Another role we need in JIRA is "contributor". This is somebody who is not a reviewer, but can still be assigned tasks & transition their assigned tasks

Re: [Development] Default enabling inbound flow control on sockets

On sexta-feira, 10 de fevereiro de 2012 19.25.04, shane.kea...@accenture.com wrote: > We could change the default read buffer size from 0 (unbounded) to a > sensible default value e.g. 64k (to be benchmarked) Applications wanting > the old behaviour could explicitly call setReadBufferSize(0) Applic

Re: [Development] Separation of QtQuick 1 from QtDeclarative repo

On 2/13/12 5:52 PM, "ext Stephen Kelly" wrote: >On Friday, February 03, 2012 12:17:35 lars.kn...@nokia.com wrote: >> >Hi, >> > >> >It seems like this change broke qt/qttools, can you confirm this >>please ? >> >> I'd assume qttools doesn't include the qtquick1 repo as a dependency. > >It need

Re: [Development] Default enabling inbound flow control on sockets

On 02/13/2012 12:33 PM, ext marius.storm-ol...@nokia.com wrote: > ^shrug^ but I rather not have applications start failing at random due > to a failure to have a new limit. ..handle a new limit. -- .marius ___ Development mailing list Development@qt-pr

Re: [Development] Default enabling inbound flow control on sockets

On Monday 13 February 2012 18:33:51 marius.storm-ol...@nokia.com wrote: > On 02/13/2012 08:10 AM, ext shane.kea...@accenture.com wrote: > >> Not sure. Is it a big problem? Or is it better to just continue as > >> is, and let the applications that do have a problem set it to > >> something reasonabl

Re: [Development] Default enabling inbound flow control on sockets

On 02/13/2012 08:10 AM, ext shane.kea...@accenture.com wrote: >> Not sure. Is it a big problem? Or is it better to just continue as >> is, and let the applications that do have a problem set it to >> something reasonable to them instead? >> >> I'd probably suggest that we instead improve the output

Re: [Development] RFC: The Future of QDoc

On Monday, February 13, 2012 09:04:22 casper.vandonde...@nokia.com wrote: > Whatever is chosen (updating qdoc, or changing to Doxygen): The task is > not small, and therefore it would be nice if there would be more > contributors than just me and Martin Smith. Maybe it would be a good idea > to hav

Re: [Development] Separation of QtQuick 1 from QtDeclarative repo

On Friday, February 03, 2012 12:17:35 lars.kn...@nokia.com wrote: > >Hi, > > > >It seems like this change broke qt/qttools, can you confirm this please ? > > I'd assume qttools doesn't include the qtquick1 repo as a dependency. It needs declarative in Qt4 because lupdate uses it to extract transl

Re: [Development] Schedule for Qt 4.8.1

On segunda-feira, 13 de fevereiro de 2012 12.28.06, Turunen Tuukka wrote: > Hi All, > > We would like to release next version of Qt Commercial 4.8 around mid-March. > > It would be really great if we can again sync the LGPL and Commercial > releases both in timing and content to the extent possible

Re: [Development] Schedule for Qt 4.8.1

Hi Turunen Tuukka, could there please be an official VS 2010 64-bit binary release for Microsoft Windows for Qt 4.8.1 onwards? Thanks a lot & kind regards, Wolfgang Baron ___ Development mailing list Development@qt-project.org http://lists.qt-project

[Development] how to enable magnifier when adjust selections in TextArea?

Hi: I have a problem can not been sloved by myself,I use meego component's TextArea in my project, the Magnifier can be activiated when placeandhold some time,but in some other applications like Calendar and facebookqml,i found the magnifier can be opened when adjust selection,how? Any hel

Re: [Development] new QtNetwork maintainer

On segunda-feira, 13 de fevereiro de 2012 14.05.36, marius.storm- ol...@nokia.com wrote: > On 02/13/2012 07:17 AM, ext lars.kn...@nokia.com wrote: > > Shane Kearns has however stepped up and is willing to take over the > > position. I'm really happy that Shane is willing to take this job. He > > ha

Re: [Development] Default enabling inbound flow control on sockets

> > Not sure. Is it a big problem? Or is it better to just continue as is, > and let the applications that do have a problem set it to something > reasonable to them instead? > > I'd probably suggest that we instead improve the output on that worst > case failure to help devs fix the problems in th

Re: [Development] new QtNetwork maintainer

On 02/13/2012 07:17 AM, ext lars.kn...@nokia.com wrote: > Shane Kearns has however stepped up and is willing to take over the > position. I'm really happy that Shane is willing to take this job. He > has a lot of experience with QtNetwork, and has been heavily involved > with Qt development (active

Re: [Development] Default enabling inbound flow control on sockets

You've correctly understood the problem, but the scale is less bad (takes a couple of minutes to exhaust 2GB limit of a 32 bit process using a loopback connection) Changing the default would mean behavior is the same as if you called setReadBufferSize(65536) in the application. Currently the de

[Development] new QtNetwork maintainer

Hi everybody, as some of you might know, our current maintainer for QtNetwork, Peter Hartmann, has left Nokia to start in a different job. Unfortunately that new job doesn't leave him with enough time to continue as the maintainer of QtNetwork, so he stepped down as the maintainer of QtNetwork. S

[Development] Schedule for Qt 4.8.1

Hi All, We would like to release next version of Qt Commercial 4.8 around mid-March. It would be really great if we can again sync the LGPL and Commercial releases both in timing and content to the extent possible. If we agree that mid-March is a good target time for the next patch release, we

Re: [Development] Default enabling inbound flow control on sockets

On Friday 10 February 2012 19:25:04 shane.kea...@accenture.com wrote: > The same change would be required at the QNetworkAccessManager level, as > there is no point applying flow control at the socket and having unbounded > memory allocations in the QNetworkReply. I think it might make sense to im

Re: [Development] RFC: The Future of QDoc

On 2/13/12 1:00 AM, "ext craig.sc...@csiro.au" wrote: > >On 10/02/2012, at 5:13 AM, >mailto:marius.storm-ol...@nokia.com>> >mailto:marius.storm-ol...@nokia.com>> wrote: > >I think there are a few issues here: > >1) Only Dimitri touches Doxygen code, and it doesn't look like >contributions go in