Re: [Development] Qt 5.4 Alpha released

2014-09-10 Thread haithem rahmani 
Hi,


Qt 5.4 Alpha release is finally out, see
 http://blog.qt.digia.com/blog/2014/09/08/qt-5-4-alpha-available/

 Alpha is source code delivery only. The plan forward is now to create a
 beta (including binary packages) during the next few weeks, see Qt 5.4
 schedule from http://qt-project.org/wiki/Qt-5.4-release

 Big thanks for everyone who were involved to make this happen!


Great Job!

I'm trying to build the qt-5.4.0 for embedded systems, it builds correctly
except the QWebEngine that is throwing the following

warning:

*Project WARNING: QtWebEngine is not maintained for this
platform/configuration and is therefore disabled.*


So I’m wondering whether the QtWebEngine will be functional or not for
embedded platforms in the qt-4.5.0, added to that will it
be working with DirectFB QPA/plugin?

*regards*
*Haithem.*
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Memory/Resource leaks in Windows multimedia backend (WMF)

2014-09-10 Thread Cornelius Hald 
Could someone help review this patch in Gerrit. I think it only needs
another +1

https://codereview.qt-project.org/#/c/94115/

Would be great to get that into Qt 5.3.2 which is due in about 6 days...

Thanks!
Conny


On Tue, 2014-08-12 at 09:33 +0200, Cornelius Hald wrote:
 Hi!
 
 Is there a Windows WMF wizard here, who could have a look at the
 following bug:
 
 https://bugreports.qt-project.org/browse/QTBUG-32481
 
 If was opened over a year ago and seems to be still valid on Qt 5.3.1.
 This bug makes is very difficult to have long-running multimedia
 applications. It would be great to get a fix in for Qt 5.3.2. And of
 course I'd help testing patches :)
 
 
 Thanks!
 Conny
 
 
 
 ___
 Development mailing list
 Development@qt-project.org
 http://lists.qt-project.org/mailman/listinfo/development


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] New documentation errors since Qt 5.3.1

2014-09-10 Thread Sze Howe Koh 
Hi all,

Using qdoc from Qt 5.4.0 Alpha1, I generated documentation from the
v5.4.0-alpha1 and v5.3.1 git tags. Then, I diff'ed the qdoc outputs
using QDocErrorTracker [1].

Below is a list of errors that are new in Qt 5.4.0 Alpha1. Could those with
knowledge of the relevant areas please fix them if time permits?


= qtbase.git =
src/corelib/global/qnamespace.qdoc:1252
warning: Undocumented enum item 'Key_Find' in Qt::Key
src/corelib/global/qnamespace.qdoc:1252
warning: Undocumented enum item 'Key_Open' in Qt::Key
src/corelib/global/qnamespace.qdoc:1252
warning: Undocumented enum item 'Key_MicVolumeUp' in Qt::Key
src/corelib/global/qnamespace.qdoc:1252
warning: Undocumented enum item 'Key_Redo' in Qt::Key
src/corelib/global/qnamespace.qdoc:1252
warning: Undocumented enum item 'Key_Undo' in Qt::Key
src/corelib/global/qnamespace.qdoc:1252
warning: Undocumented enum item 'Key_New' in Qt::Key
src/corelib/global/qnamespace.qdoc:1252
warning: Undocumented enum item 'Key_MicVolumeDown' in Qt::Key
src/corelib/global/qglobal.cpp:1106
warning: No such enum item 'MV_IOS_8_0' in QSysInfo::MacVersion
src/corelib/kernel/qmath.qdoc:206
warning: No such parameter 'radians' in qNextPowerOfTwo()
src/corelib/kernel/qmath.qdoc:206
warning: No such parameter 'value' in qRadiansToDegrees()


= qtmacextras.git =
src/macextras/qmactoolbar.mm:66
warning: Can't link to 'QWindow::attachToWindow'
examples/macextras/embeddedqwindow/doc/src/qtmacextras-example-embeddedqwindow.qdoc:28
warning: Can't link to 'Qt for OS X'
src/macextras/doc/src/qtmacextras-examples.qdoc:41
warning: Can't link to 'Qt for OS X'
examples/macextras/macfunctions/doc/src/qtmacextras-example-macfunctions.qdoc:28
warning: Can't link to 'Qt for OS X'
examples/macextras/macpasteboardmime/doc/src/qtmacextras-example-macpasteboardmime.qdoc:28
warning: Can't link to 'Qt for OS X'


