Re:Qt Quick WebGL Streaming
by discreteevent on Monday February 27, 2017 @01:42PM
(#13746629)
Why are electron or web apps acceptable but Qt with e.g. a material look not acceptable?
I just don't get it. The Qt app will be faster, better looking, better integrated with OS apis much saner to develop (QML is really productive and what react would be if it could have is own DSL).
Who said electron or web apps are acceptable?!?
Did you miss the point I mentioned I prefer native apps?
Working on web apps is unavoidable when that is what customers are willing to pay for, on my own private devices outside work hours, pure native applications are the rules of the house.
Re:Qt Quick WebGL Streaming
by discreteevent on Monday February 27, 2017 @03:00PM
(#13747391)
Sorry. Fair point. I confused your comment with the rest of the thread.
Re:Qt Quick WebGL Streaming
by mememachine on Monday February 27, 2017 @09:35PM
(#13750653)
What we really need is that fast to start up apps for customer acquisition and then the long term downloads as an offering for the customers who want the speed.
It sounds like https://blog.qt.io/blog/2017/02/06/native-look-feel/ is trying to address your needs.
I tried Qt 5.4 and wasn't happy with the result, ended up settling on a mix of Java, C++/CX and C++ for my mobile side projects.
From your link it seems that by Qt 6, they might eventually get something that I already have with such setup today.
Also I am planning to switch to Xamarin in future side projects.
> I kind don't understand their current roadmap, it appears that they are trying to spread between C++ and JavaScript devs in an attempt not to lose mind share.
And maybe losing both camps in the process.
Specially on mobile. their decision to go with QML for mobile OS support, requiring devs to replicate native widgets, means it is a bigger effort to create multiple QML frontends, than it is to follow a MVVM architecture with as much code as possible in C++, while using native support directly, even if in different languages.
Also for those targeting mobile OSes, Xamarin has a much support for the respective OS APIs than Qt, that usually requires the extra effort of manually wrapping many of them.
As someone that prefers working on native apps to web ones, I kind don't understand their current roadmap, it appears that they are trying to spread between C++ and JavaScript devs in an attempt not to lose mind share.