Re: [Interest] 5.8 Features?

[Federico Buti]

https://bugreports.qt.io/browse/QTBUG-44804 - [iOS] [Android] Add an API to
Qt for sending push notifications



On 28 June 2016 at 16:22, Jason H  wrote:

> 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" 
> > To: "Tuukka Turunen" 
> > Cc: "interest@qt-project.org" 
> > Subject: Re: [Interest] 5.8 Features?
> >
> > > Sent: Monday, June 27, 2016 at 5:40 PM
> > > From: "Tuukka Turunen" 
> > > To: "Jason H" , "Daniel França" <
> daniel.fra...@gmail.com>
> > > Cc: "interest@qt-project.org" 
> > > Subject: RE: [Interest] 5.8 Features?
> > >
> > >
> > >
> > > > -Original Message-
> > > > From: Interest [mailto:interest-bounces+tuukka.turunen=qt.io@qt-
> > > > project.org] On Behalf Of Jason H
> > > > Sent: maanantaina 27. kesäkuuta 2016 21.15
> > > > To: "Daniel França" 
> > > > Cc: interest@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@qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/interest
> >
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [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" 
> To: "Tuukka Turunen" 
> Cc: "interest@qt-project.org" 
> Subject: Re: [Interest] 5.8 Features?
>
> > Sent: Monday, June 27, 2016 at 5:40 PM
> > From: "Tuukka Turunen" 
> > To: "Jason H" , "Daniel França" 
> > Cc: "interest@qt-project.org" 
> > Subject: RE: [Interest] 5.8 Features?
> >
> > 
> > 
> > > -Original Message-
> > > From: Interest [mailto:interest-bounces+tuukka.turunen=qt.io@qt-
> > > project.org] On Behalf Of Jason H
> > > Sent: maanantaina 27. kesäkuuta 2016 21.15
> > > To: "Daniel França" 
> > > Cc: interest@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@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Jason H]

> Sent: Monday, June 27, 2016 at 5:40 PM
> From: "Tuukka Turunen" 
> To: "Jason H" , "Daniel França" 
> Cc: "interest@qt-project.org" 
> Subject: RE: [Interest] 5.8 Features?
>
> 
> 
> > -Original Message-
> > From: Interest [mailto:interest-bounces+tuukka.turunen=qt.io@qt-
> > project.org] On Behalf Of Jason H
> > Sent: maanantaina 27. kesäkuuta 2016 21.15
> > To: "Daniel França" 
> > Cc: interest@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@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Marco Piccolino]

IRC mirror is qtmob.irc.slack.com
#general is the main channel.
M

2016-06-28 9:01 GMT+02:00 Shawn Rutledge :

>
> > On 28 Jun 2016, at 08:15, Marco Piccolino 
> wrote:
> >
> > would be great to collect and exchange this to help each other - don't
> know where's the best place and it should be promoted by Qt
> >
> > Several packages which improve using Qt on mobile (and elsewhere!) are
> currently published on qpm (http://qpm.io), with the sources available on
> github. Currently there are just a couple of projects tageting native parts
> but that should change if more people invest their time and energy.
>
> Legally we can’t just snarf code from github - the authors would have to
> contribute it to Qt.  And there are probably some things there that could
> be added to Qt if they would like to make the contribution.
>
> > Most of the mobile app developers who provide these meet and discuss
> regularly on http://slackin.qtmob.org as well as on the regular channels.
> Everyone is welcome to join so that efforts are not duplicate.
>
> Is it mirrored to IRC?
>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Marco Piccolino]

This is certainly a valid point. So I guess this means that a decision
about whether a feature should be contributed to Qt or kept as a 3rd party
addon should be made early on.
Il 28 giu 2016 10:09 AM, "Kai Koehne"  ha scritto:



> -Original Message-
> From: Interest [mailto:interest-bounces+kai.koehne=qt...@qt-project.org]
> On Behalf Of Marco Piccolino
> Sent: Tuesday, June 28, 2016 9:07 AM
> To: Shawn Rutledge 
> Cc: interest@qt-project.org
> Subject: Re: [Interest] 5.8 Features?
>
> I see inclusion into Qt as a second step and only for functionality that
will be
> needed by nearly everybody working on mobile. I meant that being it github
> projects, everyone can contribute.

Well, the problem is that if you/we decide after some time to move some of
the code
into Qt, we'd need every single contributor to sign the Qt Contribution
Agreement.
This can be hard especially for github contributions, where all you have of
a
contributor at times is the github account.  That's why it's highly
encouraged
to use the Qt project infrastructure from the start. This doesn't mean that
it instantly has to be part of Qt releases, or follow the Qt release
schedule.
We also have lots of 'playground' modules. See also

https://wiki.qt.io/Creating_a_new_module_or_tool_for_Qt

Regards
Kai
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Kai Koehne]

> -Original Message-
> From: Interest [mailto:interest-bounces+kai.koehne=qt...@qt-project.org]
> On Behalf Of Marco Piccolino
> Sent: Tuesday, June 28, 2016 9:07 AM
> To: Shawn Rutledge 
> Cc: interest@qt-project.org
> Subject: Re: [Interest] 5.8 Features?
> 
> I see inclusion into Qt as a second step and only for functionality that will 
> be
> needed by nearly everybody working on mobile. I meant that being it github
> projects, everyone can contribute.

Well, the problem is that if you/we decide after some time to move some of the 
code
into Qt, we'd need every single contributor to sign the Qt Contribution 
Agreement.
This can be hard especially for github contributions, where all you have of a 
contributor at times is the github account.  That's why it's highly encouraged
to use the Qt project infrastructure from the start. This doesn't mean that
it instantly has to be part of Qt releases, or follow the Qt release schedule.
We also have lots of 'playground' modules. See also

https://wiki.qt.io/Creating_a_new_module_or_tool_for_Qt

Regards
Kai 

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Marco Piccolino]

I see inclusion into Qt as a second step and only for functionality that
will be needed by nearly everybody working on mobile. I meant that being it
github projects, everyone can contribute.
Yes the qtmob chat is accessibile through irc as well. I'll post the info
as soon as I get to work.
Il 28 giu 2016 9:01 AM, "Shawn Rutledge"  ha scritto:

>
> > On 28 Jun 2016, at 08:15, Marco Piccolino 
> wrote:
> >
> > would be great to collect and exchange this to help each other - don't
> know where's the best place and it should be promoted by Qt
> >
> > Several packages which improve using Qt on mobile (and elsewhere!) are
> currently published on qpm (http://qpm.io), with the sources available on
> github. Currently there are just a couple of projects tageting native parts
> but that should change if more people invest their time and energy.
>
> Legally we can’t just snarf code from github - the authors would have to
> contribute it to Qt.  And there are probably some things there that could
> be added to Qt if they would like to make the contribution.
>
> > Most of the mobile app developers who provide these meet and discuss
> regularly on http://slackin.qtmob.org as well as on the regular channels.
> Everyone is welcome to join so that efforts are not duplicate.
>
> Is it mirrored to IRC?
>
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Shawn Rutledge]

> On 28 Jun 2016, at 08:15, Marco Piccolino  wrote:
> 
> would be great to collect and exchange this to help each other - don't know 
> where's the best place and it should be promoted by Qt
> 
> Several packages which improve using Qt on mobile (and elsewhere!) are 
> currently published on qpm (http://qpm.io), with the sources available on 
> github. Currently there are just a couple of projects tageting native parts 
> but that should change if more people invest their time and energy.

Legally we can’t just snarf code from github - the authors would have to 
contribute it to Qt.  And there are probably some things there that could be 
added to Qt if they would like to make the contribution.

> Most of the mobile app developers who provide these meet and discuss 
> regularly on http://slackin.qtmob.org as well as on the regular channels. 
> Everyone is welcome to join so that efforts are not duplicate.

Is it mirrored to IRC?

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Marco Piccolino]

would be great to collect and exchange this to help each other - don't know
where's the best place and it should be promoted by Qt


Several packages which improve using Qt on mobile (and elsewhere!) are
currently published on qpm (http://qpm.io), with the sources available on
github. Currently there are just a couple of projects tageting native parts
but that should change if more people invest their time and energy.
Most of the mobile app developers who provide these meet and discuss
regularly on http://slackin.qtmob.org as well as on the regular channels.
Everyone is welcome to join so that efforts are not duplicate.
Hope this helps!

Marco Piccolino

Il 25 giu 2016 9:04 PM,  ha scritto:

>

> Send Interest mailing list submissions to
> interest@qt-project.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.qt-project.org/mailman/listinfo/interest
> or, via email, send a message with subject or body 'help' to
> interest-requ...@qt-project.org
>
> You can reach the person managing the list at
> interest-ow...@qt-project.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Interest digest..."
>
> Today's Topics:
>
>1. Re: 5.8 Features? (Jason H)
>2. Fwd: Re:  QUndoStack (Igor Mironchik)
>3. Fwd: Re:  QUndoStack (Igor Mironchik)
>4. Re: 5.8 Features? (Kevin Mcintyre)
>5. Re: Deploying QtWebEngine on Linux with Qt 5.6.0 (Thiago Macieira)
>6. Re: 5.8 Features? (ekke)
>7. QGraphicsScene & removing item (Igor Mironchik)
>8. Re: QMAKE_DEFAULT_INCDIRS = "/opt/local/include /usr/include"
>   and building QtWebengine (Ren? J. V. Bertin)
>9. Re: QGraphicsScene & removing item (Igor Mironchik)
>
>
> -- Messaggio inoltrato --
> From: Jason H 
> To: ekke 
> Cc: interest@qt-project.org
> Date: Fri, 24 Jun 2016 21:59:59 +0200
> Subject: Re: [Interest] 5.8 Features?
> I've solved these, to various exents, or Android and iOS.
> I would share my code as longas everyone promises to not laughs at my
code. I do not know what is "best" or everyone. I just wrote what I had to
fill the requirement I had.
>
>
*> Sent:* Friday, June 24, 2016 at 12:20 PM
*> From:* ekke 
*> To:* interest@qt-project.org
*> Subject:* Re: [Interest] 5.8 Features?
> Am 24.06.16 um 18:02 schrieb Jason H:


>>
>> 6 months of latency would be great.
>> But the things I talk about are pretty basic on mobile:
>> - Foreground/background lifecycle events,
>> - Screen wake locks,
>> - Notifications (local / remote)
>>
>> These have been aound since before Qt targeted mobile and are sorely
STILL missing from Qt.
>>
>> Things upcoming that I wouldn't complain about having to implement
myself:
>> - Fingerprint scanning
>> As this is relatively new for Android and iOS platforms. Though the
Atrix (2010) had a fingerprint scanner, but only Android 6 had a platform
API. iPhone had it as of the 5S.
>>
>> It's like Qt is on mobile only if you want to put things on the screen
and do AJAX. But if you really want to do anything really "mobile" you're
on your own. We still can't control the video recording parameters on iOS
(Thanks to my company, it will land in 5.6.2 -- was supposed to land in
5.6.1). Qt can only really be accurately described to be a Cross-platform
UI on mobile. Outside of that, you're writing Java and Obj-C. So call it
cross-platform for mobile is a stretch. I urging Qt to focus on eliminating
the asterisks, so it's proper Mobile (capital M) platform.
>>
>> With that said though, Qt's abstraction of various platform services is
a godsend. The fact that ReactNative gives you access to AVFoundation
doesn't do a whole lot when you have to write ReactNative that targets
AVFoundation and more code to target android.media SDK and handle the
intricacies of both in your own code base. So I think the Qt approach is
right. I just want more of it. :-)
>>
>
> +1
>
> another point: I think that there are many developers out there already
implementing common missing features in Java and ObjectiveC
>
> would be great to collect and exchange this to help each other - don't
know where's the best place and it should be promoted by Qt


>>
>>
*>> Sent:* Friday, June 24, 2016 at 9:26 AM
*>> From:* "Xavier Bigand" 
<http://flamaros.xav...@gmail.com>
*>> To:* "Robert Iakobashvili" 
<http://corobe...@gmail.com>
*>> Cc:* interest  <http://interest@qt-project.org>
*>> Subject:* Re: [Interest] 5.8 Features?
>> Like you said I think that the iOS and Android prog

Re: [Interest] 5.8 Features?

[Tuukka Turunen]

> -Original Message-
> From: Interest [mailto:interest-bounces+tuukka.turunen=qt.io@qt-
> project.org] On Behalf Of Jason H
> Sent: maanantaina 27. kesäkuuta 2016 21.15
> To: "Daniel França" 
> Cc: interest@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.

Yours,

Tuukka

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Sean Harmer]

Hi,


On 27/06/2016 19:14, Jason H wrote:

That's exactly my worry too. So far, I've had a number of mobile devs like you 
agree with me, but how do we take it to the next level and get the Qt company 
on board and actually do something?


As already mentioned:

1) Get a commercial license and pressure your sales contact.
2) Pay someone to contribute on your behalf.
3) Contribute yourselves - this is what happened with Qt 3D.



What's irritating me is that there aren't any other killer features competing. 
It also seems that these issues could be fixed relatively quickly if the trolls 
were to focus on it. I think adding something like 3D is much more complicated 
and affects far fewer people.


Depends upon your use cases. 3D can be very important for games 
(including mobile), scientific/engineering visualisation, and is gaining 
a lot of interest in automotive IVI. But 3D is something that I wanted 
to work on, so I did.


