[Interest] 5.8 Features?

[Jason H]

https://bugreports.qt.io/browse/QTBUG-32335 - Add support for Notifications (Android, reported July 2013)
https://bugreports.qt.io/browse/QTBUG-4011 - Add support for native notification systems. (4.5, unresolved)
https://bugreports.qt.io/browse/QTBUG-29611 - (Desktop) Notifications (Mar 2010, P2, open)
https://bugreports.qt.io/browse/QTBUG-49336 - Support new OS X Notification Center banners for systray balloon notification. (Nov 1015)

There does not seem to be one for iOS, but I suspect the OSX one would work? The issues are there, have been there, they just aren't being worked on.


> Sent: Tuesday, June 28, 2016 at 9:59 AM
> From: "Jason H" <jhihn at gmx.com>
> To: "Tuukka Turunen" <tuukka.turunen at qt.io>
> Cc: "interest at qt-project.org" <interest at qt-project.org>
> Subject: Re: [Interest] 5.8 Features?
>
> > Sent: Monday, June 27, 2016 at 5:40 PM
> > From: "Tuukka Turunen" <tuukka.turunen at qt.io>
> > To: "Jason H" <jhihn at gmx.com>, "Daniel França" <daniel.franca at gmail.com>
> > Cc: "interest at qt-project.org" <interest at qt-project.org>
> > Subject: RE: [Interest] 5.8 Features?
> >
> > 
> > 
> > > -----Original Message-----
> > > From: Interest [mailto:interest-bounces+tuukka.turunen=qt.io at qt-
> > > project.org] On Behalf Of Jason H
> > > Sent: maanantaina 27. kesäkuuta 2016 21.15
> > > To: "Daniel França" <daniel.franca at gmail.com>
> > > Cc: interest at qt-project.org
> > > Subject: Re: [Interest] 5.8 Features?
> > > 
> > > 
> > > Could we possibly come up with a "mobile features" priority list
> > > and help focus what gets delivered?
> > > 
> > 
> > That would be very much welcome. It is possible to make suggestions in the bugreports.qt.io JIRA for new features. If there already exists a suggestion, it is possible to vote for the implementation of the feature.
> > 
> > I do personally believe that a lot of the same value that Qt has as a solid c++ toolkit for creating large scale enterprise desktop applications holds true also for large scale mobile applications. If you have a large team developing with some of the mobile only frameworks over a long period of time, maintenance can become a burden. Now, for independent developers it may be a bit less challenging, but having a solid and well structured (Qt) framework should benefit in the non-trivial applications. 
> > 
> > As I wrote earlier to this thread, we have invested quite a lot into mobile lately, but perhaps not visible enough. For example, the WinRT / Windows 10 support has been created from scratch in the past couple of releases. For many focusing to Android and iOS only that probably does not matter, but from the whole picture it is important for Qt. Also the creation on lightweight Qt Quick Controls 2 as well as renewal of the HighDPI/scalability support have been big and important tasks.
> > 
> 
> 
> Yeah, I'm going to say that porting to WinRT when the platform is dead isn't a productive use of developer time (Win10 sure). ( http://www.theverge.com/2016/5/23/11743594/microsoft-windows-phone-market-share-below-1-percent ) I understand that QPA wants to shine, but really hitting more basic, missing features of exsiting phone OSs is a better use of time IMHO. WinRT might be a special case because of that MS is doing with Win10, but I would not pile that on to the 'mobile' category.
> 
> 
> 
> 
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>