2:17 I doubt that Flutter solution is developed with Kotlin language. :) Nevertheless, it would be interesting to know about the differences of these three. What are their weak points, strong points, performance comparison etc. Otherwise this presentation is quite useless. Anyway, knowing that KDAB is moving also towards Flutter and Slint is not a very good news for Qt, right?
How do you port the flutter framework onto a custom embedded [linux] device? For example, I've seen it done on a Pi Zero 2, but it's not trivial.. and it won't work on Pi Zero One, so I assume the specs of the embedded system must be verified first? Or keeping it simple, let's say flutter running on an embedded windows SBC.. how can Flutter access hardware? I've seen a 'FlutterClutter' posts with many developers (Brett Morgan, Maksim Lin, Tim Sneath, Nick Fisher, Giacomo Policicchio , Aseem Wangoo , MadMario , Majid Hajian , Igor Kharakhordin), however the example used is based on Flutter 1.x. :(
Hi! The reason that flutter does not run on the first RPI zero is because it uses a ARMv6 processor. We used flutter-pi to run flutter on this device. github.com/ardera/flutter-pi , you can find more info about "supported" hardware in flutter-pi documentation. There is also github.com/meta-flutter/meta-flutter. You can also have a peek at industrialflutter.com , there are some handy links & blog posts with useful information on the topic there. We hope this is helpful to you!
More importantly, how did visitors know KDAB actually used Flutter xD perhaps they couldn't fix it before the demo and now they're running Qt on both devices (or all three devices...) LOL
Interested to know runtime memory footprint for each of them
Hi there,
when we measured on desktop it was roughly:
Qt: 86.6 MB
Slint: 54.4 MB
Flutter: 118.7 MB
2:17 I doubt that Flutter solution is developed with Kotlin language. :) Nevertheless, it would be interesting to know about the differences of these three. What are their weak points, strong points, performance comparison etc. Otherwise this presentation is quite useless. Anyway, knowing that KDAB is moving also towards Flutter and Slint is not a very good news for Qt, right?
How do you port the flutter framework onto a custom embedded [linux] device?
For example, I've seen it done on a Pi Zero 2, but it's not trivial.. and it won't work on Pi Zero One, so I assume the specs of the embedded system must be verified first?
Or keeping it simple, let's say flutter running on an embedded windows SBC.. how can Flutter access hardware? I've seen a 'FlutterClutter' posts with many developers (Brett Morgan, Maksim Lin, Tim Sneath, Nick Fisher, Giacomo Policicchio , Aseem Wangoo , MadMario , Majid Hajian , Igor Kharakhordin), however the example used is based on Flutter 1.x. :(
I would like to know that as well. @KDAB can you post a link to your blog where you explain how you ported Flutter onto this embedded linux device?
Hi!
The reason that flutter does not run on the first RPI zero is because it uses a ARMv6 processor.
We used flutter-pi to run flutter on this device. github.com/ardera/flutter-pi , you can find more info about "supported" hardware in flutter-pi documentation. There is also github.com/meta-flutter/meta-flutter.
You can also have a peek at industrialflutter.com , there are some handy links & blog posts with useful information on the topic there.
We hope this is helpful to you!
More importantly, how did visitors know KDAB actually used Flutter xD perhaps they couldn't fix it before the demo and now they're running Qt on both devices (or all three devices...) LOL
I'm feeling wasted about 3 minutes of my life