If you are interested in more mobile related features, then please do 
consider contributing. This can be anything from coding through to 
triaging JIRAs. I'm sure there will be others who will get involved too. 
I don't work for The Qt Company so I can't speak for their priorities 
but they have just released Qt Quick Controls 2 to be lighter weight for 
better performance on constrained systems.


Cheers,

Sean

  
  
Qt 5.7 added two mobile features:

- NFC (Android) (Also reported as a 5.6 feature)
- Android Services

While any addition is good, I find it hard that NFC was more missed that notifications.  
Could we possibly come up with a "mobile features" priority list and help focus 
what gets delivered?
Say, with a minimum of 1 (or more) feature(s) per X.Y release?



---
Sent: Monday, June 27, 2016 at 11:29 AM
From: "Daniel França" 
To: "interest@qt-project.org" 
Subject: Re: [Interest] 5.8 Features?

+1
I love Qt, but I'd tried to implement 3 mobile apps using Qt, and I always fall 
in some sort of limitation that annoys me.
Like you said, pretty basic things like the video recording parameters.

And I look into the next steps and I don't see any much effort on that area, 
this was the main reason I'd cancel my subscription.

Mobile seems more like a second class citizen.
  


On Fri, 24 Jun 2016 at 18:02 Jason H  wrote:

6 months of latency would be great.
But the things I talk about are pretty basic on mobile:
- Foreground/background lifecycle events,
- Screen wake locks,
- Notifications (local / remote)
  
These have been aound since before Qt targeted mobile and are sorely STILL missing from Qt.
  
Things upcoming that I wouldn't complain about having to implement myself:

- Fingerprint scanning
As this is relatively new for Android and iOS platforms. Though the Atrix 
(2010) had a fingerprint scanner, but only Android 6 had a platform API. iPhone 
had it as of the 5S.
  
It's like Qt is on mobile only if you want to put things on the screen and do AJAX. But if you really want to do anything really "mobile" you're on your own. We still can't control the video recording parameters on iOS (Thanks to my company, it will land in 5.6.2 -- was supposed to land in 5.6.1). Qt can only really be accurately described to be a Cross-platform UI on mobile. Outside of that, you're writing Java and Obj-C. So call it cross-platform for mobile is a stretch. I urging Qt to focus on eliminating the asterisks, so it's proper Mobile (capital M) platform.
  
With that said though, Qt's abstraction of various platform services is a godsend. The fact that ReactNative gives you access to AVFoundation doesn't do a whole lot when you have to write ReactNative that targets AVFoundation and more code to target android.media SDK and handle the intricacies of both in your own code base. So I think the Qt approach is right. I just want more of it. :-)
  
  
Sent: Friday, June 24, 2016 at 9:26 AM

From: "Xavier Bigand" 
To: "Robert Iakobashvili" 
Cc: interest 

Subject: Re: [Interest] 5.8 Features?

Like you said I think that the iOS and Android progress too fast and on an 
other cadence than Qt.
We should not forget that Qt has to create a unified cross platform API, that 
is necessary harder than creating a new one for one platform.
  
I think that a latency of 6 months to a year is still reasonable for Qt depending on how it fall with releases.
  
In my opinion if you need something faster, you may have to consider to implement features your self. We started our application with 4.8 and necessitas and Qt was much slower than now to integrate new features provided by mobile devices. Some features like DPI retrieving wasn't correctly implemented so because it was a blocker for us, we fixed it by calling the native API on Android.
  
  
  
  
  
2016-06-24 15:00 GMT+02:00 Robert Iakobashvili http://corobe...@gmail.com]>:On Tue, Jun 21, 2016 

Re: [Interest] 5.8 Features?

[Jason H]

That's exactly my worry too. So far, I've had a number of mobile devs like you 
agree with me, but how do we take it to the next level and get the Qt company 
on board and actually do something?

What's irritating me is that there aren't any other killer features competing. 
It also seems that these issues could be fixed relatively quickly if the trolls 
were to focus on it. I think adding something like 3D is much more complicated 
and affects far fewer people. 
 
Qt 5.7 added two mobile features:
- NFC (Android) (Also reported as a 5.6 feature)
- Android Services 

While any addition is good, I find it hard that NFC was more missed that 
notifications.  Could we possibly come up with a "mobile features" priority 
list and help focus what gets delivered?
Say, with a minimum of 1 (or more) feature(s) per X.Y release? 



---
Sent: Monday, June 27, 2016 at 11:29 AM
From: "Daniel França" 
To: "interest@qt-project.org" 
Subject: Re: [Interest] 5.8 Features?

+1
I love Qt, but I'd tried to implement 3 mobile apps using Qt, and I always fall 
in some sort of limitation that annoys me.
Like you said, pretty basic things like the video recording parameters.

And I look into the next steps and I don't see any much effort on that area, 
this was the main reason I'd cancel my subscription.

Mobile seems more like a second class citizen.
 

On Fri, 24 Jun 2016 at 18:02 Jason H  wrote:

6 months of latency would be great.
But the things I talk about are pretty basic on mobile:
- Foreground/background lifecycle events,
- Screen wake locks,
- Notifications (local / remote)
 
These have been aound since before Qt targeted mobile and are sorely STILL 
missing from Qt.
 
Things upcoming that I wouldn't complain about having to implement myself:
- Fingerprint scanning
As this is relatively new for Android and iOS platforms. Though the Atrix 
(2010) had a fingerprint scanner, but only Android 6 had a platform API. iPhone 
had it as of the 5S. 
 
It's like Qt is on mobile only if you want to put things on the screen and do 
AJAX. But if you really want to do anything really "mobile" you're on your own. 
We still can't control the video recording parameters on iOS (Thanks to my 
company, it will land in 5.6.2 -- was supposed to land in 5.6.1). Qt can only 
really be accurately described to be a Cross-platform UI on mobile. Outside of 
that, you're writing Java and Obj-C. So call it cross-platform for mobile is a 
stretch. I urging Qt to focus on eliminating the asterisks, so it's proper 
Mobile (capital M) platform. 
 
With that said though, Qt's abstraction of various platform services is a 
godsend. The fact that ReactNative gives you access to AVFoundation doesn't do 
a whole lot when you have to write ReactNative that targets AVFoundation and 
more code to target android.media SDK and handle the intricacies of both in 
your own code base. So I think the Qt approach is right. I just want more of 
it. :-)
 
 
Sent: Friday, June 24, 2016 at 9:26 AM
From: "Xavier Bigand" 
To: "Robert Iakobashvili" 
Cc: interest 

Subject: Re: [Interest] 5.8 Features?

Like you said I think that the iOS and Android progress too fast and on an 
other cadence than Qt.
We should not forget that Qt has to create a unified cross platform API, that 
is necessary harder than creating a new one for one platform.
 
I think that a latency of 6 months to a year is still reasonable for Qt 
depending on how it fall with releases.
 
In my opinion if you need something faster, you may have to consider to 
implement features your self. We started our application with 4.8 and 
necessitas and Qt was much slower than now to integrate new features provided 
by mobile devices. Some features like DPI retrieving wasn't correctly 
implemented so because it was a blocker for us, we fixed it by calling the 
native API on Android.
 
 
 
 
 
2016-06-24 15:00 GMT+02:00 Robert Iakobashvili 
http://corobe...@gmail.com]>:On Tue, Jun 21, 2016 at 10:55 
PM, Jason H http://jh...@gmx.com]> wrote:
> I feel like the last few releases have been run by the trolls, and not the 
> users of Qt. I was hoping open governance would enable the community to 
> direct Qt development, but I seem to have misinterpreted what it means. I'm 
> looking for what's going into 5.8.. not much listed on the releases page.
>
> I'd like to suggest that mobile get some much needed love.
> - Application state transitions; Foreground, background
> - Background processing API
> - Screen wake lock API
> - In-app Notifications: local, remote
>
> While I have those characterized as "mobile" there are things like 
> notifications occurring on desktop platforms.
>
> Any thoughts?
>

Agree with Jason that mobile support needs more love
and adding "Native, native, native ..."

Howeve

Re: [Interest] 5.8 Features?

[Daniel França]

+1
I love Qt, but I'd tried to implement 3 mobile apps using Qt, and I always
fall in some sort of limitation that annoys me.
Like you said, pretty basic things like the video recording parameters.

And I look into the next steps and I don't see any much effort on that
area, this was the main reason I'd cancel my subscription.

Mobile seems more like a second class citizen.

On Fri, 24 Jun 2016 at 18:02 Jason H  wrote:

> 6 months of latency would be great.
> But the things I talk about are pretty basic on mobile:
> - Foreground/background lifecycle events,
> - Screen wake locks,
> - Notifications (local / remote)
>
> These have been aound since before Qt targeted mobile and are sorely STILL
> missing from Qt.
>
> Things upcoming that I wouldn't complain about having to implement myself:
> - Fingerprint scanning
> As this is relatively new for Android and iOS platforms. Though the Atrix
> (2010) had a fingerprint scanner, but only Android 6 had a platform API.
> iPhone had it as of the 5S.
>
> It's like Qt is on mobile only if you want to put things on the screen and
> do AJAX. But if you really want to do anything really "mobile" you're on
> your own. We still can't control the video recording parameters on iOS
> (Thanks to my company, it will land in 5.6.2 -- was supposed to land in
> 5.6.1). Qt can only really be accurately described to be a Cross-platform
> UI on mobile. Outside of that, you're writing Java and Obj-C. So call it
> cross-platform for mobile is a stretch. I urging Qt to focus on eliminating
> the asterisks, so it's proper Mobile (capital M) platform.
>
> With that said though, Qt's abstraction of various platform services is a
> godsend. The fact that ReactNative gives you access to AVFoundation doesn't
> do a whole lot when you have to write ReactNative that targets AVFoundation
> and more code to target android.media SDK and handle the intricacies of
> both in your own code base. So I think the Qt approach is right. I just
> want more of it. :-)
>
>
> *Sent:* Friday, June 24, 2016 at 9:26 AM
> *From:* "Xavier Bigand" 
> *To:* "Robert Iakobashvili" 
> *Cc:* interest 
>
> *Subject:* Re: [Interest] 5.8 Features?
> Like you said I think that the iOS and Android progress too fast and on an
> other cadence than Qt.
> We should not forget that Qt has to create a unified cross platform API,
> that is necessary harder than creating a new one for one platform.
>
> I think that a latency of 6 months to a year is still reasonable for Qt
> depending on how it fall with releases.
>
> In my opinion if you need something faster, you may have to consider to
> implement features your self. We started our application with 4.8 and
> necessitas and Qt was much slower than now to integrate new features
> provided by mobile devices. Some features like DPI retrieving wasn't
> correctly implemented so because it was a blocker for us, we fixed it by
> calling the native API on Android.
>
>
>
>
>
> 2016-06-24 15:00 GMT+02:00 Robert Iakobashvili :
>>
>> On Tue, Jun 21, 2016 at 10:55 PM, Jason H  wrote:
>> > I feel like the last few releases have been run by the trolls, and not
>> the users of Qt. I was hoping open governance would enable the community to
>> direct Qt development, but I seem to have misinterpreted what it means. I'm
>> looking for what's going into 5.8.. not much listed on the releases page.
>> >
>> > I'd like to suggest that mobile get some much needed love.
>> > - Application state transitions; Foreground, background
>> > - Background processing API
>> > - Screen wake lock API
>> > - In-app Notifications: local, remote
>> >
>> > While I have those characterized as "mobile" there are things like
>> notifications occurring on desktop platforms.
>> >
>> > Any thoughts?
>> >
>>
>> Agree with Jason that mobile support needs more love
>> and adding "Native, native, native ..."
>>
>> However, it could be that progress made at iOS and Android side is too
>> fast and
>> our expectations from Qt are too high?
>>
>> As any cross-platform framework Qt has its limitations.
>> Still, it has good integration points to allow additions of native code.
>>
>> jm4c to add.
>>
>> Kind regards,
>> Robert
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>
>
>
> --
> Xavier
> ___ Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[ekke]

