Re: [Development] API/ABI changes report
On sexta-feira, 5 de fevereiro de 2016 08:58:15 PST Thiago Macieira wrote: > - QWindowSystemInterface: binary incompatible (class is \ingroup qpa, but > not in a _qpa.h header, therefore it's public API) > > => is anyone reading the header diff for QtGui? This happened *after* the header diff. -- 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] API/ABI changes report
On sexta-feira, 5 de fevereiro de 2016 16:34:19 PST Ponomarenko Andrey wrote: > Hello, > > I've started to maintain API/ABI changes report for the Qt library here: > http://abi-laboratory.pro/tracker/timeline/qt/ Hello Andrey Thank you for the service. Looking at the only release we have any control over right now: 5.6. * Qt3D: major changes, definitely not binary compatible. Was the release in 5.5 properly marked as "technical preview, no ABI promise"? * QtCore: false positive, sendEvent() is still there. * QtGui: - QPixmapCache::allPixmaps(): innocent, was not public API, but you could get to it. - qt_sendShortcutOverrideEvent: affects QtTest binary compatibility - qt_handleMouseEvent: ditto - QWindowSystemInterface: binary incompatible (class is \ingroup qpa, but not in a _qpa.h header, therefore it's public API) => is anyone reading the header diff for QtGui? * QtNetwork: false positive * QtQuick: - DesignerSupport: previously exported, undocumented class that wasn't in a _p.h header and did not even have a Q prefix. We can safely assume this was a major mistake in releasing and is now corrected. - events & accessibility: false positive * QtWaylandClient: - events: false positive - qt_extended_output: was public and should not have been removed. The same change also changed values of enums in other public classes (like QWaylandCompositor). => is anyone reading the header diff for QtWaylandClient? * QtWidgets: - accessibility: false positive -- 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] API/ABI changes report
On Friday 05 Feb 2016 08:58:15 Thiago Macieira wrote: > On sexta-feira, 5 de fevereiro de 2016 16:34:19 PST Ponomarenko Andrey wrote: > > Hello, > > > > I've started to maintain API/ABI changes report for the Qt library here: > > http://abi-laboratory.pro/tracker/timeline/qt/ > > Hello Andrey > > Thank you for the service. > > Looking at the only release we have any control over right now: 5.6. > > * Qt3D: major changes, definitely not binary compatible. Was the release in > 5.5 properly marked as "technical preview, no ABI promise"? Yes. Still a a tech preview in 5.6 too so can be safely ignored for now. Sean > > * QtCore: false positive, sendEvent() is still there. > > * QtGui: > - QPixmapCache::allPixmaps(): innocent, was not public API, but you could > get to it. > - qt_sendShortcutOverrideEvent: affects QtTest binary compatibility > - qt_handleMouseEvent: ditto > - QWindowSystemInterface: binary incompatible (class is \ingroup qpa, but > not in a _qpa.h header, therefore it's public API) > > => is anyone reading the header diff for QtGui? > > * QtNetwork: false positive > > * QtQuick: > - DesignerSupport: previously exported, undocumented class that wasn't in a > _p.h header and did not even have a Q prefix. We can safely assume this was > a major mistake in releasing and is now corrected. > - events & accessibility: false positive > > * QtWaylandClient: > - events: false positive > - qt_extended_output: was public and should not have been removed. The same > change also changed values of enums in other public classes >(like QWaylandCompositor). > > => is anyone reading the header diff for QtWaylandClient? > > * QtWidgets: > - accessibility: false positive -- Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK KDAB (UK) Ltd, a KDAB Group company Tel. +44 (0)1625 809908; Sweden (HQ) +46-563-540090 Mobile: +44 (0)7545 140604 KDAB - Qt Experts ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] API/ABI changes report
On Fri, Feb 5, 2016, at 05:58 PM, Thiago Macieira wrote: > - QWindowSystemInterface: binary incompatible (class is \ingroup qpa, > but not >in a _qpa.h header, therefore it's public API) I don't agree with this. None of the QPA files have a _qpa.h extension (and haven't since 2012 -- see qtbase/037238022f3a91a5619709b2c7cf4b38cd4d294b), all of them clearly carry a warning "header", and all of them are put in include/qpa/ (see sync.profile), so they are not public. > * QtWaylandClient: > - events: false positive > - qt_extended_output: was public and should not have been removed. The > same >change also changed values of enums in other public classes >(like QWaylandCompositor). QtWaylandClient is not a public module. It's the platform plugin for Wayland. There isn't yet any API that is public (and not preview-level) in QtWayland. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] API/ABI changes report
On sexta-feira, 5 de fevereiro de 2016 21:07:29 PST Harri Porten wrote: > On Fri, 5 Feb 2016, Thiago Macieira wrote: > > * QtGui: > > - QPixmapCache::allPixmaps(): innocent, was not public API, but you could > > get> > > to it. > > > > - qt_sendShortcutOverrideEvent: affects QtTest binary compatibility > > Our product (and its users) were bitten by this as well. As the function > wasn't documented we took the blame on us. Renamings of quasi-public > functions are something that can be avoided however :) > > Thanks to Andrey from me as well, QtTest is special case library, for which binary compatibility isn't always guaranteed. I personally think that we should guarantee it as much as we can, since it allows us to run tests compiled with one Qt against another, to check for regressions. I did that VERY often in my days at Trolltech. In this case, the symbol isn't in QtTest, but in QtGui. It's technically a private symbol, but it was used from inline functions from QtTest. Therefore I would really prefer for the symbol to be brought back. -- 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] API/ABI changes report
On Fri, 5 Feb 2016, Thiago Macieira wrote: * QtGui: - QPixmapCache::allPixmaps(): innocent, was not public API, but you could get to it. - qt_sendShortcutOverrideEvent: affects QtTest binary compatibility Our product (and its users) were bitten by this as well. As the function wasn't documented we took the blame on us. Renamings of quasi-public functions are something that can be avoided however :) Thanks to Andrey from me as well, Harri. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt.labs controls problem
Hi, just started Qt development and installed Qt 5.6 beta for Android and iOS All went well and I'm able to deploy sample apps to my (Android) BlackBerry PRIV :) The slider also works well: switching between virtual and hardware keyboard works as expected Most samples are looking ugly because of High DPI - but that's the reason why I waited for Qt 5.6 Beta to start Qt development for mobile ;-) I want to use High DPI support, the labs controls and Material Design. As a first step I followed the instructions here: https://doc-snapshots.qt.io/qt5-5.6/qtlabscontrols-gettingstarted.html and copied the content to main.cpp and main.qml unfortunately it fails: |W/libtest_q2_controls.so(15994): (null):0 ((null)): QQmlApplicationEngine failed to load component W/libtest_q2_controls.so(15994): (null):0 ((null)): file:///data/data/org.qtproject.example.test_q2_controls/files/main.qml:-1 File not found | also in design mode Qt.quick 2.6 isn't available am I missing anything ? thanks for any hints. (see also my entry in forum: https://forum.qt.io/topic/63824/unsupported-qt-quick-version-main-qml-not-found ) -- ekke (ekkehard gentz) independent software architect international development mobile apps for BlackBerry 10 workshops - trainings - bootcamps *BlackBerry Elite Developer BlackBerry Platinum Enterprise Partner* max-josefs-platz 30, D-83022 rosenheim, germany mailto:e...@ekkes-corner.org blog: http://ekkes-corner.org apps and more: http://appbus.org twitter: @ekkescorner skype: ekkes-corner LinkedIn: http://linkedin.com/in/ekkehard/ Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID: DE189929490 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt.labs controls problem
just got the answer in forum.
had to change the path to main.qml:
|QQmlApplicationEngine engine;
engine.load(QUrl(QStringLiteral("qrc:/main.qml")));|
now it works and I can go on :)
ekke
Am 05.02.16 um 13:27 schrieb ekke:
> Hi,
>
> just started Qt development and installed Qt 5.6 beta for Android and iOS
> All went well and I'm able to deploy sample apps to my (Android)
> BlackBerry PRIV :)
>
> The slider also works well: switching between virtual and hardware
> keyboard works as expected
>
> Most samples are looking ugly because of High DPI - but that's the
> reason why I waited for Qt 5.6 Beta to start Qt development for mobile ;-)
> I want to use High DPI support, the labs controls and Material Design.
>
> As a first step I followed the instructions here:
> https://doc-snapshots.qt.io/qt5-5.6/qtlabscontrols-gettingstarted.html
> and copied the content to main.cpp and main.qml
>
> unfortunately it fails:
> |W/libtest_q2_controls.so(15994): (null):0 ((null)):
> QQmlApplicationEngine failed to load component
> W/libtest_q2_controls.so(15994): (null):0 ((null)):
> file:///data/data/org.qtproject.example.test_q2_controls/files/main.qml:-1
> File not found |
> also in design mode Qt.quick 2.6 isn't available
>
> am I missing anything ?
>
> thanks for any hints.
>
> (see also my entry in forum:
> https://forum.qt.io/topic/63824/unsupported-qt-quick-version-main-qml-not-found
> )
> --
>
> ekke (ekkehard gentz)
>
> independent software architect
> international development mobile apps for BlackBerry 10
> workshops - trainings - bootcamps
>
> *BlackBerry Elite Developer
> BlackBerry Platinum Enterprise Partner*
>
> max-josefs-platz 30, D-83022 rosenheim, germany
> mailto:e...@ekkes-corner.org
> blog: http://ekkes-corner.org
> apps and more: http://appbus.org
>
> twitter: @ekkescorner
> skype: ekkes-corner
> LinkedIn: http://linkedin.com/in/ekkehard/
> Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID: DE189929490
>
>
>
> ___
> 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
Re: [Development] API/ABI changes report
Excelent job, Andrey! On Fri, Feb 5, 2016 at 4:34 PM Ponomarenko Andrey < andrewponomare...@yandex.ru> wrote: > Hello, > > I've started to maintain API/ABI changes report for the Qt library here: > http://abi-laboratory.pro/tracker/timeline/qt/ > > It took about two weeks to build and perform analysis for ~50 versions of > the library from 4.0 up to 5.6.0-beta and finally I can share the report > with the community. Hope the report will help Linux maintainers of the > library to be aware of ABI structure changes and added/removed binary > symbols. > > I understand that the report contains several false positives and > definitely some false negatives. Also it says nothing about behavioral ABI > changes. But it still can be used as a first approximation. > > Please let me know if some information in the report is incorrect/missed > or you see some obvious false positives/negatives. I'll try to improve > basic analysis tools. > > Thank you. > ___ > 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] API/ABI changes report
Hello, I've started to maintain API/ABI changes report for the Qt library here: http://abi-laboratory.pro/tracker/timeline/qt/ It took about two weeks to build and perform analysis for ~50 versions of the library from 4.0 up to 5.6.0-beta and finally I can share the report with the community. Hope the report will help Linux maintainers of the library to be aware of ABI structure changes and added/removed binary symbols. I understand that the report contains several false positives and definitely some false negatives. Also it says nothing about behavioral ABI changes. But it still can be used as a first approximation. Please let me know if some information in the report is incorrect/missed or you see some obvious false positives/negatives. I'll try to improve basic analysis tools. Thank you. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
