[Development] Codifying the .qml License Header Exemption

2013-09-20 Thread Alan Alpert
A while ago it came up that the rules for license headers in QML files isn't clearly defined. Here's my suggestion for how to define it, and if the project likes the idea we can get a legal check and then fix up the infrastructure to follow (sanity bot and license-check test). Current rule is roug

Re: [Development] QIODevice::peek is not virtual. Workaround proposed

2013-09-20 Thread André Pönitz
On Fri, Sep 20, 2013 at 01:31:30PM +0200, Stephen Kelly wrote: > > Hello, > > In grantlee there is a example called htmlapps, which creates a QNetworkReply > subclass to render a template. > > > https://gitorious.org/grantlee/grantlee/source/master:examples/htmlapps/templatereply.cpp > 24d711

[Development] potential bug with qml context properties

2013-09-20 Thread Matt Broadstone
Hi, I'm running into a strange error related to context properties in qml. Basically, I'm trying to expose a QQmlPropertyMap into the context of my QQmlApplicationEngine, and within the qml set up a "recursive" binding so that changes to that map from C++ are expressed in qml, and vica versa. This

Re: [Development] Heads up: QtAlgorithms to be deprecated in 5.2

2013-09-20 Thread Thiago Macieira
On sexta-feira, 20 de setembro de 2013 10:52:40, André Somers wrote: > Reading through that discussion, I wonder why the choice made has been > to depricate QtAlgorithms, while in that thread it was suggested to > depricate QT_NO_STL itself. Personally, I'm sad to see them go, but I > understand

[Development] QIODevice::peek is not virtual. Workaround proposed

2013-09-20 Thread Stephen Kelly
Hello, In grantlee there is a example called htmlapps, which creates a QNetworkReply subclass to render a template. https://gitorious.org/grantlee/grantlee/source/master:examples/htmlapps/templatereply.cpp 24d711fc3ac88565a59c45fb6fb2dd1e75a7a9f2 This works with Qt 4.7, but the QWebView displ

Re: [Development] Qt Category Logging Patch - please review

2013-09-20 Thread Koehne Kai
> -Original Message- > From: Koehne Kai > Sent: Tuesday, September 03, 2013 3:07 PM > To: Koehne Kai; Blasche Alexander; Robin Burchell; development@qt- > project.org > Cc: Poenitz Andre > Subject: Qt Category Logging Patch - please review > > Hi, > > This is just a heads up that https:/

Re: [Development] [QtSerialPort] Leaving from the project

2013-09-20 Thread Simon Hausmann
On Friday 20. September 2013 12.42.28 Denis Shienkov wrote: [...] > Thus, I changed the mind and made the decision to remain and continue to > keep the project. So - do not worry! :) Yay, welcome back :) Simon ___ Development mailing list Development@q

Re: [Development] Heads up: QtAlgorithms to be deprecated in 5.2

2013-09-20 Thread André Somers
Op 13-9-2013 22:16, Giuseppe D'Angelo schreef: > Hello, > > https://codereview.qt-project.org/#change,43441 (currently waiting for > a review) is going to mark most of the QtAlgorithms functions as > deprecated. > > The decision about this has already happened some time ago: > http://www.mail-arc

Re: [Development] [QtSerialPort] Leaving from the project

2013-09-20 Thread Denis Shienkov
Hi all, I feel a bit sorry about the email I sent out the other day. I was a bit overheated, and I think this email content was a bit of exaggeration for the real problems at hand. It is true that there were some pending changes for a while (4-5 out of the 200-300 or more?), but rethinking it with

Re: [Development] Heads up: QtAlgorithms to be deprecated in 5.2

2013-09-20 Thread Giuseppe D'Angelo
Howdy, Il 13/09/2013 22:16, Giuseppe D'Angelo ha scritto: https://codereview.qt-project.org/#change,43441 (currently waiting for a review) And still waiting. Can anyone please go ahead and push some button? Thanks, -- Join us at Qt Developer Days 2013! - https://devdays.kdab.com Giuseppe D'A

Re: [Development] [QtSerialPort] Leaving from the project

2013-09-20 Thread Saether Jan-Arve
Hello Denis. That was sad to hear. If he is always busy, (I know this might be subjective from your POV) then I'm not sure if it was the right decision for you to leave. If he's always busy, who will drive the project forward now? Did you discuss this with other contributors of the project? If o