Am 24.06.16 um 21:59 schrieb Jason H:
> I've solved these, to various exents, or Android and iOS.
> I would share my code as longas everyone promises to not laughs at my
> code. I do not know what is "best" or everyone. I just wrote what I
> had to fill the requirement I had. 
>  
>  
sharing code is always great
and if someone can do it better, getting patches or comments at github
helps to make own code better
this is also reason why I'm publishing code: to hear from other devs
what is wrong or can be done better
> *Sent:* Friday, June 24, 2016 at 12:20 PM
> *From:* ekke 
> *To:* interest@qt-project.org
> *Subject:* Re: [Interest] 5.8 Features?
> Am 24.06.16 um 18:02 schrieb Jason H:
>
> 6 months of latency would be great.
> But the things I talk about are pretty basic on mobile:
> - Foreground/background lifecycle events,
> - Screen wake locks,
> - Notifications (local / remote)
>  
> These have been aound since before Qt targeted mobile and are
> sorely STILL missing from Qt.
>  
> Things upcoming that I wouldn't complain about having to implement
> myself:
> - Fingerprint scanning
> As this is relatively new for Android and iOS platforms. Though
> the Atrix (2010) had a fingerprint scanner, but only Android 6
> had a platform API. iPhone had it as of the 5S. 
>  
> It's like Qt is on mobile only if you want to put things on the
> screen and do AJAX. But if you really want to do anything really
> "mobile" you're on your own. We still can't control the video
> recording parameters on iOS (Thanks to my company, it will land in
> 5.6.2 -- was supposed to land in 5.6.1). Qt can only really be
> accurately described to be a Cross-platform UI on mobile. Outside
> of that, you're writing Java and Obj-C. So call it cross-platform
> for mobile is a stretch. I urging Qt to focus on eliminating the
> asterisks, so it's proper Mobile (capital M) platform. 
>  
> With that said though, Qt's abstraction of various platform
> services is a godsend. The fact that ReactNative gives you access
> to AVFoundation doesn't do a whole lot when you have to write
> ReactNative that targets AVFoundation and more code to target
> android.media SDK and handle the intricacies of both in your own
> code base. So I think the Qt approach is right. I just want more
> of it. :-)
>  
>
> +1
>
> another point: I think that there are many developers out there
> already implementing common missing features in Java and ObjectiveC
>
> would be great to collect and exchange this to help each other - don't
> know where's the best place and it should be promoted by Qt
>
>  
> *Sent:* Friday, June 24, 2016 at 9:26 AM
> *From:* "Xavier Bigand" 
> *To:* "Robert Iakobashvili" 
> *Cc:* interest 
> *Subject:* Re: [Interest] 5.8 Features?
> Like you said I think that the iOS and Android progress too fast
> and on an other cadence than Qt.
> We should not forget that Qt has to create a unified cross
> platform API, that is necessary harder than creating a new one for
> one platform.
>  
> I think that a latency of 6 months to a year is still reasonable
> for Qt depending on how it fall with releases.
>  
> In my opinion if you need something faster, you may have to
> consider to implement features your self. We started our
> application with 4.8 and necessitas and Qt was much slower than
> now to integrate new features provided by mobile devices. Some
> features like DPI retrieving wasn't correctly implemented so
> because it was a blocker for us, we fixed it by calling the native
> API on Android.
>  
>  
>  
>  
>  
> 2016-06-24 15:00 GMT+02:00 Robert Iakobashvili :
>
> On Tue, Jun 21, 2016 at 10:55 PM, Jason H  wrote:
> > I feel like the last few releases have been run by the
> trolls, and not the users of Qt. I was hoping open governance
> would enable the community to direct Qt development, but I
> seem to have misinterpreted what it means. I'm looking for
> what's going into 5.8.. not much listed on the releases page.
> >
> > I'd like to suggest that mobile get some much needed love.
> > - Application state transitions; Foreground, background
> > - Background processing API
> > - Screen wake lock API
> > - In-app Notifications: local, remote
> >
> &

Re: [Interest] 5.8 Features?

[Kevin Mcintyre]

I had this issue after I installed QT a couple of times (the first time I
didn't install with version with Android)

So looking back on my notes I sent to "Interest" - I resolved

"via export LD_LIBRARY_PATH=/home/ubuntu/Qt/5.6/gcc_64/lib in my .bashrc
file."

On Fri, Jun 24, 2016 at 12:59 PM, Jason H  wrote:

> I've solved these, to various exents, or Android and iOS.
> I would share my code as longas everyone promises to not laughs at my
> code. I do not know what is "best" or everyone. I just wrote what I had to
> fill the requirement I had.
>
>
> *Sent:* Friday, June 24, 2016 at 12:20 PM
> *From:* ekke 
> *To:* interest@qt-project.org
>
> *Subject:* Re: [Interest] 5.8 Features?
> Am 24.06.16 um 18:02 schrieb Jason H:
>
> 6 months of latency would be great.
> But the things I talk about are pretty basic on mobile:
> - Foreground/background lifecycle events,
> - Screen wake locks,
> - Notifications (local / remote)
>
> These have been aound since before Qt targeted mobile and are sorely STILL
> missing from Qt.
>
> Things upcoming that I wouldn't complain about having to implement myself:
> - Fingerprint scanning
> As this is relatively new for Android and iOS platforms. Though the Atrix
> (2010) had a fingerprint scanner, but only Android 6 had a platform API.
> iPhone had it as of the 5S.
>
> It's like Qt is on mobile only if you want to put things on the screen and
> do AJAX. But if you really want to do anything really "mobile" you're on
> your own. We still can't control the video recording parameters on iOS
> (Thanks to my company, it will land in 5.6.2 -- was supposed to land in
> 5.6.1). Qt can only really be accurately described to be a Cross-platform
> UI on mobile. Outside of that, you're writing Java and Obj-C. So call it
> cross-platform for mobile is a stretch. I urging Qt to focus on eliminating
> the asterisks, so it's proper Mobile (capital M) platform.
>
> With that said though, Qt's abstraction of various platform services is a
> godsend. The fact that ReactNative gives you access to AVFoundation doesn't
> do a whole lot when you have to write ReactNative that targets AVFoundation
> and more code to target android.media SDK and handle the intricacies of
> both in your own code base. So I think the Qt approach is right. I just
> want more of it. :-)
>
>
> +1
>
> another point: I think that there are many developers out there already
> implementing common missing features in Java and ObjectiveC
>
> would be great to collect and exchange this to help each other - don't
> know where's the best place and it should be promoted by Qt
>
>
> *Sent:* Friday, June 24, 2016 at 9:26 AM
> *From:* "Xavier Bigand" 
> <http://flamaros.xav...@gmail.com>
> *To:* "Robert Iakobashvili" 
> <http://corobe...@gmail.com>
> *Cc:* interest  <http://interest@qt-project.org>
> *Subject:* Re: [Interest] 5.8 Features?
> Like you said I think that the iOS and Android progress too fast and on an
> other cadence than Qt.
> We should not forget that Qt has to create a unified cross platform API,
> that is necessary harder than creating a new one for one platform.
>
> I think that a latency of 6 months to a year is still reasonable for Qt
> depending on how it fall with releases.
>
> In my opinion if you need something faster, you may have to consider to
> implement features your self. We started our application with 4.8 and
> necessitas and Qt was much slower than now to integrate new features
> provided by mobile devices. Some features like DPI retrieving wasn't
> correctly implemented so because it was a blocker for us, we fixed it by
> calling the native API on Android.
>
>
>
>
>
> 2016-06-24 15:00 GMT+02:00 Robert Iakobashvili :
>>
>> On Tue, Jun 21, 2016 at 10:55 PM, Jason H  wrote:
>> > I feel like the last few releases have been run by the trolls, and not
>> the users of Qt. I was hoping open governance would enable the community to
>> direct Qt development, but I seem to have misinterpreted what it means. I'm
>> looking for what's going into 5.8.. not much listed on the releases page.
>> >
>> > I'd like to suggest that mobile get some much needed love.
>> > - Application state transitions; Foreground, background
>> > - Background processing API
>> > - Screen wake lock API
>> > - In-app Notifications: local, remote
>> >
>> > While I have those characterized as "mobile" there are things like
>> notifications occurring on desktop platforms.
>> >
>> > Any thoughts?
>> >

Re: [Interest] 5.8 Features?

[Jason H]

I've solved these, to various exents, or Android and iOS.

I would share my code as longas everyone promises to not laughs at my code. I do not know what is "best" or everyone. I just wrote what I had to fill the requirement I had. 

 

 



Sent: Friday, June 24, 2016 at 12:20 PM
From: ekke 
To: interest@qt-project.org
Subject: Re: [Interest] 5.8 Features?



Am 24.06.16 um 18:02 schrieb Jason H:




6 months of latency would be great.

But the things I talk about are pretty basic on mobile:

- Foreground/background lifecycle events,

- Screen wake locks,

- Notifications (local / remote)

 

These have been aound since before Qt targeted mobile and are sorely STILL missing from Qt.

 

Things upcoming that I wouldn't complain about having to implement myself:

- Fingerprint scanning

As this is relatively new for Android and iOS platforms. Though the Atrix (2010) had a fingerprint scanner, but only Android 6 had a platform API. iPhone had it as of the 5S. 

 

It's like Qt is on mobile only if you want to put things on the screen and do AJAX. But if you really want to do anything really "mobile" you're on your own. We still can't control the video recording parameters on iOS (Thanks to my company, it will land in 5.6.2 -- was supposed to land in 5.6.1). Qt can only really be accurately described to be a Cross-platform UI on mobile. Outside of that, you're writing Java and Obj-C. So call it cross-platform for mobile is a stretch. I urging Qt to focus on eliminating the asterisks, so it's proper Mobile (capital M) platform. 

 

With that said though, Qt's abstraction of various platform services is a godsend. The fact that ReactNative gives you access to AVFoundation doesn't do a whole lot when you have to write ReactNative that targets AVFoundation and more code to target android.media SDK and handle the intricacies of both in your own code base. So I think the Qt approach is right. I just want more of it. :-)

 



+1

another point: I think that there are many developers out there already implementing common missing features in Java and ObjectiveC

would be great to collect and exchange this to help each other - don't know where's the best place and it should be promoted by Qt



 

Sent: Friday, June 24, 2016 at 9:26 AM
From: "Xavier Bigand" 
To: "Robert Iakobashvili" 
Cc: interest 
Subject: Re: [Interest] 5.8 Features?




Like you said I think that the iOS and Android progress too fast and on an other cadence than Qt.
We should not forget that Qt has to create a unified cross platform API, that is necessary harder than creating a new one for one platform.

 

I think that a latency of 6 months to a year is still reasonable for Qt depending on how it fall with releases.

 

In my opinion if you need something faster, you may have to consider to implement features your self. We started our application with 4.8 and necessitas and Qt was much slower than now to integrate new features provided by mobile devices. Some features like DPI retrieving wasn't correctly implemented so because it was a blocker for us, we fixed it by calling the native API on Android.

 

 

 

 


 
2016-06-24 15:00 GMT+02:00 Robert Iakobashvili <corobe...@gmail.com>:

On Tue, Jun 21, 2016 at 10:55 PM, Jason H <jh...@gmx.com> wrote:
> I feel like the last few releases have been run by the trolls, and not the users of Qt. I was hoping open governance would enable the community to direct Qt development, but I seem to have misinterpreted what it means. I'm looking for what's going into 5.8.. not much listed on the releases page.
>
> I'd like to suggest that mobile get some much needed love.
> - Application state transitions; Foreground, background
> - Background processing API
> - Screen wake lock API
> - In-app Notifications: local, remote
>
> While I have those characterized as "mobile" there are things like notifications occurring on desktop platforms.
>
> Any thoughts?
>

Agree with Jason that mobile support needs more love
and adding "Native, native, native ..."

However, it could be that progress made at iOS and Android side is too fast and
our expectations from Qt are too high?

As any cross-platform framework Qt has its limitations.
Still, it has good integration points to allow additions of native code.

jm4c to add.

Kind regards,
Robert
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

 

 
--


Xavier


___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest




 

 
 

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest



 

_

Re: [Interest] 5.8 Features?

[ekke]

Am 24.06.16 um 18:02 schrieb Jason H:
> 6 months of latency would be great.
> But the things I talk about are pretty basic on mobile:
> - Foreground/background lifecycle events,
> - Screen wake locks,
> - Notifications (local / remote)
>  
> These have been aound since before Qt targeted mobile and are sorely
> STILL missing from Qt.
>  
> Things upcoming that I wouldn't complain about having to implement myself:
> - Fingerprint scanning
> As this is relatively new for Android and iOS platforms. Though the
> Atrix (2010) had a fingerprint scanner, but only Android 6 had a
> platform API. iPhone had it as of the 5S. 
>  
> It's like Qt is on mobile only if you want to put things on the screen
> and do AJAX. But if you really want to do anything really "mobile"
> you're on your own. We still can't control the video recording
> parameters on iOS (Thanks to my company, it will land in 5.6.2 -- was
> supposed to land in 5.6.1). Qt can only really be accurately described
> to be a Cross-platform UI on mobile. Outside of that, you're writing
> Java and Obj-C. So call it cross-platform for mobile is a stretch. I
> urging Qt to focus on eliminating the asterisks, so it's proper Mobile
> (capital M) platform. 
>  
> With that said though, Qt's abstraction of various platform services
> is a godsend. The fact that ReactNative gives you access to
> AVFoundation doesn't do a whole lot when you have to write ReactNative
> that targets AVFoundation and more code to target android.media
> SDK and handle the intricacies of both in your own code base. So I
> think the Qt approach is right. I just want more of it. :-)
>  
+1

another point: I think that there are many developers out there already
implementing common missing features in Java and ObjectiveC

would be great to collect and exchange this to help each other - don't
know where's the best place and it should be promoted by Qt
>  
> *Sent:* Friday, June 24, 2016 at 9:26 AM
> *From:* "Xavier Bigand" 
> *To:* "Robert Iakobashvili" 
> *Cc:* interest 
> *Subject:* Re: [Interest] 5.8 Features?
> Like you said I think that the iOS and Android progress too fast and
> on an other cadence than Qt.
> We should not forget that Qt has to create a unified cross platform
> API, that is necessary harder than creating a new one for one platform.
>  
> I think that a latency of 6 months to a year is still reasonable for
> Qt depending on how it fall with releases.
>  
> In my opinion if you need something faster, you may have to consider
> to implement features your self. We started our application with 4.8
> and necessitas and Qt was much slower than now to integrate new
> features provided by mobile devices. Some features like DPI retrieving
> wasn't correctly implemented so because it was a blocker for us, we
> fixed it by calling the native API on Android.
>  
>  
>  
>  
>  
> 2016-06-24 15:00 GMT+02:00 Robert Iakobashvili :
>
> On Tue, Jun 21, 2016 at 10:55 PM, Jason H  wrote:
> > I feel like the last few releases have been run by the trolls,
> and not the users of Qt. I was hoping open governance would enable
> the community to direct Qt development, but I seem to have
> misinterpreted what it means. I'm looking for what's going into
> 5.8.. not much listed on the releases page.
> >
> > I'd like to suggest that mobile get some much needed love.
> > - Application state transitions; Foreground, background
> > - Background processing API
> > - Screen wake lock API
> > - In-app Notifications: local, remote
> >
> > While I have those characterized as "mobile" there are things
> like notifications occurring on desktop platforms.
> >
> > Any thoughts?
> >
>
> Agree with Jason that mobile support needs more love
> and adding "Native, native, native ..."
>
> However, it could be that progress made at iOS and Android side is
> too fast and
> our expectations from Qt are too high?
>
> As any cross-platform framework Qt has its limitations.
> Still, it has good integration points to allow additions of native
> code.
>
> jm4c to add.
>
> Kind regards,
> Robert
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>  
>  
> -- 
> Xavier
> ___ Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest



