Revision history [back]

Dear Jolla,

There have been hints and suggestions dropped in the past few years on a Qt upgrade being worked on, and would likely be coming down the pipes in Sailfish 3.x. However, it's been awfully quiet when it comes to a roadmap, and on Qt in particular.

It's sad to see the (IMO) best linux based phone on the market lagging behind Ubuntu phone or even android when it comes to Qt. The ecosystem is small as it is, and to stay viable, we need every developer on the platform we can get.

It would help immensely if we would have QtQuick Controls 2 available, which would allow developers to more easily target multiple platforms without having to write a completely different UI when porting to another platform. This would work in reverse as well, existing QQC2 applications are more easily ported to Sailfish (even if that doesn't use Silica styling, which is ok)

I think the developer community deserves a more concrete timeline from Jolla on Qt, not just vague statements when asked in the IRC developer meetings.

A few past posts highlighting the limitations we encounter: https://together.jolla.com/question/183733/qt5-qtconnectivity-update-from-56-to-58/ https://together.jolla.com/question/155875/qt57-and-sailfish/ https://together.jolla.com/question/194079/qt-512-and-sailfish-os-3/ https://together.jolla.com/question/191756/qt-version-upgrade-plans/

Dear Jolla,

There have been hints and suggestions dropped in the past few years on a Qt upgrade being worked on, and would likely be coming down the pipes in Sailfish 3.x. However, it's been awfully quiet when it comes to a roadmap, and on Qt in particular.

It's sad to see the (IMO) best linux based phone on the market lagging behind Ubuntu phone or even android when it comes to Qt. The ecosystem is small as it is, and to stay viable, we need every developer on the platform we can get.

It would help immensely if we would have QtQuick Controls 2 available, which would allow developers to more easily target multiple platforms without having to write a completely different UI when porting to another platform. This would work in reverse as well, existing QQC2 applications are more easily ported to Sailfish (even if that doesn't use Silica styling, which is ok)

I think the developer community deserves a more concrete timeline from Jolla on Qt, not just vague statements when asked in the IRC developer meetings.

A few past posts highlighting the limitations we encounter: https://together.jolla.com/question/183733/qt5-qtconnectivity-update-from-56-to-58/ https://together.jolla.com/question/155875/qt57-and-sailfish/ https://together.jolla.com/question/194079/qt-512-and-sailfish-os-3/ encounter:

• https://together.jolla.com/question/183733/qt5-qtconnectivity-update-from-56-to-58/
• https://together.jolla.com/question/155875/qt57-and-sailfish/
• https://together.jolla.com/question/194079/qt-512-and-sailfish-os-3/
• https://together.jolla.com/question/191756/qt-version-upgrade-plans/