Re: [Development] New Qt 5.7.0 RC snapshot available

2016-05-18 Thread Ralf Nolden
Am Mittwoch, 18. Mai 2016, 15:04:24 schrieb Kai Koehne:
> It's the first time I hear someone asking for a tarball for QtQuick1. 
> 
> I see that people are still stuck with WebKit for some use cases, because
> the 
 architecture, OS requirements and API of WebEngine differs. For
> QtQuick, it's IMO really painless to update. Also, last time I checked,
> there were very little  Linux packages left that still require Qt Quick 1.
> So what's your use case?

https://www.freshports.org/x11-toolkits/qt5-declarative/

(qt5-declarative is a misleading name for qtquick1 as the qt4 version was 
named declarative, however it is the qtquick1 sources packaged).

We will have to check if those ports that depend on qtquick1 do really need 
them (where qt5 (metaport) and qtcreator can go obviously anyway) or if we can 
find another solution.


> 
> Regards
> 
> Kai
> 

-- 
Kind regards,

Ralf Nolden

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


Re: [Development] New Qt 5.7.0 RC snapshot available

2016-05-18 Thread Kai Koehne
> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Ralf Nolden
> [...]
> I suggest having a look at https://bugreports.qt.io/browse/QTBUG-49883
> and do some consideration how to handle those issues. If modules are
> deprecated but should still work for backwards compatibility, then there
> should be no change at all that prevents that.

There's a difference between deprecated and unsupported.

Deprecated means we don't advice you to start _new_ projects with it,
Otherwise it has the same promises as any other module.

Unsupported means it's not part of Qt anymore.

> Otherwise that module is
> "somewhat supported even if we don't like to" - which creates a really
> confusing situation for packagers and porters, but (at least I) can live with
> that as long as we get updated (tagged) release tarballs :)

QtQuick1 and QtWebKit are _not_ supported anymore since Qt 5.6. 

What we have said is that we will provide QtWebKit source packages as courtesy 
on a  best-effort basis. That is, also the QtWebKit source package under

http://download.qt.io/community_releases/5.6/5.6.0/

is not part of Qt anymore, and not supported. Use it at your own risk.
There's also no promise we can continue providing these.

> So, an updated tarball for qtquick1 for 5.6 would be really much appreciated
> (so that it works with 5.6.x and 5.7.x)

It's the first time I hear someone asking for a tarball for QtQuick1. 

I see that people are still stuck with WebKit for some use cases, because the 
architecture, OS requirements and API of WebEngine differs. For QtQuick, 
it's IMO really painless to update. Also, last time I checked, there were very 
little  Linux packages left that still require Qt Quick 1. So what's your use
case?

Regards

Kai

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


Re: [Development] New Qt 5.7.0 RC snapshot available

2016-05-18 Thread Ralf Nolden
Am Mittwoch, 18. Mai 2016, 04:44:45 schrieb Jani Heikkinen:

Hi, thanks for the snapshot that allows us some build tests before any 
releases.

I just hit a compile error on the deprecated qtquick1 module, latest src 
tarball is for 5.5.1. For qtwebkit, there's the community releases subdir:
http://download.qt.io/community_releases/5.6/5.6.0/
(which does work)

I suggest having a look at https://bugreports.qt.io/browse/QTBUG-49883
and do some consideration how to handle those issues. If modules are 
deprecated but should still work for backwards compatibility, then there 
should be no change at all that prevents that. Otherwise that module is 
"somewhat supported even if we don't like to" - which creates a really 
confusing situation for packagers and porters, but (at least I) can live with 
that as long as we get updated (tagged) release tarballs :)

So, an updated tarball for qtquick1 for 5.6 would be really much appreciated 
(so that it works with 5.6.x and 5.7.x)

Thanks :)


> Hi all,
> 
> 
> New Qt 5.7.0 RC snapshot available
> 
> 
> Windows: http://download.qt.io/snapshots/qt/5.7/5.7.0-rc/456/
> 
> Linux: http://download.qt.io/snapshots/qt/5.7/5.7.0-rc/424/
> 
> Mac: http://download.qt.io/snapshots/qt/5.7/5.7.0-rc/354/
> 
> src: http://download.qt.io/snapshots/qt/5.7/5.7.0-rc/latest_src/submodules/
> 
>  />
> 
> 

-- 
Kind regards,

Ralf Nolden

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


[Development] New Qt 5.7.0 RC snapshot available

2016-05-17 Thread Jani Heikkinen

Hi all,


New Qt 5.7.0 RC snapshot available


Windows: http://download.qt.io/snapshots/qt/5.7/5.7.0-rc/456/

Linux: http://download.qt.io/snapshots/qt/5.7/5.7.0-rc/424/

Mac: http://download.qt.io/snapshots/qt/5.7/5.7.0-rc/354/

src: http://download.qt.io/snapshots/qt/5.7/5.7.0-rc/latest_src/submodules/