___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Jason H]

6 months of latency would be great.

But the things I talk about are pretty basic on mobile:

- Foreground/background lifecycle events,

- Screen wake locks,

- Notifications (local / remote)

 

These have been aound since before Qt targeted mobile and are sorely STILL missing from Qt.

 

Things upcoming that I wouldn't complain about having to implement myself:

- Fingerprint scanning

As this is relatively new for Android and iOS platforms. Though the Atrix (2010) had a fingerprint scanner, but only Android 6 had a platform API. iPhone had it as of the 5S. 

 

It's like Qt is on mobile only if you want to put things on the screen and do AJAX. But if you really want to do anything really "mobile" you're on your own. We still can't control the video recording parameters on iOS (Thanks to my company, it will land in 5.6.2 -- was supposed to land in 5.6.1). Qt can only really be accurately described to be a Cross-platform UI on mobile. Outside of that, you're writing Java and Obj-C. So call it cross-platform for mobile is a stretch. I urging Qt to focus on eliminating the asterisks, so it's proper Mobile (capital M) platform. 

 

With that said though, Qt's abstraction of various platform services is a godsend. The fact that ReactNative gives you access to AVFoundation doesn't do a whole lot when you have to write ReactNative that targets AVFoundation and more code to target android.media SDK and handle the intricacies of both in your own code base. So I think the Qt approach is right. I just want more of it. :-)

 

 

Sent: Friday, June 24, 2016 at 9:26 AM
From: "Xavier Bigand" 
To: "Robert Iakobashvili" 
Cc: interest 
Subject: Re: [Interest] 5.8 Features?




Like you said I think that the iOS and Android progress too fast and on an other cadence than Qt.
We should not forget that Qt has to create a unified cross platform API, that is necessary harder than creating a new one for one platform.

 

I think that a latency of 6 months to a year is still reasonable for Qt depending on how it fall with releases.

 

In my opinion if you need something faster, you may have to consider to implement features your self. We started our application with 4.8 and necessitas and Qt was much slower than now to integrate new features provided by mobile devices. Some features like DPI retrieving wasn't correctly implemented so because it was a blocker for us, we fixed it by calling the native API on Android.

 

 

 

 


 
2016-06-24 15:00 GMT+02:00 Robert Iakobashvili <corobe...@gmail.com>:

On Tue, Jun 21, 2016 at 10:55 PM, Jason H <jh...@gmx.com> wrote:
> I feel like the last few releases have been run by the trolls, and not the users of Qt. I was hoping open governance would enable the community to direct Qt development, but I seem to have misinterpreted what it means. I'm looking for what's going into 5.8.. not much listed on the releases page.
>
> I'd like to suggest that mobile get some much needed love.
> - Application state transitions; Foreground, background
> - Background processing API
> - Screen wake lock API
> - In-app Notifications: local, remote
>
> While I have those characterized as "mobile" there are things like notifications occurring on desktop platforms.
>
> Any thoughts?
>

Agree with Jason that mobile support needs more love
and adding "Native, native, native ..."

However, it could be that progress made at iOS and Android side is too fast and
our expectations from Qt are too high?

As any cross-platform framework Qt has its limitations.
Still, it has good integration points to allow additions of native code.

jm4c to add.

Kind regards,
Robert
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

 

 
--


Xavier


___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest



___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Xavier Bigand]

Like you said I think that the iOS and Android progress too fast and on an
other cadence than Qt.
We should not forget that Qt has to create a unified cross platform API,
that is necessary harder than creating a new one for one platform.

I think that a latency of 6 months to a year is still reasonable for Qt
depending on how it fall with releases.

In my opinion if you need something faster, you may have to consider to
implement features your self. We started our application with 4.8 and
necessitas and Qt was much slower than now to integrate new features
provided by mobile devices. Some features like DPI retrieving wasn't
correctly implemented so because it was a blocker for us, we fixed it by
calling the native API on Android.





2016-06-24 15:00 GMT+02:00 Robert Iakobashvili :

> On Tue, Jun 21, 2016 at 10:55 PM, Jason H  wrote:
> > I feel like the last few releases have been run by the trolls, and not
> the users of Qt. I was hoping open governance would enable the community to
> direct Qt development, but I seem to have misinterpreted what it means. I'm
> looking for what's going into 5.8.. not much listed on the releases page.
> >
> > I'd like to suggest that mobile get some much needed love.
> > - Application state transitions; Foreground, background
> > - Background processing API
> > - Screen wake lock API
> > - In-app Notifications: local, remote
> >
> > While I have those characterized as "mobile" there are things like
> notifications occurring on desktop platforms.
> >
> > Any thoughts?
> >
>
> Agree with Jason that mobile support needs more love
> and adding "Native, native, native ..."
>
> However, it could be that progress made at iOS and Android side is too
> fast and
> our expectations from Qt are too high?
>
> As any cross-platform framework Qt has its limitations.
> Still, it has good integration points to allow additions of native code.
>
> jm4c to add.
>
> Kind regards,
> Robert
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>



-- 
Xavier
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Robert Iakobashvili]

On Tue, Jun 21, 2016 at 10:55 PM, Jason H  wrote:
> I feel like the last few releases have been run by the trolls, and not the 
> users of Qt. I was hoping open governance would enable the community to 
> direct Qt development, but I seem to have misinterpreted what it means. I'm 
> looking for what's going into 5.8.. not much listed on the releases page.
>
> I'd like to suggest that mobile get some much needed love.
> - Application state transitions; Foreground, background
> - Background processing API
> - Screen wake lock API
> - In-app Notifications: local, remote
>
> While I have those characterized as "mobile" there are things like 
> notifications occurring on desktop platforms.
>
> Any thoughts?
>

Agree with Jason that mobile support needs more love
and adding "Native, native, native ..."

However, it could be that progress made at iOS and Android side is too fast and
our expectations from Qt are too high?

As any cross-platform framework Qt has its limitations.
Still, it has good integration points to allow additions of native code.

jm4c to add.

Kind regards,
Robert
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Sze Howe Koh]

On 22 June 2016 at 21:39, Jason H  wrote:
>
> > Subject: Re: [Interest] 5.8 Features?
> >
> > On 22 June 2016 at 09:34, Thiago Macieira  wrote:
> > >
> > > On terça-feira, 21 de junho de 2016 22:55:07 PDT Jason H wrote:
> > > > I feel like the last few releases have been run by the trolls, and not 
> > > > the
> > > > users of Qt. I was hoping open governance would enable the community to
> > > > direct Qt development, but I seem to have misinterpreted what it means.
> >
> > See https://wiki.qt.io/The_Qt_Governance_Model
> >
> > "Open governance" means that all members of the community can raise
> > proposals and vote on them. It is also a meritocratic system (as
> > opposed to democratic), which means more weight is given to members of
> > higher rank. Put simply, rank is gained through contributions and
> > commitment to the Qt Project.
>
> Where and when does this voting occur?

Where: Often at the Development mailing list:
http://lists.qt-project.org/mailman/listinfo/development
When: Whenever someone posts a proposal.

Examples:
* Proposal for choosing the list of platforms to support for Qt 5.8:
http://thread.gmane.org/gmane.comp.lib.qt.devel/24938/focus=24965
* Proposal for polishing and releasing QtSingleApplication:
http://thread.gmane.org/gmane.comp.lib.qt.devel/26279/focus=26358

My apologies, "voting" was the wrong word to use, as Thiago explained
in his email. Rather than counting votes, the process is a
discussion/debate where the proposals with the highest merit get
accepted.


> I've been vocal about improving Qt on mobile since mobile was an option. I've 
> been hardcore on the shortcomings for about 20 months. During that time, I 
> saw 5.6 get released, 5.7 get released at the same time as 5.6.1, and a lot 
> of meaningless (to me) modules added. And now 5.8 is only 1.5 months from 
> 5.7? What_the_hell? I'd like to see Qt complete it's mobile initiative.
>
> As for contributing, the past 20 months I've been under _multiple_ commercial 
> licenses, one that was paying for a Desktop just to use Qt Charts. I think 
> that's pretty material.

First of all, thank you for supporting Qt's development by purchasing
commercial licenses.

I'd imagine that funds from commercial licenses are normally allocated
to the development and maintenance of the entire Qt framework. Start a
conversation with your sales rep, and see if you can request greater
focus on specific areas. (Disclaimer: I'm not affiliated with the Qt
Company and I don't speak on their behalf, so please correct me if
this advice is inappropriate.)

Please remember: The Qt Company's commercial decision making process
and the Qt Project's Open Governance are _not_ the same thing. In the
context of Open Governance, "contribution" refers mainly to code
contributions. I don't have insight into the commercial decision
making process.

Anyway, as Tuukka pointed out in his email, Qt is making steady
progress in the mobile world (although "mobile" is still very broad,
and it sounds like the progress to date isn't in the areas that you're
interested in). There are multiple ways to get the mobile features
that you want, sooner:

* The open source community way: Get involved personally. Test,
review, and provide feedback for relevant patches, e.g.
https://codereview.qt-project.org/#/c/149602/ . If a patch gets
neglected, ping the list for more attention. Even better, write and
submit your own patches.
* The commercial customer way: Talk to your Qt Company sales rep
directly to try to influence their decisions.
* Use a ready-made 3rd party toolkit to complement official Qt
features, e.g. V-Play: http://v-play.net/
* Get 3rd party professionals on board to implement the specific
features that you want, e.g.
https://woboq.com/blog/qdockwidget-changes-in-56.html -- "You can hire
Woboq to fix your own Qt bugs or implement new features inside Qt"


Regards,
Sze-Howe
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[ekke]

Hi Maurice,
I'll go on and will try to find solutions and to write blogs / sample
apps / bugreports ...
and discuss here

having time is also an issue for me - working as an independent developer

hopefully others will also make their solutions public.

coming from BlackBerry Cascades it's not always easy to figure out how
it works in Android via JNI and iOS / ObjectiveC
I'm using Qt to avoid this ;-)

so for the moment I think it will consume much time to make apps running
for my customers - don't know when I'll reach a point to make contributions

ekke

Am 23.06.16 um 09:52 schrieb Maurice Kalinowski:
>
> Hi Ekke,
>
>  
>
> Thx for all the effort you put into the mobile platforms for Qt,
> evangelizing as well as sharing your knowledge on it.
>
>  
>
> Even when the items mentioned are not on the immediate roadmap as
> such, why not take the next step and consider creating a crossplatform
> API on your own, developed on the playground? Based on your knowledge
> of using those features, you seem like a natural candidate for this.
>
>  
>
> This might be a good place to start, you can ask the community and
> contributors to check for API consistency and if there are others
> needing those features as well, there is a likelihood that you will
> get feedback on those, maybe even contributions?
>
>  
>
> Having time is always an issue, so it is for the others. So, be
> proactive and start the initiative. There is no need to be done with
> it for FF of 5.8. If you are afraid of not being able to maintain this
> in the future, somebody else might take over but needs a head-start.
> After all, this would be on the playground.
>
>  
>
> Maurice
>
>  
>
>  
>
> *From:*ekke [mailto:e...@ekkes-corner.org]
> *Sent:* Thursday, June 23, 2016 7:15 AM
> *To:* Maurice Kalinowski ; Matthias
> Degenkolb ; interest@qt-project.org
> *Subject:* Re: [Interest] 5.8 Features?
>
>  
>
> thx Maurice,
>
> Am 22.06.16 um 12:22 schrieb Maurice Kalinowski:
>
> > Highest prio from my personal perspective:
>
> > >> - Background processing API
>
> > >> - In-app Notifications: local, remote
>
> > + add Windows Store to Qt Purchasing module
>
> there's more missing:
> - avoid flicker for android apps out-of-the-box
> - easy way to 'share' content with/from other apps (Intents, Deep
> Linking) Android, iOS
> such common use-cases should be abstracted and available via Qt API
>
> coming from BlackBerry 10 Cascades/QML APP Development I'm astonished
> how many common mobile tasks are missing
>
> I want to motivate my enterprise customers to use Qt for mobile
> x-platform development
> they're comparing with Xamarin, Ionic, Angular ...
>
> I still believe Qt is the best solution for mobile x platform and hope
> there will be really progress on this
> esp. after providing QtQuickControls2 Material style for great looking
> apps
>
> ekke
>
>  
>
> https://codereview.qt-project.org/#/c/149602/
>
> https://codereview.qt-project.org/#/c/162992/
>
>  
>
> ;)
>
>  
>
> Maurice
>
>  
>
>  
>
> *From:*Interest
> [mailto:interest-bounces+maurice.kalinowski=qt...@qt-project.org]
> *On Behalf Of *Matthias Degenkolb via Interest
> *Sent:* Wednesday, June 22, 2016 11:25 AM
> *To:* ekke  <mailto:e...@ekkes-corner.org>
> *Cc:* interest@qt-project.org <mailto:interest@qt-project.org>
> *Subject:* Re: [Interest] 5.8 Features?
>
>  
>
> I fully agree to ekke's and Jason's wishes. The features mentioned
> are all topics I also miss urgently since our first app
> development tests with Qt ..
>
> Not having cross-platform access to those "standard" mechanisms
> for mobile OS really makes me wonder whether my next projects will
> be based on Qt ...
>
>  
>
> Highest prio from my personal perspective:
>
> >> - Background processing API
> >> - In-app Notifications: local, remote
>
> + add Windows Store to Qt Purchasing module
>
>  
>
>  
>
> 2016-06-22 10:45 GMT+02:00 ekke  <mailto:e...@ekkes-corner.org>>:
>
> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
>
> > Den 21-06-2016 kl. 22:55 skrev Jason H:
> >> I feel like the last few releases have been run by the
> trolls, and
> >> not the users of Qt. I was hoping open governance would
> enable the
> >> community to direct Qt development, but I seem to have
> misi

