Re: [Development] Deprecating modules with 5.5

2015-03-17 Thread Bo Thorsen
Den 17-03-2015 kl. 23:45 skrev Thiago Macieira: > On Tuesday 17 March 2015 17:14:38 Jan Kundrát wrote: >> On Tuesday, 3 February 2015 08:33:46 CET, Knoll Lars wrote: >>> * Qt WebKit >> While I understand the reasons on why you want to remove this one, I think >> that this goes against the promise o

[Development] Adding .mtl files into qt3d+qt5.5 based applcation

2015-03-17 Thread Arjun Das
Hi, When i export "blender" files into .obj files, i get .mtl supporting files as well. However, I am able to add .obj files but am not sure how to add the .mtl file information. Additionally, are there any documentation for qt3d 2.0 (5.5 branch) ? I am trying to understand the APIs from the exam

[Development] Debug category for sql drivers

2015-03-17 Thread Guido Seifert
Hi, could have have an sql category for the sql drivers? Currently the postgres driver drives me crazy. :-D I get constantly a warning: Unable to free statement: ERROR: prepared statement "qpsqlpstmt_23" does not exist Does not look like I can do much to remove the cause of this warning

Re: [Development] Deprecating modules with 5.5

2015-03-17 Thread Thiago Macieira
On Tuesday 17 March 2015 17:14:38 Jan Kundrát wrote: > On Tuesday, 3 February 2015 08:33:46 CET, Knoll Lars wrote: > > * Qt WebKit > > While I understand the reasons on why you want to remove this one, I think > that this goes against the promise of compatibility at [1]: > > "Qt essentials define

Re: [Development] Two source incompatibilities in Qt 5.5 with Clang

2015-03-17 Thread Thiago Macieira
On Tuesday 17 March 2015 09:40:08 Olivier Goffart wrote: > > Opinions for or against? > > I think it's a good idea, just like we have QT_USE_QSTRINGBUILDER, we could > have QT_CHECK_ASSERT or something like that. Ok, I'll prepare a patch. -- Thiago Macieira - thiago.macieira (AT) intel.com So

Re: [Development] Deprecating modules with 5.5

2015-03-17 Thread Bernhard
Some of our applications are relying on Qt Script and Qt Webkit. So I just had a look at the replacements (Qt Webengine and Qt QML). The documentation says "... WebEngine ... doesn't give direct access to the network stack and the HTML document through C++ APIs". Does this mean there is no way to

Re: [Development] Deprecating modules with 5.5

2015-03-17 Thread Jan Kundrát
On Tuesday, 3 February 2015 08:33:46 CET, Knoll Lars wrote: > * Qt WebKit While I understand the reasons on why you want to remove this one, I think that this goes against the promise of compatibility at [1]: "Qt essentials define the foundation of Qt on all platforms. They are available on all

Re: [Development] Deprecating modules with 5.5

2015-03-17 Thread Corentin Jabot
Regarding QJSEngine, some things are unclear to me. Let's say I have a QObject-derived class. how do I create an instance of that class from a script ? c++ : class Foo : public QObject { Q_OBJECT }; js : var foo = new Foo() How do I call a c++ function from a js script ? That use case seem

[Development] Qt 5.5 Alpha released

2015-03-17 Thread Heikkinen Jani
Hi all! Qt 5.5 Alpha release is out, see http://blog.qt.io/blog/2015/03/17/qt-5-5-alpha-available/ ‎ As earlier, Alpha is source code delivery only. The plan forward is now to create a beta (including binary packages) during the next few weeks. Big thanks for everyone who were involved to make

Re: [Development] Qt mailing list migration

2015-03-17 Thread Marc Mutz
On Monday 16 March 2015 18:29:58 Oswald Buddenhagen wrote: > On Mon, Mar 16, 2015 at 05:42:40PM +0100, Marc Mutz wrote: > > On Monday 16 March 2015 13:57:57 Järvenpää Petri wrote: > > > The change should be invisible to the normal user, > > > > Are you going to break List-Id again? > > that seems

Re: [Development] Two source incompatibilities in Qt 5.5 with Clang

2015-03-17 Thread Olivier Goffart
On Monday 16 March 2015 14:54:53 Thiago Macieira wrote: > On Monday 16 March 2015 21:05:41 Stephen Kelly wrote: > > Thiago Macieira wrote: > > > Because we want to benefit from the new code and remove the unnecessary > > > #ifndef and Q_UNUSED. If we don't change the current macro, then we > > > de