I ran it with what is currently in the Pi repos. The code is in the blog
post:
http://www.logikalsolutions.com/wordpress/information-technology/raspberry-qt-part-12-qml-blows-big-stinky-chunks/
Feel free to pull down the QML version and run whatever tests you want.
Scan back to this post:
http://www.logikalsolutions.com/wordpress/raspberry-pi/raspberry-qt-part-5/
for the SerialKeypad link to download the C++ version.
Speaking as someone with 30+ years in IT, using a scripting language for
anything other than a batch job is _always_ a bad idea. The overhead of
the engine places an undue burden on the processor. This is especially
true in the battery operated world and one of the main reasons we now
have "wall huggers."
On 09/04/2016 06:22 PM, Sze Howe Koh wrote:
On 5 September 2016 at 02:13, Roland Hughes <rol...@logikalsolutions.com> wrote:
I just ran a simple QML project test on the Raspberry Pi:
http://www.logikalsolutions.com/wordpress/information-technology/raspberry-qt-part-12-qml-blows-big-stinky-chunks/
Yimminy is it a resource pig.
Would you be willing to re-run your test using Qt Quick Controls 2?
You can find relevant benchmarks for Raspberry Pi B+ at
http://blog.qt.io/blog/2015/03/31/qt-quick-controls-for-embedded/
See also http://blog.qt.io/blog/2016/06/16/qt-5-7-released/ -- "Qt
Quick Controls 1 were targeted at the desktop, and came with all the
bells and whistles required for desktop applications. This implied an
overhead that often made them too slow for usage on embedded devices.
Qt Quick Controls 2 solve these issues." The resource hog was not so
much JavaScript as the graphics stack.
Regards,
Sze-Howe
--
Roland Hughes, President
Logikal Solutions
(630)-205-1593
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
http://www.interestingauthors.com/blog
_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