Re: [Interest] 5.8 Features?

[Maurice Kalinowski]

Hi Ekke,

Thx for all the effort you put into the mobile platforms for Qt, evangelizing 
as well as sharing your knowledge on it.

Even when the items mentioned are not on the immediate roadmap as such, why not 
take the next step and consider creating a crossplatform API on your own, 
developed on the playground? Based on your knowledge of using those features, 
you seem like a natural candidate for this.

This might be a good place to start, you can ask the community and contributors 
to check for API consistency and if there are others needing those features as 
well, there is a likelihood that you will get feedback on those, maybe even 
contributions?

Having time is always an issue, so it is for the others. So, be proactive and 
start the initiative. There is no need to be done with it for FF of 5.8. If you 
are afraid of not being able to maintain this in the future, somebody else 
might take over but needs a head-start. After all, this would be on the 
playground.

Maurice


From: ekke [mailto:e...@ekkes-corner.org]
Sent: Thursday, June 23, 2016 7:15 AM
To: Maurice Kalinowski ; Matthias Degenkolb 
; interest@qt-project.org
Subject: Re: [Interest] 5.8 Features?

thx Maurice,

Am 22.06.16 um 12:22 schrieb Maurice Kalinowski:
> Highest prio from my personal perspective:
> >> - Background processing API
> >> - In-app Notifications: local, remote
> + add Windows Store to Qt Purchasing module
there's more missing:
- avoid flicker for android apps out-of-the-box
- easy way to 'share' content with/from other apps (Intents, Deep Linking) 
Android, iOS
such common use-cases should be abstracted and available via Qt API

coming from BlackBerry 10 Cascades/QML APP Development I'm astonished how many 
common mobile tasks are missing

I want to motivate my enterprise customers to use Qt for mobile x-platform 
development
they're comparing with Xamarin, Ionic, Angular ...

I still believe Qt is the best solution for mobile x platform and hope there 
will be really progress on this
esp. after providing QtQuickControls2 Material style for great looking apps

ekke


https://codereview.qt-project.org/#/c/149602/
https://codereview.qt-project.org/#/c/162992/

;)

Maurice


From: Interest 
[mailto:interest-bounces+maurice.kalinowski=qt...@qt-project.org] On Behalf Of 
Matthias Degenkolb via Interest
Sent: Wednesday, June 22, 2016 11:25 AM
To: ekke <mailto:e...@ekkes-corner.org>
Cc: interest@qt-project.org<mailto:interest@qt-project.org>
Subject: Re: [Interest] 5.8 Features?

I fully agree to ekke's and Jason's wishes. The features mentioned are all 
topics I also miss urgently since our first app development tests with Qt ..
Not having cross-platform access to those "standard" mechanisms for mobile OS 
really makes me wonder whether my next projects will be based on Qt ...

Highest prio from my personal perspective:
>> - Background processing API
>> - In-app Notifications: local, remote
+ add Windows Store to Qt Purchasing module


2016-06-22 10:45 GMT+02:00 ekke 
mailto:e...@ekkes-corner.org>>:
Am 22.06.16 um 10:36 schrieb Bo Thorsen:
> Den 21-06-2016 kl. 22:55 skrev Jason H:
>> I feel like the last few releases have been run by the trolls, and
>> not the users of Qt. I was hoping open governance would enable the
>> community to direct Qt development, but I seem to have misinterpreted
>> what it means. I'm looking for what's going into 5.8.. not much
>> listed on the releases page.
>>
>> I'd like to suggest that mobile get some much needed love.
>> - Application state transitions; Foreground, background
>> - Background processing API
>> - Screen wake lock API
>> - In-app Notifications: local, remote
>>
>> While I have those characterized as "mobile" there are things like
>> notifications occurring on desktop platforms.
>>
>> Any thoughts?
>
> There's only one reason why you don't see more features for the mobile
> parts: There are not enough developers on it. And that's not because
> QtCompany is doing anything wrong, they just have their priorities
> different from what you have.
>
> Personally I don't care about mobile at all. I haven't had a mobile
> customer since 2011 and I don't see that changing. My focus is almost
> entirely on Linux embedded and Windows desktop. Those are the areas
> where a lot of applications are written.
>
> I'd love to see the mobile platforms thrive. But unless you Qt users
> start becoming Qt developers and contribute to it, I don't see that
> happening.
hmmm
the only reason for me to use Qt is mobile
using new Qt Quick Controls 2 Qt is a great platform for mobile app
development and I hope many new developers will start with Qt on mobile
to make this easier I'm writing exampl

Re: [Interest] 5.8 Features?

[ekke]

Am 23.06.16 um 08:57 schrieb Shawn Rutledge:
>> On 23 Jun 2016, at 07:15, ekke  wrote:
>>
>> thx Maurice,
>>
>> Am 22.06.16 um 12:22 schrieb Maurice Kalinowski:
 Highest prio from my personal perspective:
>> - Background processing API
>> - In-app Notifications: local, remote
 + add Windows Store to Qt Purchasing module
>> there's more missing:
>> - avoid flicker for android apps out-of-the-box
> What does that mean, just the initial appearance at startup? 
yep. would be great to start Android Apps without flicker by default.
Now I must follow instructions like this:
https://medium.com/@benlaud/complete-guide-to-make-a-splash-screen-for-your-qml-android-application-567ca3bc70af#.demzldbe9

>  My pet peeve is that startup of Qt Android apps takes too long, compared to 
> Java apps.  Ironically it's Java apps that are too slow on desktop platforms. 
>  So I just wish I had a modern Qt-based phone, so that there’s one copy of 
> the libs in memory already.  Apps would be small and fast.
yep :) How fast this can be I know from BlackBerry10 Cascades/Qt/QML
apps. But I have to look forward and provide x-platform apps for
Android/iOS (perhaps W10 later)
>
>> - easy way to 'share' content with/from other apps (Intents, Deep Linking) 
>> Android, iOS
>> such common use-cases should be abstracted and available via Qt API
> Yes but it should be good, portable, future-proof API, to be worthwhile.  
> Ideally even portable between desktops and mobiles.  It’s hard to predict the 
> future, too.  There is a disconnect that on desktop platforms you share by 
> saving files in one application and re-opening in another, or via the 
> clipboard, or drag-and-drop, whereas on mobile platforms this stuff got 
> re-invented.  I’m not sure if it’s an improvement: applications seem mostly 
> isolated now, effectively.  Not that I’ve tried very hard to use a tablet for 
> office-y stuff, but I’m not sure if everything that was possible on the 
> desktop is possible on those platforms.  If you extend the platform to 
> include cloud services (since not all data is even stored locally, I guess 
> it’s supposed to mean that inter-app sharing must include sharing of access 
> to data which is stored only on the cloud), do you trust them: are they 
> secure? are they going to still be there in a few years?  will they continue 
> to have a gazillion non-interoperable ways to do similar stuff?  How much 
> abstraction can we do, to make sharing locally or via the cloud look similar? 
>  Would you dare to start a university degree program for example, and do all 
> your work only on a tablet?  If you do that, can you still open anything that 
> you did in a decade or two?  If the inter-app sharing mechanisms are 
> hindering people from getting work done, maybe they will be re-invented 
> again?  So it seems hard to create APIs now that won’t look foolish in 
> retrospect later on.
>
> The file abstraction is nice because of being so universal.  Even cloud 
> storage (with offline caching) can be done by making it a virtual filesystem. 
>  Yet the file abstraction does seem long in the tooth, because we no longer 
> rely on hard disks as much, and installing flash memory as a “disk” instead 
> of “memory” is so arbitrary - it will end some day, especially if most memory 
> ends up being non-volatile eventually.  But what is the long-term-stable 
> replacement for the hierarchical filesystem?  Will we keep using it just 
> because it’s such a human-friendly metaphor?  Or will sharing between all 
> apps end up looking more like today’s mobile APIs, where you first have to 
> open one app, and select the data, and “send” it to another; or, one app 
> invokes another to “pull” something?  I guess the reason is that active 
> transfer between apps which are both running at the same time is deemed more 
> secure than passive file-reading.  Or is there another reason?  But the 
> protocols for that data transfer seem like shifting sand to me.
from my enterprise customers requirements for x-platform android/ios:
* support for incoming intents: employee opens a file (pdf, image, ...)
and can open this one with Qt App to upload to server or so
* support for outgoing intents: employee downloads file from server,
then wants to open this one in Acrobat to read pdf, etc
there are more use-cases for open-in-map (Google, here), open Phone-Call
from phone-number, ...
For my customers security is no question because app is running on BES12
server and AndroidForWork / SamsungKNOX on Android and
secure-VPN-connection on iOS 9.x - so the app has only restricted access
inside work data

>  
> https://bugreports.qt.io/browse/QTBUG-36015 has links to some lower-level 
> tasks like support for intents, anyway.
>
thx mentioning this. will read through and add comments / bugreports.

-- 

ekke (ekkehard gentz)

independent software architect
international development native mobile business apps
BlackBerry 10 | Qt Mobile (Android, iOS)
workshops - tr

Re: [Interest] 5.8 Features?

[Shawn Rutledge]

> On 23 Jun 2016, at 07:15, ekke  wrote:
> 
> thx Maurice,
> 
> Am 22.06.16 um 12:22 schrieb Maurice Kalinowski:
>> > Highest prio from my personal perspective:
>> > >> - Background processing API
>> > >> - In-app Notifications: local, remote
>> > + add Windows Store to Qt Purchasing module
> there's more missing:
> - avoid flicker for android apps out-of-the-box

What does that mean, just the initial appearance at startup?  My pet peeve is 
that startup of Qt Android apps takes too long, compared to Java apps.  
Ironically it's Java apps that are too slow on desktop platforms.  So I just 
wish I had a modern Qt-based phone, so that there’s one copy of the libs in 
memory already.  Apps would be small and fast.

> - easy way to 'share' content with/from other apps (Intents, Deep Linking) 
> Android, iOS
> such common use-cases should be abstracted and available via Qt API

Yes but it should be good, portable, future-proof API, to be worthwhile.  
Ideally even portable between desktops and mobiles.  It’s hard to predict the 
future, too.  There is a disconnect that on desktop platforms you share by 
saving files in one application and re-opening in another, or via the 
clipboard, or drag-and-drop, whereas on mobile platforms this stuff got 
re-invented.  I’m not sure if it’s an improvement: applications seem mostly 
isolated now, effectively.  Not that I’ve tried very hard to use a tablet for 
office-y stuff, but I’m not sure if everything that was possible on the desktop 
is possible on those platforms.  If you extend the platform to include cloud 
services (since not all data is even stored locally, I guess it’s supposed to 
mean that inter-app sharing must include sharing of access to data which is 
stored only on the cloud), do you trust them: are they secure? are they going 
to still be there in a few years?  will they continue to have a gazillion 
non-interoperable ways to do similar stuff?  How much abstraction can we do, to 
make sharing locally or via the cloud look similar?  Would you dare to start a 
university degree program for example, and do all your work only on a tablet?  
If you do that, can you still open anything that you did in a decade or two?  
If the inter-app sharing mechanisms are hindering people from getting work 
done, maybe they will be re-invented again?  So it seems hard to create APIs 
now that won’t look foolish in retrospect later on.

The file abstraction is nice because of being so universal.  Even cloud storage 
(with offline caching) can be done by making it a virtual filesystem.  Yet the 
file abstraction does seem long in the tooth, because we no longer rely on hard 
disks as much, and installing flash memory as a “disk” instead of “memory” is 
so arbitrary - it will end some day, especially if most memory ends up being 
non-volatile eventually.  But what is the long-term-stable replacement for the 
hierarchical filesystem?  Will we keep using it just because it’s such a 
human-friendly metaphor?  Or will sharing between all apps end up looking more 
like today’s mobile APIs, where you first have to open one app, and select the 
data, and “send” it to another; or, one app invokes another to “pull” 
something?  I guess the reason is that active transfer between apps which are 
both running at the same time is deemed more secure than passive file-reading.  
Or is there another reason?  But the protocols for that data transfer seem like 
shifting sand to me.
 
https://bugreports.qt.io/browse/QTBUG-36015 has links to some lower-level tasks 
like support for intents, anyway.

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[ekke]

thx Maurice,

