qt/qt3d.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Removes ThreadWeaver code from Qt3D	Mika Salmela	2015-02-19	1	-1/+5
\| \| \| \| \| \| \| \| \|	Qt3D will be published with commercial licenses and there can't be 3rd party LGPL code. This task will remove the ThreadWeaver code and places the adaptation code inside configuration. Change-Id: I316f23087cdd8fed0afafbb1a3d78e3ff159585a Reviewed-by: Sean Harmer <sean.harmer@kdab.com>
*	Add qdocconf file for Qt3DCore	Sean Harmer	2014-12-22	1	-1/+1
\| \| \| \| \|	Change-Id: I5407b486a5a7d5a1eacc654c2c227b8114959b65 Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
*	Don't force a dynamic build when not configured for gcov	Sean Harmer	2014-12-21	1	-2/+0
\| \| \| \| \| \| \| \|	This is needed to allow Qt3D to build when Qt is configured for a static build. Change-Id: Ib3d5bbe3df57ef13d94788dcbadedef983b028a6 Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
*	Remove references to unused private headers variable in .pro files	Sean Harmer	2014-12-21	1	-3/+0
\| \| \| \| \|	Change-Id: Ia0e38843b4dc720e55d6e65d9bd97c27eeb7e9f7 Reviewed-by: Paul Lemire <paul.lemire@kdab.com>
*	QQmlExtensionPlugins for Qt3DCore and Qt3DRenderer	Paul Lemire	2014-05-25	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Quick3D components for core and renderer have been moved to their own module. For each module, a QQmlExtensionPlugin has been created and is installed in qtbase/qml/Qt3D/. To use the Qml API, 3dquick needs to added in the .pro. 3dquickrenderer can be added if subclassing Quick3D elements defined in Renderer. Otherwise, appending it is not necessary as the Qml engine will automatically load the QQmlExtensionPlugin. Core has no more reference to the QML module. Qt3DRenderer still has references to the QML module which will be remove in follow up patches. Change-Id: I0cd5cbd27020c776b9eb8d1548514df2b1321bbd Reviewed-by: Sean Harmer <sean.harmer@kdab.com>
*	Rendering Aspect to dedicated Qt3D module library.	Paul Lemire	2014-03-25	1	-2/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Aspects are now independent Qt3D modules. This allows aspects to expose classes that can be reused by other aspects. Unlike plugins however, aspect modules have to be registered to the QAspectManager when the Qt3D window is created. At the moment there is only a single aspect : RendererAspect To load the RendererAspect QT += 3drenderer Examples updated to work with the changes. QML components defined in the RendererAspect are accessible by importing Qt3D.Render 2.0. Examples have been updated accordingly. Change-Id: I1281b1ffc1a633292b394c7d0460f1e16b34b488 Reviewed-by: Sean Harmer <sean.harmer@kdab.com>
*	Moved Assimp to src/3rdparty	Paul Lemire	2014-03-21	1	-0/+1
\| \| \| \| \|	Change-Id: Ic813285c2ee6a36d0e8e6dc6807d6d55f7ec1df4 Reviewed-by: Sean Harmer <sean.harmer@kdab.com>
*	Import initial examples and export symbols from lib	Sean Harmer	2014-02-25	1	-1/+1
\| \| \| \| \|	Change-Id: I6eb7c66cb96956e3cb3e1d319a82a08a0fd3c37a Reviewed-by: Sean Harmer <sean.harmer@kdab.com>
*	Use threadweaver in concrete implementation of tasking api	Sean Harmer	2014-02-10	1	-0/+1
\| \| \| \| \| \| \|	ThreadWeaver::Job requires exception support be enabled. Change-Id: I404ded3388d1eb8dc9ad8bfe2bf8727b6bc86e8d Reviewed-by: Giuseppe D'Angelo <giuseppe.dangelo@kdab.com>
*	Initial import of Qt3DCore and Renderer aspect	Sean Harmer	2014-02-10	1	-0/+27
	For now the renderer aspect is still compiled into the Qt3DCore library. This needs to be split out into a plugin so it can be loaded dynamically along with other future aspects. Change-Id: Iba8402b35c7ebc1c503d438c87aad77f5fef2261 Reviewed-by: Giuseppe D'Angelo <giuseppe.dangelo@kdab.com>