QT 5 Will Be Available For Raspberry Pi
New submitter sirjohn writes with the good news that "A small group of ICS and Nokia engineers have started working on a minimal bootstrap to bring fully functional Qt 5" to the Raspberry Pi, writing "Do you want to create the next big thing on embedded devices and have $35 to invest? You can now have a complete development environment with accelerated graphics for basically nothing. I think it's a big deal ..." Plus, Nokia is funding 400 of the boards and looking for ideas (and developers) to use them. The competition is stiff; there are already quite a few impressive ideas listed.
Why expect everyone else to do things for you?
Instead of whinging, why not make the effort and sign up for their mailing list and they'll email you when its out. (early/mid December is the bookies fav at the moment).
Qt 5 is about a *minimal* break in compatibility between Qt 4[1], so your suggestion of "breaking compatibility badly" was rather poorly researched.
As for hating on moc... moc is not just for signals! I hear this sort of thing repeated time and time again, and it's clear that every time, people do not do their homework. When you can come up with a solution that can provide at least these capabilities, feel free to suggest it for Qt 6, and better still, offer a patch.
- qobject_cast, a dynamic_cast which works across module boundaries (and doesn't use RTTI)
- the meta object system, allowing you to introspect objects at runtime, think of something like C#'s reflection - take a look at things like QMetaObject[2] and QMetaMethod[3], etc.
this includes runtime creation of instances of a given class, looking up a method by name and invoking it with random arguments, etc...
- the properties system (Q_PROPERTY), allowing things like QML to set properties on C++ objects from javascript
- signals and slots
[1]: http://labs.qt.nokia.com/wp-content/uploads/2011/05/Qt5.pdf
[2]: http://doc.qt.nokia.com/latest/qmetaobject.html
[3]: http://doc.qt.nokia.com/latest/qmetamethod.html
The difference is Arduino's are fairly forgiving when you throw a funny voltage or analog input at them. the R-Pi has no analog, only 16 GPIO that is designed for short-distance communication on a board. In order to get decent IO you will have to buffer the GPIO in some way, and with this buffer comes the protection that the ATMEL's have already. It will be very easy to break a standard R-Pi without buffering the GPIO, plus compared to an Arduino, there is probably 10x as much code to do the same thing.
Just working with /sys/class/gpio is more work that your average Arduino program.
Wait, no one has mentioned this yet?
So, with the Raspberry Pi running the QT 5 operating system, of course this combination will be called ...
the QT Pi
Thank you, thank you. I'll be here all week ...
404555974007725459910684486621289147856453481154 in hex is "You sank my Battleship?"
[GPG key in journal]