Am 22.06.16 um 12:22 schrieb Maurice Kalinowski:
>
> > Highest prio from my personal perspective:
>
> > >> - Background processing API
>
> > >> - In-app Notifications: local, remote
>
> > + add Windows Store to Qt Purchasing module
>
there's more missing:
- avoid flicker for android apps out-of-the-box
- easy way to 'share' content with/from other apps (Intents, Deep
Linking) Android, iOS
such common use-cases should be abstracted and available via Qt API

coming from BlackBerry 10 Cascades/QML APP Development I'm astonished
how many common mobile tasks are missing

I want to motivate my enterprise customers to use Qt for mobile
x-platform development
they're comparing with Xamarin, Ionic, Angular ...

I still believe Qt is the best solution for mobile x platform and hope
there will be really progress on this
esp. after providing QtQuickControls2 Material style for great looking apps

ekke
>
>  
>
> https://codereview.qt-project.org/#/c/149602/
>
> https://codereview.qt-project.org/#/c/162992/
>
>  
>
> ;)
>
>  
>
> Maurice
>
>  
>
>  
>
> *From:*Interest
> [mailto:interest-bounces+maurice.kalinowski=qt...@qt-project.org] *On
> Behalf Of *Matthias Degenkolb via Interest
> *Sent:* Wednesday, June 22, 2016 11:25 AM
> *To:* ekke 
> *Cc:* interest@qt-project.org
> *Subject:* Re: [Interest] 5.8 Features?
>
>  
>
> I fully agree to ekke's and Jason's wishes. The features mentioned are
> all topics I also miss urgently since our first app development tests
> with Qt ..
>
> Not having cross-platform access to those "standard" mechanisms for
> mobile OS really makes me wonder whether my next projects will be
> based on Qt ...
>
>  
>
> Highest prio from my personal perspective:
>
> >> - Background processing API
> >> - In-app Notifications: local, remote
>
> + add Windows Store to Qt Purchasing module
>
>  
>
>  
>
> 2016-06-22 10:45 GMT+02:00 ekke  <mailto:e...@ekkes-corner.org>>:
>
> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
>
> > Den 21-06-2016 kl. 22:55 skrev Jason H:
> >> I feel like the last few releases have been run by the trolls, and
> >> not the users of Qt. I was hoping open governance would enable the
> >> community to direct Qt development, but I seem to have
> misinterpreted
> >> what it means. I'm looking for what's going into 5.8.. not much
> >> listed on the releases page.
> >>
> >> I'd like to suggest that mobile get some much needed love.
> >> - Application state transitions; Foreground, background
> >> - Background processing API
> >> - Screen wake lock API
> >> - In-app Notifications: local, remote
> >>
> >> While I have those characterized as "mobile" there are things like
> >> notifications occurring on desktop platforms.
> >>
> >> Any thoughts?
> >
> > There's only one reason why you don't see more features for the
> mobile
> > parts: There are not enough developers on it. And that's not because
> > QtCompany is doing anything wrong, they just have their priorities
> > different from what you have.
> >
> > Personally I don't care about mobile at all. I haven't had a mobile
> > customer since 2011 and I don't see that changing. My focus is
> almost
> > entirely on Linux embedded and Windows desktop. Those are the areas
> > where a lot of applications are written.
> >
> > I'd love to see the mobile platforms thrive. But unless you Qt users
> > start becoming Qt developers and contribute to it, I don't see that
> > happening.
>
> hmmm
> the only reason for me to use Qt is mobile
> using new Qt Quick Controls 2 Qt is a great platform for mobile app
> development and I hope many new developers will start with Qt on
> mobile
> to make this easier I'm writing example apps and a blog series
> http://j.mp/qt-x
>
> I really hope that there will be development on the topics Jason H
> mentioned above
>
> ekke
>
> >
> > Bo Thorsen,
> > Director, Viking Software.
> >
>
> ___
> Interest mailing list
> Interest@qt-project.org <mailto:Interest@qt-project.org>
> http://lists.qt-project.org/mailman/listinfo/interest
>
>  
>


-- 

ekke (ekkehard gentz)

independent software architect
international development native mobile business apps
BlackBerry 10 | Qt Mobile (Android, iOS)
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

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Tuukka Turunen]

> -Original Message-
> From: Interest [mailto:interest-bounces+tuukka.turunen=qt.io@qt-
> project.org] On Behalf Of Michael R Nelson
> Sent: keskiviikkona 22. kesäkuuta 2016 19.11
> To: interest@qt-project.org
> Subject: Re: [Interest] 5.8 Features?
> 
> I have to say I completely agree with Jason's sentiment here. I'm a
> commercial customer since early Qt 5.0. I bought with the belief mobile
> support would continue to grow, and not require me to step into native
> platform coding, nor require me to build custom versions of Qt to get around
> shortcomings that never get fixed.
> 

Hi,

Perhaps the pace has been slower than you wanted, or maybe the developed items 
different, but the mobile support of Qt has developed steadily with each 
release. Not only are we keeping pace with the mobile developments supporting 
new platform versions as they are available, but there has also been steady 
increase of the API parity and maturity. One of the big investments benefiting 
mobile has been to support WinRT / Windows 10, which of course does not benefit 
those who are only interested in iOS or Android. Qt is well committed in 
keeping and improving the position as the leading cross-platform toolkit across 
desktop-mobile-embedded. 

Yours,

Tuukka


> Mike
> 
> -Original Message-
> From: Interest [mailto:interest-bounces+mnelson=sutron.com@qt-
> project.org] On Behalf Of Jason H
> Sent: Wednesday, June 22, 2016 9:40 AM
> To: Sze Howe Koh 
> Cc: interest@qt-project.org
> Subject: Re: [Interest] 5.8 Features?
> 
> 
> > Subject: Re: [Interest] 5.8 Features?
> >
> > On 22 June 2016 at 09:34, Thiago Macieira 
> wrote:
> > >
> > > On terça-feira, 21 de junho de 2016 22:55:07 PDT Jason H wrote:
> > > > I feel like the last few releases have been run by the trolls, and
> > > > not the users of Qt. I was hoping open governance would enable the
> > > > community to direct Qt development, but I seem to have
> misinterpreted what it means.
> >
> > See https://wiki.qt.io/The_Qt_Governance_Model
> >
> > "Open governance" means that all members of the community can raise
> > proposals and vote on them. It is also a meritocratic system (as
> > opposed to democratic), which means more weight is given to members of
> > higher rank. Put simply, rank is gained through contributions and
> > commitment to the Qt Project.
> 
> Where and when does this voting occur? I've been vocal about improving Qt
> on mobile since mobile was an option. I've been hardcore on the
> shortcomings for about 20 months. During that time, I saw 5.6 get released,
> 5.7 get released at the same time as 5.6.1, and a lot of meaningless (to me)
> modules added. And now 5.8 is only 1.5 months from 5.7? What_the_hell?
> I'd like to see Qt complete it's mobile initiative.
> 
> As for contributing, the past 20 months I've been under _multiple_
> commercial licenses, one that was paying for a Desktop just to use Qt Charts.
> I think that's pretty material.
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
> 
> Please be advised that this email may contain confidential information. If you
> are not the intended recipient, please notify us by email by replying to the
> sender and delete this message. The sender disclaims that the content of
> this email constitutes an offer to enter into, or the acceptance of, any
> agreement; provided that the foregoing does not invalidate the binding
> effect of any digital or other electronic reproduction of a manual signature
> that is included in any attachment.
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Thiago Macieira]

On quarta-feira, 22 de junho de 2016 15:39:35 PDT Jason H wrote:
> > "Open governance" means that all members of the community can raise
> > proposals and vote on them. It is also a meritocratic system (as
> > opposed to democratic), which means more weight is given to members of
> > higher rank. Put simply, rank is gained through contributions and
> > commitment to the Qt Project.
> 
> Where and when does this voting occur? I've been vocal about improving Qt on
> mobile since mobile was an option. I've been hardcore on the shortcomings
> for about 20 months. During that time, I saw 5.6 get released, 5.7 get
> released at the same time as 5.6.1, and a lot of meaningless (to me)
> modules added. And now 5.8 is only 1.5 months from 5.7? What_the_hell? I'd
> like to see Qt complete it's mobile initiative.

See the other email on the voting.

Your contribution in terms of being vocal about an issue is not new with the 
Qt Open Governance: you could have done before that. Developers are supposed 
to listen to users to figure out what to do next, especially listen to 
complaints about pain points. That doesn't mean we always do what users ask, 
though -- sometimes we take our own opinion, like was the case of 
QNetworkDatagram.

> As for contributing, the past 20 months I've been under _multiple_
> commercial licenses, one that was paying for a Desktop just to use Qt
> Charts. I think that's pretty material.

Indeed, that's another way to influence: to pay for a commercial licence and 
use your premium support as well as relationship with the commercial sales to 
request features and provide feedback.

But those are outside the governance. Those have been in place since Trolltech 
was founded in 1993.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Thiago Macieira]

On quarta-feira, 22 de junho de 2016 16:57:57 PDT Sze Howe Koh wrote:
> "Open governance" means that all members of the community can raise
> proposals and vote on them. It is also a meritocratic system (as
> opposed to democratic), which means more weight is given to members of
> higher rank. Put simply, rank is gained through contributions and
> commitment to the Qt Project.

Just to be clear: there's no actual *voting*. The Qt governance is not a 
democracy.

Issues are discussed, opinions are raised, those with the most merit (best 
logical arguments, best technical reasoning, coming from those with most 
experience, etc.) win.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Michael R Nelson]

I have to say I completely agree with Jason's sentiment here. I'm a commercial 
customer since early Qt 5.0. I bought with the belief mobile support would 
continue to grow, and not require me to step into native platform coding, nor 
require me to build custom versions of Qt to get around shortcomings that never 
get fixed.

Mike

-Original Message-
From: Interest [mailto:interest-bounces+mnelson=sutron@qt-project.org] On 
Behalf Of Jason H
Sent: Wednesday, June 22, 2016 9:40 AM
To: Sze Howe Koh 
Cc: interest@qt-project.org
Subject: Re: [Interest] 5.8 Features?


> Subject: Re: [Interest] 5.8 Features?
>
> On 22 June 2016 at 09:34, Thiago Macieira  wrote:
> >
> > On terça-feira, 21 de junho de 2016 22:55:07 PDT Jason H wrote:
> > > I feel like the last few releases have been run by the trolls, and
> > > not the users of Qt. I was hoping open governance would enable the
> > > community to direct Qt development, but I seem to have misinterpreted 
> > > what it means.
>
> See https://wiki.qt.io/The_Qt_Governance_Model
>
> "Open governance" means that all members of the community can raise
> proposals and vote on them. It is also a meritocratic system (as
> opposed to democratic), which means more weight is given to members of
> higher rank. Put simply, rank is gained through contributions and
> commitment to the Qt Project.

Where and when does this voting occur? I've been vocal about improving Qt on 
mobile since mobile was an option. I've been hardcore on the shortcomings for 
about 20 months. During that time, I saw 5.6 get released, 5.7 get released at 
the same time as 5.6.1, and a lot of meaningless (to me) modules added. And now 
5.8 is only 1.5 months from 5.7? What_the_hell? I'd like to see Qt complete 
it's mobile initiative.

As for contributing, the past 20 months I've been under _multiple_ commercial 
licenses, one that was paying for a Desktop just to use Qt Charts. I think 
that's pretty material.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Please be advised that this email may contain confidential information. If you 
are not the intended recipient, please notify us by email by replying to the 
sender and delete this message. The sender disclaims that the content of this 
email constitutes an offer to enter into, or the acceptance of, any agreement; 
provided that the foregoing does not invalidate the binding effect of any 
digital or other electronic reproduction of a manual signature that is included 
in any attachment.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Jason H]

> Subject: Re: [Interest] 5.8 Features?
>
> On 22 June 2016 at 09:34, Thiago Macieira  wrote:
> >
> > On terça-feira, 21 de junho de 2016 22:55:07 PDT Jason H wrote:
> > > I feel like the last few releases have been run by the trolls, and not the
> > > users of Qt. I was hoping open governance would enable the community to
> > > direct Qt development, but I seem to have misinterpreted what it means.
> 
> See https://wiki.qt.io/The_Qt_Governance_Model
> 
> "Open governance" means that all members of the community can raise
> proposals and vote on them. It is also a meritocratic system (as
> opposed to democratic), which means more weight is given to members of
> higher rank. Put simply, rank is gained through contributions and
> commitment to the Qt Project.

Where and when does this voting occur? I've been vocal about improving Qt on 
mobile since mobile was an option. I've been hardcore on the shortcomings for 
about 20 months. During that time, I saw 5.6 get released, 5.7 get released at 
the same time as 5.6.1, and a lot of meaningless (to me) modules added. And now 
5.8 is only 1.5 months from 5.7? What_the_hell? I'd like to see Qt complete 
it's mobile initiative.

As for contributing, the past 20 months I've been under _multiple_ commercial 
licenses, one that was paying for a Desktop just to use Qt Charts. I think 
that's pretty material. 
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Maurice Kalinowski]

> Highest prio from my personal perspective:
> >> - Background processing API
> >> - In-app Notifications: local, remote
> + add Windows Store to Qt Purchasing module

https://codereview.qt-project.org/#/c/149602/
https://codereview.qt-project.org/#/c/162992/

;)

Maurice


From: Interest 
[mailto:interest-bounces+maurice.kalinowski=qt...@qt-project.org] On Behalf Of 
Matthias Degenkolb via Interest
Sent: Wednesday, June 22, 2016 11:25 AM
To: ekke 
Cc: interest@qt-project.org
Subject: Re: [Interest] 5.8 Features?

I fully agree to ekke's and Jason's wishes. The features mentioned are all 
topics I also miss urgently since our first app development tests with Qt ..
Not having cross-platform access to those "standard" mechanisms for mobile OS 
really makes me wonder whether my next projects will be based on Qt ...

Highest prio from my personal perspective:
>> - Background processing API
>> - In-app Notifications: local, remote
+ add Windows Store to Qt Purchasing module


2016-06-22 10:45 GMT+02:00 ekke 
mailto:e...@ekkes-corner.org>>:
Am 22.06.16 um 10:36 schrieb Bo Thorsen:
> Den 21-06-2016 kl. 22:55 skrev Jason H:
>> I feel like the last few releases have been run by the trolls, and
>> not the users of Qt. I was hoping open governance would enable the
>> community to direct Qt development, but I seem to have misinterpreted
>> what it means. I'm looking for what's going into 5.8.. not much
>> listed on the releases page.
>>
>> I'd like to suggest that mobile get some much needed love.
>> - Application state transitions; Foreground, background
>> - Background processing API
>> - Screen wake lock API
>> - In-app Notifications: local, remote
>>
>> While I have those characterized as "mobile" there are things like
>> notifications occurring on desktop platforms.
>>
>> Any thoughts?
>
> There's only one reason why you don't see more features for the mobile
> parts: There are not enough developers on it. And that's not because
> QtCompany is doing anything wrong, they just have their priorities
> different from what you have.
>
> Personally I don't care about mobile at all. I haven't had a mobile
> customer since 2011 and I don't see that changing. My focus is almost
> entirely on Linux embedded and Windows desktop. Those are the areas
> where a lot of applications are written.
>
> I'd love to see the mobile platforms thrive. But unless you Qt users
> start becoming Qt developers and contribute to it, I don't see that
> happening.
hmmm
the only reason for me to use Qt is mobile
using new Qt Quick Controls 2 Qt is a great platform for mobile app
development and I hope many new developers will start with Qt on mobile
to make this easier I'm writing example apps and a blog series
http://j.mp/qt-x

I really hope that there will be development on the topics Jason H
mentioned above

ekke

>
> Bo Thorsen,
> Director, Viking Software.
>
___
Interest mailing list
Interest@qt-project.org<mailto:Interest@qt-project.org>
http://lists.qt-project.org/mailman/listinfo/interest

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[ekke]

Am 22.06.16 um 12:12 schrieb Xavier Bigand:
> It is good to know, I made my test with Qt5.6 and Qt Quick Controls
> labs. It seems that there is some improvement since.
> It seems that one of the hardest thing to simulate is the shadow with
> elevation, but on your captures it seems perfect.
Material.elevation property can be set in Qt 5.7
>
> If I can make my personal application with Qt, it would be great,
> because I dislike Android Studio.
I'll do more example apps and provide recipes for Controls not available
out-of-the-box
ekke
>
> 2016-06-22 11:43 GMT+02:00 ekke  >:
>
> Am 22.06.16 um 11:31 schrieb Xavier Bigand:
>> I made few tests for a personal project with Qt Quick Controls 2
>> on Android and was not convinced. Because for a full GUI
>> application it still too far from the same GUI made with the
>> Android SDK.
> take a look at this example app: blog http://bit.ly/qt-drawer-nav-x
> and at github: https://github.com/ekke/drawer_nav_x
> Drawer, Bottom Navigation, FAB, Popup, Toast, StackView,
> SwipeView, Pages, ...
> some fine-tuning is already in-development (have written
> bugreports for this)
> From my POV you can write good looking Android Material Apps
> the only controls I'm missing are Date- and Time Pickers
>
>
> I'm still evaluating, but have a good feeling that Qt 5.7 will be
> great for mobile business apps I'm writing
>
> ekke
>
>> I still think that for small applications that is preferable to
>> develop them with the platform SDK as they contains all features.
>> But for middle and biggest applications it can be different
>> especially if desktop platforms are also target.
>> There is an other reason why I think that it is preferable to use
>> platform SDK, it is for commercial application that want to try
>> to be featured by mobile stores, it would be easier to integrate
>> latest SDK features,...
>>
>>
>> I am working on big application with a 3D engine that runs on
>> mobile and desktop, we are using Qt Quick for the GUI, everything
>> else is in standard C++. For feature specific to the platform
>> (in-app, social,...) we use platform SDK and it's not that long
>> to do the job 2 or 3 times for those features.
>>
>> Qt represent a big time saver for the GUI for us mainly because
>> of the property binding that allow us to adapt the GUI easily and
>> efficiently to the screen size, and tweak it per platform,
>> product version,...
>>
>> And now I am trying to replace our 3D engine by qt3d to improve
>> the user experience, the compatibility on desktop, the
>> performances and be able to use different rendering techniques on
>> desktop.
>>
>>
>>
>>
>> 2016-06-22 10:45 GMT+02:00 ekke > >:
>>
>> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
>> > Den 21-06-2016 kl. 22:55 skrev Jason H:
>> >> I feel like the last few releases have been run by the
>> trolls, and
>> >> not the users of Qt. I was hoping open governance would
>> enable the
>> >> community to direct Qt development, but I seem to have
>> misinterpreted
>> >> what it means. I'm looking for what's going into 5.8.. not
>> much
>> >> listed on the releases page.
>> >>
>> >> I'd like to suggest that mobile get some much needed love.
>> >> - Application state transitions; Foreground, background
>> >> - Background processing API
>> >> - Screen wake lock API
>> >> - In-app Notifications: local, remote
>> >>
>> >> While I have those characterized as "mobile" there are
>> things like
>> >> notifications occurring on desktop platforms.
>> >>
>> >> Any thoughts?
>> >
>> > There's only one reason why you don't see more features for
>> the mobile
>> > parts: There are not enough developers on it. And that's
>> not because
>> > QtCompany is doing anything wrong, they just have their
>> priorities
>> > different from what you have.
>> >
>> > Personally I don't care about mobile at all. I haven't had
>> a mobile
>> > customer since 2011 and I don't see that changing. My focus
>> is almost
>> > entirely on Linux embedded and Windows desktop. Those are
>> the areas
>> > where a lot of applications are written.
>> >
>> > I'd love to see the mobile platforms thrive. But unless you
>> Qt users
>> > start becoming Qt developers and contribute to it, I don't
>> see that
>> > happening.
>> hmmm
>> the only reason for me to use Qt is mobile
>> using new Qt Quick Controls 2 Qt is a great platform for
>> mobile app
>> development and I hope many ne

Re: [Interest] 5.8 Features?

[Xavier Bigand]

It is good to know, I made my test with Qt5.6 and Qt Quick Controls labs.
It seems that there is some improvement since.
It seems that one of the hardest thing to simulate is the shadow with
elevation, but on your captures it seems perfect.

If I can make my personal application with Qt, it would be great, because I
dislike Android Studio.

2016-06-22 11:43 GMT+02:00 ekke :

> Am 22.06.16 um 11:31 schrieb Xavier Bigand:
>
> I made few tests for a personal project with Qt Quick Controls 2 on
> Android and was not convinced. Because for a full GUI application it still
> too far from the same GUI made with the Android SDK.
>
> take a look at this example app: blog http://bit.ly/qt-drawer-nav-x
> and at github: https://github.com/ekke/drawer_nav_x
> Drawer, Bottom Navigation, FAB, Popup, Toast, StackView, SwipeView, Pages,
> ...
> some fine-tuning is already in-development (have written bugreports for
> this)
> From my POV you can write good looking Android Material Apps
> the only controls I'm missing are Date- and Time Pickers
>
>
> I'm still evaluating, but have a good feeling that Qt 5.7 will be great
> for mobile business apps I'm writing
>
> ekke
>
> I still think that for small applications that is preferable to develop
> them with the platform SDK as they contains all features. But for middle
> and biggest applications it can be different especially if desktop
> platforms are also target.
> There is an other reason why I think that it is preferable to use platform
> SDK, it is for commercial application that want to try to be featured by
> mobile stores, it would be easier to integrate latest SDK features,...
>
>
> I am working on big application with a 3D engine that runs on mobile and
> desktop, we are using Qt Quick for the GUI, everything else is in standard
> C++. For feature specific to the platform (in-app, social,...) we use
> platform SDK and it's not that long to do the job 2 or 3 times for those
> features.
>
> Qt represent a big time saver for the GUI for us mainly because of the
> property binding that allow us to adapt the GUI easily and efficiently to
> the screen size, and tweak it per platform, product version,...
>
> And now I am trying to replace our 3D engine by qt3d to improve the user
> experience, the compatibility on desktop, the performances and be able to
> use different rendering techniques on desktop.
>
>
>
>
> 2016-06-22 10:45 GMT+02:00 ekke :
>
>> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
>> > Den 21-06-2016 kl. 22:55 skrev Jason H:
>> >> I feel like the last few releases have been run by the trolls, and
>> >> not the users of Qt. I was hoping open governance would enable the
>> >> community to direct Qt development, but I seem to have misinterpreted
>> >> what it means. I'm looking for what's going into 5.8.. not much
>> >> listed on the releases page.
>> >>
>> >> I'd like to suggest that mobile get some much needed love.
>> >> - Application state transitions; Foreground, background
>> >> - Background processing API
>> >> - Screen wake lock API
>> >> - In-app Notifications: local, remote
>> >>
>> >> While I have those characterized as "mobile" there are things like
>> >> notifications occurring on desktop platforms.
>> >>
>> >> Any thoughts?
>> >
>> > There's only one reason why you don't see more features for the mobile
>> > parts: There are not enough developers on it. And that's not because
>> > QtCompany is doing anything wrong, they just have their priorities
>> > different from what you have.
>> >
>> > Personally I don't care about mobile at all. I haven't had a mobile
>> > customer since 2011 and I don't see that changing. My focus is almost
>> > entirely on Linux embedded and Windows desktop. Those are the areas
>> > where a lot of applications are written.
>> >
>> > I'd love to see the mobile platforms thrive. But unless you Qt users
>> > start becoming Qt developers and contribute to it, I don't see that
>> > happening.
>> hmmm
>> the only reason for me to use Qt is mobile
>> using new Qt Quick Controls 2 Qt is a great platform for mobile app
>> development and I hope many new developers will start with Qt on mobile
>> to make this easier I'm writing example apps and a blog series
>> http://j.mp/qt-x
>>
>> I really hope that there will be development on the topics Jason H
>> mentioned above
>>
>> ekke
>>
>> >
>> > Bo Thorsen,
>> > Director, Viking Software.
>> >
>>
>> ___
>> Interest mailing list
>> Interest@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>>
>
>
>
> --
> Xavier
>
>
>
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>


-- 
Xavier
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[ekke]

Am 22.06.16 um 11:31 schrieb Xavier Bigand:
> I made few tests for a personal project with Qt Quick Controls 2 on
> Android and was not convinced. Because for a full GUI application it
> still too far from the same GUI made with the Android SDK.
take a look at this example app: blog http://bit.ly/qt-drawer-nav-x
and at github: https://github.com/ekke/drawer_nav_x
Drawer, Bottom Navigation, FAB, Popup, Toast, StackView, SwipeView,
Pages, ...
some fine-tuning is already in-development (have written bugreports for
this)
>From my POV you can write good looking Android Material Apps
the only controls I'm missing are Date- and Time Pickers


I'm still evaluating, but have a good feeling that Qt 5.7 will be great
for mobile business apps I'm writing

ekke
> I still think that for small applications that is preferable to
> develop them with the platform SDK as they contains all features. But
> for middle and biggest applications it can be different especially if
> desktop platforms are also target.
> There is an other reason why I think that it is preferable to use
> platform SDK, it is for commercial application that want to try to be
> featured by mobile stores, it would be easier to integrate latest SDK
> features,...
>
>
> I am working on big application with a 3D engine that runs on mobile
> and desktop, we are using Qt Quick for the GUI, everything else is in
> standard C++. For feature specific to the platform (in-app,
> social,...) we use platform SDK and it's not that long to do the job 2
> or 3 times for those features.
>
> Qt represent a big time saver for the GUI for us mainly because of the
> property binding that allow us to adapt the GUI easily and efficiently
> to the screen size, and tweak it per platform, product version,...
>
> And now I am trying to replace our 3D engine by qt3d to improve the
> user experience, the compatibility on desktop, the performances and be
> able to use different rendering techniques on desktop.
>
>
>
>
> 2016-06-22 10:45 GMT+02:00 ekke  >:
>
> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
> > Den 21-06-2016 kl. 22:55 skrev Jason H:
> >> I feel like the last few releases have been run by the trolls, and
> >> not the users of Qt. I was hoping open governance would enable the
> >> community to direct Qt development, but I seem to have
> misinterpreted
> >> what it means. I'm looking for what's going into 5.8.. not much
> >> listed on the releases page.
> >>
> >> I'd like to suggest that mobile get some much needed love.
> >> - Application state transitions; Foreground, background
> >> - Background processing API
> >> - Screen wake lock API
> >> - In-app Notifications: local, remote
> >>
> >> While I have those characterized as "mobile" there are things like
> >> notifications occurring on desktop platforms.
> >>
> >> Any thoughts?
> >
> > There's only one reason why you don't see more features for the
> mobile
> > parts: There are not enough developers on it. And that's not because
> > QtCompany is doing anything wrong, they just have their priorities
> > different from what you have.
> >
> > Personally I don't care about mobile at all. I haven't had a mobile
> > customer since 2011 and I don't see that changing. My focus is
> almost
> > entirely on Linux embedded and Windows desktop. Those are the areas
> > where a lot of applications are written.
> >
> > I'd love to see the mobile platforms thrive. But unless you Qt users
> > start becoming Qt developers and contribute to it, I don't see that
> > happening.
> hmmm
> the only reason for me to use Qt is mobile
> using new Qt Quick Controls 2 Qt is a great platform for mobile app
> development and I hope many new developers will start with Qt on
> mobile
> to make this easier I'm writing example apps and a blog series
> http://j.mp/qt-x
>
> I really hope that there will be development on the topics Jason H
> mentioned above
>
> ekke
>
> >
> > Bo Thorsen,
> > Director, Viking Software.
> >
>
> ___
> Interest mailing list
> Interest@qt-project.org 
> http://lists.qt-project.org/mailman/listinfo/interest
>
>
>
>
> -- 
> Xavier


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Xavier Bigand]

