More Post-MeeGo Musing: Community Echoes

Ever since Intel’s MeeGo-cedes-to-Tizen announcement, I’ve been in a slightly unfocused state.  It’s familiar territory– when Maemo was set aside by Nokia for MeeGo, there was the same quandary: what now?  Better yet, what next?

After a little over two years of scant free time, I’m finally working normal hours.  So that liberates me for more community engagement, aka the stuff I really love.  It also frees me up to think.  But looking back on the past 5 years of support for open source projects with great promise but ultimate abandonment, I’m left to wonder what to target. 

A Qt QML Beginner’s Project: MotoRing, part 2 – Rewind and Reveal

Finally, here’s the much-demanded second part to this QML beginner-focused series.  Okay, one guy asked, but he sounded really interested.

I said at the end of the first article that I would progress to the next phase in this one.  But the request for a screenshot of the app at this point got me to thinking that it would be worth more to fledgling QML developers if I backed up and broke down the code.  So let’s do it.  There’s a lot to cover, so I’ll spread it across two or three articles.

A Qt QML Beginner’s Project: MotoRing, part 1 – GPS

I unloaded some Qt newbie frustration the other day detailing my first serious efforts to code for the Nokia N9.  Now I’d like to step back a bit and outline the actual project, and in subsequent posts walk other newcomers through my coding journey of pleasure and pain.

First a disclaimer: I’ve been programming for over 25 years.  That has included COBOL, Forth, Logo, DOS/VAX/Unix batch commands, Basic, LISP, Pascal, C, JavaScript and Visual Basic (both COM and .NET).  While I could work minor wonders with scripting and compiled linear languages, I found that I have been most productive in event-driven VB.Net.  Readers should know that I am not targeting an audience that’s totally new to programming, but rather, programmers who like me are experienced with other languages and platforms but new to Qt.

I really wasn’t very apprehensive about Qt, especially the mature 4.7.  Friends kept telling me how easy it was, and the Qt Creator environment did not look difficult at all at first glance. 

Why I am Every Qt Expert’s Worst Nightmare

As I’ve noted before, I have been interested in Qt development for some time and finally got to where I could allocate the hours to learning.  I missed out on local Qt training a while back so I’m dependent on documentation along with patient people online.

The latter have been a huge help.  I’ve encountered some weird and frustrating situations from which many friends have rescued me.  The former, however, have been severely lacking.  But let me share the pain with you progressively.

I decided to create an application for the Nokia N9.  The app will make use of GPS and cellular services mainly, and shouldn’t be very complicated.  I chose Qt Quick because I wanted to see how mature QML really is at this point.  Plus I’m allergic to C++. 

Confessions of an APPathetic User

I’m going to confess something that’s likely to cost me Twitter followers, kill future career prospects and launch a mild Comment war:

I’m not much of an app user.

And I can’t understand those who are, either.  Well, I can align with the casual user.  The few utilitarians out there.  Those discriminating sorts who reserve their precious device storage space for more valuable content.  Like songs, photos and LOLcats.  

Works for Me

Want to stop productive bug reporting in its tracks? Want to get the trolling rolling? Toss a flaming “Works for me!” into the mix and stand back.  

Maemo is Dead… Long Live Maemo

Source: http://www.maemoit.org

Before I launch into coverage of the MeeGo Conference in San Francisco this past week, I’d like to touch on a touchy and related issue:  the future of Maemo.

As most readers here are already aware, Maemo was Nokia’s enigmatic attempt at a Linux operating system for mobile devices.  I don’t want to go into the history in this article; it’s easy enough to find on this blog and elsewhere and I want to focus clearly on the future.  

Wrap-up at MIX11

Me in the Pictage booth

Sorry for the delay– here’s the MIX11 wrap-up!

Keynotes

Wednesday MIX11 keynotes opened with a video that turned out to have been developed by 24-year old Brandon Foy, by request of Microsoft after being made aware of a fan video he had made.  Microsoft VP Joe Belfiore told the audience that if the Youtube video gets 200000 views, then Brandon’s video will be made an actual Microsoft commercial.  So support crowdsourcing and help the guy out (he’s at 83890 as of this writing)!

Joe went on with a lengthy apology/explanation for the latest WP7 update delay.  Their goal, he continued, is ‘more, clearer, disclosure’.  The complexities of the mobile phone world seem to have caught Microsoft by surprise… something perhaps Nokia can help them with (Joe is excited at the prospects, and at one point invited Nokia’s Marko Argenti onstage to present on their behalf).  

Linus Torvalds, Linux, and the Issue of Software Quality

Friend and Maemo/MeeGo bugjar master Stephen Gadsby alerted twitterites yesterday to a Fedora bugzilla flamefest, and at first blush it made for interesting comic relief.  Who doesn’t enjoy a good Internet argument?

But a second read sobered me up quickly.  The bug turned out to be an issue introduced into the crucial (and occasionally controversial) glibc code library that doesn’t appear to have been sufficiently regression-tested.  The code change reason is described as an execution speed improvement, but it appears to have come at the expense of pre-emptive error-checking.

Most people aren’t going to care about the technical reasons underlying the discovered bug.  Most will, instead, be concerned with its impact.  And that gets us to the reason behind me writing today.  

Play-by-Air Gaming

A long time ago in a DOS-based world far, far away, there were Play-by-Mail games.

I was involved in one called Galactic Anarchy, run by a friend and  business colleague, as a tester and (of all things) cartoonist.  The concept was simple: a turn-based space conquest game played over snail mail (and later also email) populated by several character types (“races”), filled with interesting artifacts and of course founded on certain rules.  Players examined the status of their fleets and owned worlds, and then issued commands to move, attack, defend and anything else the command set supported.