Packages are RTA sanity checked and everything seems to be pretty much Ok. So 
please test the packages and make sure all Qt 5.7.0 blockers are visible in 
https://bugreports.qt.io/issues/?filter=17619. We are planning to release Qt 
5.7.0 rc 1st of June and so on all blockers must be fixed latest 23rd May. Then 
we have enough time to integrate changes in qt5.qit, create and test the 
packages before rc.


Known issues in the packages:

- WebEngine and WebView missing from 32 bit windows packages

- Serialbus missing form Windows Android packages

- VKB and qtquickcontrols2 example paths are wrong


Last qt5.git integration in these packages:

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

Patch Set 26: Code-Review+2 Sanity-Review+1

qt/qt3d 
7c9331e953700e4c35e4bd3d51ebc49e4c3b0f80..faf56f50608f9391d2a73ed7c61bfdd9c2afab78:
> Make QSceneChange ctor protected to prevent direct use
> Split out QPropertyValue[Added|Removed] classes
> Rename QNodeRemovedPropertyChange -> QPropertyNodeRemovedChange
> Rename QNodeAddedPropertyChange -> QPropertyNodeAddedChange
> QNode[Added|Removed]PropertyChange inheritance changed
> Add QStaticPropertyValueRemovedChangeBase
> Add QStaticPropertyValueAddedChangeBase
> Make typed property change a private header template
> QNodePropertyChange -> QPropertyUpdatedChange
> QNodePropertyChangeBase -> QStaticPropertyUpdatedChangeBase
> QNodeDynamicPropertyChange -> QDynamicPropertyUpdatedChange
> Rename QNodePropertyChangeBase -> QPropertyChangeBase
> Mark QNodeUpdatedChangeBase ctor protected and export class
> Make ctors explicit, provide out of line dtors and export classes
> Remove QSceneChange::SenderType
> Change arbiter checks DeliveryFlags
> QBackendNodePropertyChange sets delivery flags to all
> Add setter/getter for delivery flags to QSceneChange
> Remove unnecessary forward declaration and move another
> Remove QSceneChange::timestamp()
> Remove ChangeFlag from NodeUpdated change type ctors
> Temporarily remove use of a custom allocator for QNodePropertyChanges
> Change inheritance of QNode[Added|Removed]PropertyChange
> Move change classes into their own dir and tidy up .pro/.pri files
> Add QPropertyValueRemovedChangeBase
> Add QPropertyValueAddedChangeBase
> Rename NodeAdded/NodeRemoved ChangeFlags
> Rename NodeUpdated ChangeFlag to PropertyUpdated
> Fix compilation on MSVC2013
> Fix reset in bigmodel example
> Add QNode::notifyObservers()
> QRenderState needs to create creation changes too
> Set QObject parent immediately and defer backend notifications
> qgltf: fix GCC 6 warning about misleading indention
> ShaderParameterPack: use rvalue QVector::push_back
> ShaderParameterPack: fix parameter passing (II)
> ShaderParameterPack: fix parameter passing (I)
> Mark more types movable/primitive/shared
> Removing defunct examples - Cpp_example
> QShaderData should notify dynamic property changes
> Add convenience to notify dynamic property changes
> Add missing pointer typedef
> Properly export QNodeDynamicPropertyChange symbols
> Replaced FPS Camera with Orbit - Custom-mesh-cpp
> Replaced FPS Camera with Orbit - Custom-mesh
> Replaced FPS Camera with Orbit - Loader-qml
> Replaced FPS Camera with Orbit - MouseInpt
> Replaced FPS Camera with Orbit - Simple-cpp
> Replaced FPS Camera with Orbit - Simple-qml
> Replaced FPS Camera with Orbit - Smpl Shader
> Replaced FPS Camera with Orbit - Tessellation
> Add missing "We mean it" warnings
> Add QNodeDynamicPropertyChange class
> Change QNodePropertyChangeBase to inherit from QNodeUpdatedChangeBase
> Add QNodeUpdatedChangeBase
> Remove unneeded ctors from QSceneChange and subclasses
> Add Q_DECL_NOEXCEPT to getters in QSceneChange
> Cleanup defunct comment in qscenechange.h
> Rename ObserverType to SenderType in QSceneChange
> Port missing examples to the new Layer(Filter) API
> Removing defunct examples - Torus-qml
> Removing defunct examples - Playground-qml
> Remove NodeAboutToBeDeleted change type enum value
> GLTFIO: claim copyright for the substantial recent changes
> GLTFIO: move QFile::readAll() into resolveLocalData()
> GLTFIO: replace QMap with QHash
> GLTFIO: includemocs
> GLTFIO: use printf-style qWarning/qDebug where possible
> GLTFIO: wrap remaining qWarning()s in Q_UNLIKELY
> GLTFIO: replace static const QLatin1Strings with #defines
> GLTFIO: brush up ctors of nested structs
> GLTFIO: avoid some hidden detaches
> GLTFIO: remove {QMap,QMultiHash}::remove() calls
> GLTFIO: eradicate remaining Q_FOREACH loops
> GLTFIO: remove {QMap,QMultiHash}::contains() calls
> GLTFIO: fix leak of QShaderProgram in processJSONProgram()
> GLTFIO: