I would like to see Qt Bluetooth support back to Windows 7. However I agree work priority should be focused on Windows mobile devices.
For Windows 7 support I had to write an abstraction layer for Bluetooth that is implemented using Winsock 2.2. If Windows 10 and mobile devices drop support for Windsock 2.2, then I totally understand not having the resource for Qt to support all Windows platforms. -Ed On Jun 17, 2015, at 3:33 AM, Eric Lemanisser <eric.lemaniss...@gmail.com<mailto:eric.lemaniss...@gmail.com>> wrote: Hello, I totally +1 this feature ! However if I'm not mistaking, focusing on WinRT api discards MinGW compiler, that's bad news for open source tools. Best regards, Eric Le mar. 16 juin 2015 à 15:35, Attila Csipa <q...@csipa.in.rs<mailto:q...@csipa.in.rs>> a écrit : Hi, A huge +1 on this, BT support on Windows is long overdue. While there is certainly more inertia in the windows desktop version than probably any other Qt supported platform, Microsoft itself is trying to nudge people into quicker upgrade cycles, and while Win8 has certainly gotten a pushback, with Win10 around the corner I would also try not to get bogged down with pre-WinRT solutions, as painful as that might sound in some cases. Best regards, Attila On 6/16/2015 1:42 PM, Kalinowski Maurice wrote: > Hi everyone, > > It might sound weird that while we're trying to get 5.5.0 out I am starting a > discussion about Qt 5.6, but if you look at the release schedule there is not > much time for the feature freeze > > https://wiki.qt.io/Qt-5.6-release > > One of the items the Windows / WinRT team would really like to see included > to that release is support for Bluetooth and BTLE. > > The current idea is to use the WinRT API for that backend, as it provides the > advantage that it can also be used on Windows Desktop starting Windows 8(.1). > WinRT covers Windows 10 support (both classic and Unified Windows Platform) > as well. > > This leaves out support for Windows Desktop older than Windows 8. But as we > are aiming to implement new features, we should draw the line somewhere and > the WinRT backend clearly has the biggest potential to be supported in many > years' time, while the (or multiple) pure desktop solution would be > deprecated sooner or later again. Also given the fact that we can target > quite many platforms with one backend gives us a better coverage for > maintenance and resourcing. > > The reason that I am mentioning this on the mailing list is that after > talking to some folks here in The Qt Company, multiple people inside and > outside already started or wanted to start efforts on this topic. Hence the > aim of this email is to get everyone connected and work on it together to > make it happen within the 5.6 feature freeze. > > So, if you have worked on Bluetooth (LE) on Windows or want to, please get in > touch with me to align. > > > BR, > Maurice > > > -------- > Maurice Kalinowski - Senior Manager, Qt Tools > > The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin > Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der > Gesellschaft: > Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B > > Email: > maurice.kalinow...@theqtcompany.com<mailto:maurice.kalinow...@theqtcompany.com> > | Mobile: + 49 175 187 19 52 | Phone: > +49 30 63 92 3255 www.qt.io<http://www.qt.io/> |Qt Blog: > http://blog.qt.digia.com/ | Twitter: > @QtbyDigia, @Qtproject | Facebook: > www.facebook.com/qt<http://www.facebook.com/qt> > > > _______________________________________________ > Development mailing list > Development@qt-project.org<mailto:Development@qt-project.org> > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org<mailto:Development@qt-project.org> http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org<mailto:Development@qt-project.org> http://lists.qt-project.org/mailman/listinfo/development This email and any files transmitted with it from The Charles Machine Works, Inc. are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the sender. Our company accepts no liability for the contents of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
