Re: [Development] Compiler warnings

Leaving out the parameter name is not a problem. A better approach is marking the parameter as unused. But, the potential problem lays in breaking semantic compatibility. A very nice example is: http://en.m.wikipedia.org/wiki/Cluster_(spacecraft) Interfaces were compatible, semantics were not. Th

Re: [Development] Platform maintainers

+1 from my side. Both have been very active on the port, and we've seen with Qt Network that a shared maintainership can work well. Cheers, Lars On 16/10/14 13:44, "Vladimir Minenko" wrote: >In addition to the below, I would suggest adding Rafael Roquetto as a >second maintainer for the QNX pla

Re: [Development] Qt3D on iOS

On 16. okt. 2014 18:49, Sean Harmer wrote: > > > We've not started testing Qt3D 2.0 on iOS yet but we will do shortly. If > you wish to help out with this that would be very much appreciated. I > don't know if James has made any attempt to build Qt3D on iOS yet or not. > Definitely! We don't have

Re: [Development] Compiler warnings

Kurt Pattyn wrote: > On second thought, I think this is a very bad example. Even while you keep > binary compatibility, you break semantics here. This is typically a case > where one should break binary compatibility. > I am sure (or at least I hope so) that Qt does not allow these kind of > things

Re: [Development] Compiler warnings

But if lack of a parameter name means unused (by choice) parameter, then compilers shouldn't warn that it is an unused parameter. martin From: development-bounces+martin.smith=theqtcompany@qt-project.org on behalf of Kevin Kofler Sent: Thursday, Oc

Re: [Development] Branching scheme & bugs

On 14/10/2014 10:39 pm, Thiago Macieira wrote: > On Tuesday 14 October 2014 21:14:10 Ben McGinnes wrote: >> I can't speak for Kurt, but mine is just a couple of lines in one >> file, though it might be better served by a script to detect the >> correct attributes for that file and apply them during

Re: [Development] Compiler warnings

Smith Martin wrote: > But maintaining binary compatibility is now a necessary facet of software > engineering, so maybe it is time for the C++ standard to support it. A > keyword could be added to the parameter declaration, "compatibility" or > "placeholder" for example, could precede a parameter d

Re: [Development] Qt3D on iOS

Hi, On 16/10/2014 17:37, Svenn-Arne Dragly wrote: > Hi, > > Does the current development version of Qt3D 1.0 (master) or Qt3D 2.0 > (wip/newapi) build on iOS? We tried building both versions, but we get > the following error with Qt3D 1.0: > > No rule to make target > `/repos/qt3d/build-qt3d-wi

[Development] Qt3D on iOS

Hi, Does the current development version of Qt3D 1.0 (master) or Qt3D 2.0 (wip/newapi) build on iOS? We tried building both versions, but we get the following error with Qt3D 1.0: No rule to make target `/repos/qt3d/build-qt3d-wip-Release/lib/libQt53D.a', needed by `../../lib/libQt53DQuick.dy

Re: [Development] Qt3D roadmap

Hi, On 16/10/2014 11:56, Ayberk Özgür wrote: > Dear Qt Developers, > > We're the Computer Human Interaction in Learning and Instruction > laboratory at Ecole Polytechnique Federale de Lausanne. We're beginning > to use Qt as a framework for cross-platform tangible interfaces, > augmented reality a

Re: [Development] Platform maintainers

In addition to the below, I would suggest adding Rafael Roquetto as a second maintainer for the QNX platform. Rafael was tightly involved in the development of Qt5 for QNX and is working on several customer projects using Qt on QNX. — Vladimir On 26.09.14 14:04, "Vladimir Minenko" wrote: >On 25

[Development] QtRemoteObjects (was Replicant)

Qt Devs, I know I've been silent for a while after the discussing Replicant and QQSM at the Qt Contributors Summit. If you aren't aware, QQSM was renamed to DSM (Declarative State Machine) and has been incorporated into QML. It is already merged and will be released with Qt 5.4. The 2nd proj

[Development] Qt3D roadmap

Dear Qt Developers, We're the Computer Human Interaction in Learning and Instruction laboratory at Ecole Polytechnique Federale de Lausanne. We're beginning to use Qt as a framework for cross-platform tangible interfaces, augmented reality and robotics applications. We'll be using stock + cust

Re: [Development] QConfig update.

Thiago Macieira schreef op 16-10-2014 09:17: > On Thursday 16 October 2014 08:51:52 André Somers wrote: >> Exactly the same way moc already parses header files now? My idea was to >> explore if it were possible to build on what moc already can do. You >> might have noticed that this idea looks exac

Re: [Development] QConfig update.

Am 14.10.2014 um 18:44 schrieb Tomaz Canabrava: > On Tue, Oct 14, 2014 at 1:35 PM, Milian Wolff > wrote: > >> On Tuesday 14 October 2014 13:22:51 Tomaz Canabrava wrote: >>> QConfig and QConfigGroup *does not* support setting a default value >>> on the getter, I kno

Re: [Development] Help needed to test Ministro 10.0

Hello, I did a minor update to Ministro and I upload a new version to: http://files.kde.org/necessitas/installer/test/Ministro%20II%20v10.1.apk I just bumped the Ministro API version[1]. The new Ministro API version is required by any Qt 5.4 application in order to make sure that all the needed

Re: [Development] QConfig update.

On Thursday 16 October 2014 08:51:52 André Somers wrote: > Exactly the same way moc already parses header files now? My idea was to > explore if it were possible to build on what moc already can do. You > might have noticed that this idea looks exactly like how you create > Q_PROPERTY declarations.