= qtdeclarative.git =
src/qml/doc/src/qmlfunctions.qdoc:159
warning: Cannot find 'QQmlEgine' in '\relates'
src/qml/doc/src/qmlfunctions.qdoc:181
warning: Cannot find 'QQmlEgine' in '\relates'
src/imports/statemachine/finalstate.cpp:73
warning: Cannot find file to quote from:
'qml/statemachine/finalstate.qml'
src/imports/statemachine/finalstate.cpp:73
warning: Unable to parse QML snippet: Expected token `numeric
literal' at line 1, column 1
src/imports/statemachine/finalstate.cpp:73
warning: Unexpected '\snippet (//! [document])'
src/imports/statemachine/signaltransition.cpp:227
warning: Cannot find file to quote from:
'qml/statemachine/signaltransition.qml'
src/imports/statemachine/signaltransition.cpp:227
warning: Unable to parse QML snippet: Expected token `numeric
literal' at line 1, column 1
src/imports/statemachine/signaltransition.cpp:227
warning: Unexpected '\snippet (//! [document])'
src/imports/statemachine/signaltransition.cpp:239
warning: Cannot find file to quote from:
'qml/statemachine/signaltransitionsignal.qml'
src/imports/statemachine/signaltransition.cpp:239
warning: Unable to parse QML snippet: Expected token `numeric
literal' at line 1, column 1
src/imports/statemachine/signaltransition.cpp:239
warning: Unexpected '\snippet (//! [document])'
src/imports/statemachine/signaltransition.cpp:253
warning: Cannot find file to quote from:
'qml/statemachine/guardcondition.qml'
src/imports/statemachine/signaltransition.cpp:253
warning: Unable to parse QML snippet: Expected token `numeric
literal' at line 1, column 1
src/imports/statemachine/signaltransition.cpp:253
warning: Unexpected '\snippet (//! [document])'
src/imports/statemachine/statebase.cpp:136
warning: Cannot find file to quote from:
'qml/statemachine/basicstate.qml'
src/imports/statemachine/statebase.cpp:136
warning: Unable to parse QML snippet: Expected token `numeric
literal' at line 1, column 1
src/imports/statemachine/statebase.cpp:136
warning: Unexpected '\snippet (//! [document])'
src/imports/statemachine/statebase.cpp:199
warning: Cannot find file to quote from:
'qml/statemachine/historystate.qml'
src/imports/statemachine/statebase.cpp:199
warning: Unable to parse QML snippet: Expected token `numeric
literal' at line 1, column 1
src/imports/statemachine/statebase.cpp:199
warning: Unexpected '\snippet (//! [document])'
src/imports/statemachine/statemachine.cpp:117
warning: Cannot find file to quote from:
'qml/statemachine/simplestatemachine.qml'
src/imports/statemachine/statemachine.cpp:117
warning: Unable to parse QML snippet: Expected token `numeric
literal' at line 1, column 1
src/imports/statemachine/statemachine.cpp:117
warning: Unexpected '\snippet (//! [document])'
src/imports/statemachine/timeouttransition.cpp:96
warning: Cannot find file to quote from:
'qml/statemachine/timeouttransition.qml'
src/imports/statemachine/timeouttransition.cpp:96
warning: Unable to parse QML snippet: Expected token `numeric
literal' at line 1,

Re: [Development] QTBUG-35892. QML XMLHttpRequest does not support the OPTIONS method.

2014-09-10 Thread Thiago Macieira 
On Tuesday 09 September 2014 18:24:58 Валерий Котов wrote:
 I realize that we had this discussion before. But I have to ask. =)
 Does not it make sense to add method and type in Operations enum for
 options in case we need some special treatment for OPTIONS verb?

Only if we have a method for it and we're not adding one. If it's just 
sendCustomVerb, then we don't need an enum entry.

By the way, do you know of who would need OPTIONS *? What's the use-case, who 
would use it and how do they do it today?
-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.4 Alpha released

2014-09-10 Thread Thiago Macieira 
On Wednesday 10 September 2014 10:03:48 haithem rahmani wrote:
 So I’m wondering whether the QtWebEngine will be functional or not for
 embedded platforms in the qt-4.5.0, added to that will it
 be working with DirectFB QPA/plugin?

It's unlikely it will work with DirectFB for now.
-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] QTBUG-35892. QML XMLHttpRequest does not support the OPTIONS method.

2014-09-10 Thread Richard Moore 
On 10 September 2014 21:15, Thiago Macieira thiago.macie...@intel.com
wrote:

 On Tuesday 09 September 2014 18:24:58 Валерий Котов wrote:
  I realize that we had this discussion before. But I have to ask. =)
  Does not it make sense to add method and type in Operations enum for
  options in case we need some special treatment for OPTIONS verb?

 Only if we have a method for it and we're not adding one. If it's just
 sendCustomVerb, then we don't need an enum entry.

 By the way, do you know of who would need OPTIONS *? What's the use-case,
 who
 would use it and how do they do it today?


Given the previous discussions referenced from the working groups for
xmlhttprequest I think it's pretty clear that we can forget about OPTIONS
*. Just using a custom verb and implementing it in the xmlhttprequest
implementation of qml seems like the way to go.

Cheers

Rich.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development