I made few tests for a personal project with Qt Quick Controls 2 on Android
and was not convinced. Because for a full GUI application it still too far
from the same GUI made with the Android SDK.
I still think that for small applications that is preferable to develop
them with the platform SDK as they contains all features. But for middle
and biggest applications it can be different especially if desktop
platforms are also target.
There is an other reason why I think that it is preferable to use platform
SDK, it is for commercial application that want to try to be featured by
mobile stores, it would be easier to integrate latest SDK features,...


I am working on big application with a 3D engine that runs on mobile and
desktop, we are using Qt Quick for the GUI, everything else is in standard
C++. For feature specific to the platform (in-app, social,...) we use
platform SDK and it's not that long to do the job 2 or 3 times for those
features.

Qt represent a big time saver for the GUI for us mainly because of the
property binding that allow us to adapt the GUI easily and efficiently to
the screen size, and tweak it per platform, product version,...

And now I am trying to replace our 3D engine by qt3d to improve the user
experience, the compatibility on desktop, the performances and be able to
use different rendering techniques on desktop.




2016-06-22 10:45 GMT+02:00 ekke :

> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
> > Den 21-06-2016 kl. 22:55 skrev Jason H:
> >> I feel like the last few releases have been run by the trolls, and
> >> not the users of Qt. I was hoping open governance would enable the
> >> community to direct Qt development, but I seem to have misinterpreted
> >> what it means. I'm looking for what's going into 5.8.. not much
> >> listed on the releases page.
> >>
> >> I'd like to suggest that mobile get some much needed love.
> >> - Application state transitions; Foreground, background
> >> - Background processing API
> >> - Screen wake lock API
> >> - In-app Notifications: local, remote
> >>
> >> While I have those characterized as "mobile" there are things like
> >> notifications occurring on desktop platforms.
> >>
> >> Any thoughts?
> >
> > There's only one reason why you don't see more features for the mobile
> > parts: There are not enough developers on it. And that's not because
> > QtCompany is doing anything wrong, they just have their priorities
> > different from what you have.
> >
> > Personally I don't care about mobile at all. I haven't had a mobile
> > customer since 2011 and I don't see that changing. My focus is almost
> > entirely on Linux embedded and Windows desktop. Those are the areas
> > where a lot of applications are written.
> >
> > I'd love to see the mobile platforms thrive. But unless you Qt users
> > start becoming Qt developers and contribute to it, I don't see that
> > happening.
> hmmm
> the only reason for me to use Qt is mobile
> using new Qt Quick Controls 2 Qt is a great platform for mobile app
> development and I hope many new developers will start with Qt on mobile
> to make this easier I'm writing example apps and a blog series
> http://j.mp/qt-x
>
> I really hope that there will be development on the topics Jason H
> mentioned above
>
> ekke
>
> >
> > Bo Thorsen,
> > Director, Viking Software.
> >
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>



-- 
Xavier
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Konstantin Tokarev]

21.06.2016, 23:55, "Jason H" :
> I feel like the last few releases have been run by the trolls, and not the 
> users of Qt. I was hoping open governance would enable the community to 
> direct Qt development, but I seem to have misinterpreted what it means. I'm 
> looking for what's going into 5.8.. not much listed on the releases page.
>
> I'd like to suggest that mobile get some much needed love.
> - Application state transitions; Foreground, background
> - Background processing API
> - Screen wake lock API
> - In-app Notifications: local, remote
>
> While I have those characterized as "mobile" there are things like 
> notifications occurring on desktop platforms.
>
> Any thoughts?

You still have ~1.5 months before 5.8 feature freeze to implement some of these 
items :)

-- 
Regards,
Konstantin
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Matthias Degenkolb via Interest]

I fully agree to ekke's and Jason's wishes. The features mentioned are all
topics I also miss urgently since our first app development tests with Qt ..
Not having cross-platform access to those "standard" mechanisms for mobile
OS really makes me wonder whether my next projects will be based on Qt ...

Highest prio from my personal perspective:
>> - Background processing API
>> - In-app Notifications: local, remote
+ add Windows Store to Qt Purchasing module


2016-06-22 10:45 GMT+02:00 ekke :

> Am 22.06.16 um 10:36 schrieb Bo Thorsen:
> > Den 21-06-2016 kl. 22:55 skrev Jason H:
> >> I feel like the last few releases have been run by the trolls, and
> >> not the users of Qt. I was hoping open governance would enable the
> >> community to direct Qt development, but I seem to have misinterpreted
> >> what it means. I'm looking for what's going into 5.8.. not much
> >> listed on the releases page.
> >>
> >> I'd like to suggest that mobile get some much needed love.
> >> - Application state transitions; Foreground, background
> >> - Background processing API
> >> - Screen wake lock API
> >> - In-app Notifications: local, remote
> >>
> >> While I have those characterized as "mobile" there are things like
> >> notifications occurring on desktop platforms.
> >>
> >> Any thoughts?
> >
> > There's only one reason why you don't see more features for the mobile
> > parts: There are not enough developers on it. And that's not because
> > QtCompany is doing anything wrong, they just have their priorities
> > different from what you have.
> >
> > Personally I don't care about mobile at all. I haven't had a mobile
> > customer since 2011 and I don't see that changing. My focus is almost
> > entirely on Linux embedded and Windows desktop. Those are the areas
> > where a lot of applications are written.
> >
> > I'd love to see the mobile platforms thrive. But unless you Qt users
> > start becoming Qt developers and contribute to it, I don't see that
> > happening.
> hmmm
> the only reason for me to use Qt is mobile
> using new Qt Quick Controls 2 Qt is a great platform for mobile app
> development and I hope many new developers will start with Qt on mobile
> to make this easier I'm writing example apps and a blog series
> http://j.mp/qt-x
>
> I really hope that there will be development on the topics Jason H
> mentioned above
>
> ekke
>
> >
> > Bo Thorsen,
> > Director, Viking Software.
> >
>
> ___
> Interest mailing list
> Interest@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Sze Howe Koh]

On 22 June 2016 at 09:34, Thiago Macieira  wrote:
>
> On terça-feira, 21 de junho de 2016 22:55:07 PDT Jason H wrote:
> > I feel like the last few releases have been run by the trolls, and not the
> > users of Qt. I was hoping open governance would enable the community to
> > direct Qt development, but I seem to have misinterpreted what it means.

See https://wiki.qt.io/The_Qt_Governance_Model

"Open governance" means that all members of the community can raise
proposals and vote on them. It is also a meritocratic system (as
opposed to democratic), which means more weight is given to members of
higher rank. Put simply, rank is gained through contributions and
commitment to the Qt Project.

Regarding governance of new features, you can propose to add Feature X
to Qt. If nobody objects, that means you now have the green light to
implement and submit Feature X. (The normal review process still
applies.) You don't _have_ to make a formal proposal each time you
submit a patch, but it's strongly recommended when adding a large new
feature.


> > I'm
> > looking for what's going into 5.8.. not much listed on the releases page.
>
> Open governance allows developers of Qt, not users of Qt, to direct new
> features. I have added features to every version since 5.0 (inclusive) and
> have already submitted a few to 5.8. Open governance did not change the means
> for non-developing users to influence the progression.

To clarify Thiago's point, "Developers of Qt" refers to all
contributors, not just the Qt Company. You can become a developer of
Qt and direct new features simply by submitting, reviewing, and/or
testing code + documentation that pertain to the features you want.
For example, Qt 3D is now released mainly because KDAB poured
resources into its development [1].

Alternatively, you can achieve your goal indirectly by persuading
someone to develop the features that you want. For example, you can
persuade them by paying them [2], or by convincing them that it's
better to focus on Feature X instead of Feature Y or Bugfix Z.


Regards,
Sze-Howe

[1] https://blog.qt.io/blog/2016/06/16/introducing-qt-3d/
[2] https://woboq.com/blog/qdockwidget-changes-in-56.html
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[ekke]

Am 22.06.16 um 10:36 schrieb Bo Thorsen:
> Den 21-06-2016 kl. 22:55 skrev Jason H:
>> I feel like the last few releases have been run by the trolls, and
>> not the users of Qt. I was hoping open governance would enable the
>> community to direct Qt development, but I seem to have misinterpreted
>> what it means. I'm looking for what's going into 5.8.. not much
>> listed on the releases page.
>>
>> I'd like to suggest that mobile get some much needed love.
>> - Application state transitions; Foreground, background
>> - Background processing API
>> - Screen wake lock API
>> - In-app Notifications: local, remote
>>
>> While I have those characterized as "mobile" there are things like
>> notifications occurring on desktop platforms.
>>
>> Any thoughts?
>
> There's only one reason why you don't see more features for the mobile
> parts: There are not enough developers on it. And that's not because
> QtCompany is doing anything wrong, they just have their priorities
> different from what you have.
>
> Personally I don't care about mobile at all. I haven't had a mobile
> customer since 2011 and I don't see that changing. My focus is almost
> entirely on Linux embedded and Windows desktop. Those are the areas
> where a lot of applications are written.
>
> I'd love to see the mobile platforms thrive. But unless you Qt users
> start becoming Qt developers and contribute to it, I don't see that
> happening.
hmmm
the only reason for me to use Qt is mobile
using new Qt Quick Controls 2 Qt is a great platform for mobile app
development and I hope many new developers will start with Qt on mobile
to make this easier I'm writing example apps and a blog series
http://j.mp/qt-x

I really hope that there will be development on the topics Jason H
mentioned above

ekke

>
> Bo Thorsen,
> Director, Viking Software.
>

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Bo Thorsen]

Den 21-06-2016 kl. 22:55 skrev Jason H:

I feel like the last few releases have been run by the trolls, and not the 
users of Qt. I was hoping open governance would enable the community to direct 
Qt development, but I seem to have misinterpreted what it means. I'm looking 
for what's going into 5.8.. not much listed on the releases page.

I'd like to suggest that mobile get some much needed love.
- Application state transitions; Foreground, background
- Background processing API
- Screen wake lock API
- In-app Notifications: local, remote

While I have those characterized as "mobile" there are things like 
notifications occurring on desktop platforms.

Any thoughts?


There's only one reason why you don't see more features for the mobile 
parts: There are not enough developers on it. And that's not because 
QtCompany is doing anything wrong, they just have their priorities 
different from what you have.


Personally I don't care about mobile at all. I haven't had a mobile 
customer since 2011 and I don't see that changing. My focus is almost 
entirely on Linux embedded and Windows desktop. Those are the areas 
where a lot of applications are written.


I'd love to see the mobile platforms thrive. But unless you Qt users 
start becoming Qt developers and contribute to it, I don't see that 
happening.


Bo Thorsen,
Director, Viking Software.

--
Viking Software
Qt and C++ developers for hire
http://www.vikingsoft.eu
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] 5.8 Features?

[Thiago Macieira]

On terça-feira, 21 de junho de 2016 22:55:07 PDT Jason H wrote:
> I feel like the last few releases have been run by the trolls, and not the
> users of Qt. I was hoping open governance would enable the community to
> direct Qt development, but I seem to have misinterpreted what it means. I'm
> looking for what's going into 5.8.. not much listed on the releases page.

Open governance allows developers of Qt, not users of Qt, to direct new 
features. I have added features to every version since 5.0 (inclusive) and 
have already submitted a few to 5.8. Open governance did not change the means 
for non-developing users to influence the progression.

We don't maintain a list of upcoming features. Features are known to be in a 
release only when they are actually in that release. For example, I wrote 
QNetworkDatagram in time for Qt 5.6 and submitted it for that version. For 
many reasons, it was delayed and was only integrated this week, which means it 
will be in 5.8.

The changelog and new feature pages are created close to the release. We've 
just done it for 5.7. You're not going to find anything for 5.8 until sometime 
in September.

If you want to see what's already in 5.8, you have to use Git to see the log 
of changes in the dev branch that aren't in the 5.7 branch. If you want to see 
what may be coming, talk to people and check their Gerrit dashboards.

For example, right now I'm working on QDeadlineTimer (new class) and 
deprecating multiple win32-msvc20xx mkspecs with version number (one should be 
enough for all versions).

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

[Interest] 5.8 Features?

[Jason H]

I feel like the last few releases have been run by the trolls, and not the 
users of Qt. I was hoping open governance would enable the community to direct 
Qt development, but I seem to have misinterpreted what it means. I'm looking 
for what's going into 5.8.. not much listed on the releases page.

I'd like to suggest that mobile get some much needed love.
- Application state transitions; Foreground, background
- Background processing API
- Screen wake lock API
- In-app Notifications: local, remote

While I have those characterized as "mobile" there are things like 
notifications occurring on desktop platforms. 

Any thoughts?


___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest