[Development] Marking BB10 unsupported

[Rafael Roquetto]

Hi all,

Exactly what Bo said.

From time to time I keep getting BB10 related bug reports. It is not a lot,
but they still exist. In additition to that, there have been quite some
changes in Qt (such as the move towards C++11, or the forkfd based QProcess)
that affect QNX/BB10. These involve some testing to make sure no regressions
have been introduced (for instance, I have two pending patches for fixing the
QNX build on Windows that was broken because of a patch related to IPC and
shared memory). The focus now falls entirely on spending these limited
resources on keeping QNX 650 and 660 healthy on Qt - BB10 will no longer be
tested (at least not by KDAB) or supported.

In practice, if the build breaks, or something is not working, as Bo said, we
(KDAB) won't fix it. That of course does not prevent interested third parties
from keeping things going forward for BB10.

I hope this answers your questions regarding which kind of problem it solves.

If anyone think it is worth it volunteering to look after the BB10 side of
things, as a BB10 user myself I would be more than happy to provide
assistance.

Cheers,
Rafael

On Tue, Mar 24, 2015 at 12:07:18PM +0100, Bo Thorsen wrote:
> Hi Vladimir,
> 
> Den 24-03-2015 kl. 10:23 skrev Vladimir Minenko:
> >On 24/03/15 09:04, Blasche Alexander wrote:
> >>The BB10 code in Qt is not just the platform plugin. Does this
> >>statement apply to all other BB10 code throughout other Qt modules?
> >
> >Following this question from Alex, and actually asking more Rafael. What
> >do you mean exactly with "mark the BlackBerry 10 platform unsupported"?
> >Which problem do you like to solve?
> >
> >>To mind comes sensors, qtlocation, bluetooth, nfc and maybe
> >>multimedia.
> >
> >On top of this, the current implementation of QPA for BB10 is very much
> >interlinked with the QNX one, it is basically almost the same.
> >
> >While clarifying which problem will "mark the BlackBerry 10 platform
> >unsupported" actually solve, I just want to warn that making actual
> >changes in code in that respect will result in quite some work. I'm not
> >sure if somebody in the project has that much time for this.
> >
> >>And just out of curiosity, how do I distinguish QNX from BB10.The
> >>line is often very blurry.
> >
> >Indeed. It is just as easy as on other platforms which have used a core
> >OS and have added middleware and apps on top. Do you know the way how to
> >distinguish Linux from Andriod which runs on top of it?
> >
> >Generally, there are defines set by configure which let you check you
> >you run on pure QNX or on BB10.
> 
> I could be wrong in this, so please correct if there are mistakes.
> 
> When BB10 is unsupported, if a fix for QNX breaks BB10, that's acceptable
> (undesirable, of course, BB10 might come back).
> 
> "Things" should work on QNX. Whether or not it works on BB10 is not
> important.
> 
> Bugs for BB10 are basically irrelevant, QNX bugs are not.
> 
> There will be no active development on BB, QNX will be kept up to date.
> 
> I don't think this makes much of a difference for QNX, if any. One of my
> customers use the on screen BB keyboard on QNX, and this might have an
> impact. But other than weird stuff like this, I don't think you have to
> worry.
> 
> Bo Thorsen,
> Director, Viking Software.
> 
> -- 
> Viking Software
> Qt and C++ developers for hire
> http://www.vikingsoft.eu

-- 
Rafael Roquetto | rafael.roquetto at kdab.com | Software Engineer
Klarälvdalens Datakonsult AB, a KDAB Group company
Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322)
KDAB - Qt Experts
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 4861 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/development/attachments/20150324/713b882a/attachment.bin>