|
|
Log in / Subscribe / Register

Playing with MeeGo 1.0

By Jonathan Corbet
June 7, 2010
The MeeGo project - the result of the merger between Moblin and Maemo - released version 1.0 of its core platform on May 25, accompanied by the first iteration of its "Netbook user experience." Your editor, who happens to have a netbook system sitting around, decided to give this release a try to see what has happened since the Moblin review written last November. While the overall feel of the system is quite similar, there has also been some real progress; MeeGo feels more like a finished product than Moblin did.

[Home screen] The overall user interface concepts laid out by Moblin have not changed much in the merger with Maemo. There is still a home screen meant to provide access to recently-used activities, be they web pages or communications with others. The line of icons at the top still shows what the MeeGo developers think people will want to do with netbooks: talk to people, browse web pages, play music, etc. The quality of the graphics and animation have improved somewhat, but the basic interaction model is what Moblin had before.

There is an interesting distinction between running an activity from the top icon bar and running an application. Applications run in "zones," which are essentially virtual desktops which hold one window each. Moving between zones is done quickly enough by putting the pointer at the top of the screen, selecting the zones icon (yielding a display of the active zones), then picking the new destination; it's an experience similar to holding down the "home" key on an Android system. But an application run from the top bar (the music player, say, or the web browser) is treated differently; it has no zone and cannot be jumped into and out of that way. Your editor finds this to be a bit of a confusing inconsistency.

Speaking of web browsers, MeeGo now uses Chrome (or Chromium, one can choose at download time) for web access. Chrome is, of course, a reasonably mature and quite functional browser. The "Mozilla headless" mechanism used with the Moblin browser worked, but not all users were happy with the experience; Chrome, perhaps, will be better received.

While most things work nicely, one occasionally encounters a rough edge. Your editor was able to crash the desktop by playing with an external monitor. MeeGo lets the user choose between the built-in or an external monitor, but does not want to run both at the same time - not even in [Slider] mirrored mode. One other thing that has jumped out is that options which are toggles are controlled by a widget which looks like a sliding switch. There are no labels, though, so it's not always obvious whether the option is enabled or not.

The big sliders are typical of the way the MeeGo interface looks, though; buttons and such are big. Netbooks tend not to have touchscreens, but this user interface is clearly headed in the direction where everything has to be finger-sized. The interface is also still very much GNOME-based, despite MeeGo's plan to move over to Qt. Mail is handled by Evolution, the media player is Banshee, etc. Perhaps that will change over time; evidently the tablet user experience is more Qt-heavy.

[Gadgets] While exploring options for customizing the top icon bar, your editor stumbled across "gadgets," a relatively hidden feature that, perhaps, shows where the MeeGo developers plan to go. Gadgets are little applications which can be placed on a special screen; there are weather monitors, silly games, slideshow applications, etc. The interface for choosing them is awkward (browse through all 1000 of them in some strange order, four at a time) and there doesn't seem to be a way to place them somewhere useful, like the home "MyZone" screen. But it has the look of the beginnings of some sort of "application store" mechanism which is separate from the normal package management system used by MeeGo.

There is one other difference between Moblin and MeeGo that your editor has noticed: Moblin was a multi-user system with the ability to set up multiple independent accounts. MeeGo, instead, has a single account (called "meego," but one has to look hard to find that out) and no provision for creating or logging into any others. MeeGo devices, it seems, will be more like phones than Linux computers; they are highly personal devices that one does not ordinarily share.

Perhaps that is the future of Linux on the desktop - at least, Linux on the relatively small desktop. Like Android, it's not the sort of Linux experience that we are used to, though MeeGo is far closer to "traditional" Linux than Android is. But perhaps it's an experience that will bring in a new set of users; once they get used to this environment, the full Linux experience will be there for them to discover. That should be a good thing.

First, though, MeeGo needs to get out there on devices and into the hands of users. Evidently a number of MeeGo-based devices were on display at Computex, which is a start, but there are not a whole lot of deployed systems out there. So MeeGo is far behind other systems, including Android, which are aiming for very similar markets (though it is ahead of ChromeOS, which won't have a stable release for a few more months). Coming from behind in a highly competitive market is a hard thing to do, even when the market is expanding. But MeeGo has a lot of resources behind it and a lot of thought going into its design. Even if it's a bit of a dark horse, it's worth keeping an eye on.


to post comments

Playing with MeeGo 1.0

Posted Jun 7, 2010 20:43 UTC (Mon) by arjan (subscriber, #36785) [Link]

Moblin was also single user...... never was multi user.

For both Moblin and Meego, the user ID/password/etc get set up during installation (moblin) or during the first boot (meego).
If you only run the live image you'll not run this part of the system (which to be honest, is what pretty much every livecd for any OS does)

Playing with MeeGo 1.0

Posted Jun 7, 2010 22:51 UTC (Mon) by Darkmere (subscriber, #53695) [Link]

The Meego homepage mentions that a third version is available as well, the "Developer images" which would be more suitable for virtualised environments if I read it correctly.

However, so far I have not been able to find them anywhere but in the blurb on the "Download" page.

stick a fork in it

Posted Jun 8, 2010 4:47 UTC (Tue) by b7j0c (guest, #27559) [Link] (8 responses)

oh had they only been two years earlier, this might be a viable product. the mobile/small platforms race is over, its android vs iphoneos from here forward.

the article seems to indicate that meego is going from gnome to qt? huh? sounds like a rewrite. if they have any hope of this project being relevant, they should polish up what they have and get it on a device from a company people have heard of that they can play with at fry's or best buy.

nokia is in serious danger of being left out of the smartphone/mobile tidal wave if they continue to pursue the microsoft-like mentality that current marketshare dictates future relevance. prior to the iphone, ballmer wouldn't take apple seriously because hey, they only had 6% marketshare. whoops. now its probably only a matter of time until winmobile either gets killed or gets ignored. nokia is on the way to this same fate, as well as rimm

unless rimm and nokia realize their current market share is based on products they built four years ago, they're done. they need to get on android asap

as for intel, i really don't know why they waste their time playing in software. i appreciate their contributions to linux...but come on, they should stick to what they know. that ain't mobile os's

the end of history

Posted Jun 8, 2010 8:34 UTC (Tue) by wingo (guest, #26929) [Link] (1 responses)

Is that you, Francis Fukuyama? :)

the end of history

Posted Jun 8, 2010 16:27 UTC (Tue) by b7j0c (guest, #27559) [Link]

i'm not declaring the end of history by any stretch, but the window for meego opened and closed a long time ago

stick a fork in it

Posted Jun 8, 2010 8:57 UTC (Tue) by epa (subscriber, #39769) [Link] (1 responses)

Doesn't your argument contradict itself? First you say that the race is only between Android and Iphone - the two main players right now - but then you say that current marketshare is irrelevant...

stick a fork in it

Posted Jun 8, 2010 16:25 UTC (Tue) by b7j0c (guest, #27559) [Link]

i'd be contradicting myself if meego was actually available on a product i can buy

stick a fork in it

Posted Jun 8, 2010 13:21 UTC (Tue) by zdzichu (subscriber, #17118) [Link] (2 responses)

It seems that they support Qt for user interface. And Qt will be used for UI on Handheld devices and maybe more. Netbook UI is in GTK+/Clutter. There are talks about other UIs: for TVs, In-Vehicle Entertainment and maybe others.
Each MeeGo distribution is one selected UI + common framework. Framework (GNOME Mobile) consist mainly in D-Bus consumable services. You can easily use them from both QT and GTK+ stacks.

stick a fork in it

Posted Jun 8, 2010 16:30 UTC (Tue) by b7j0c (guest, #27559) [Link] (1 responses)

what? meego is potentially either qt OR gtk, depending on the device???? so how does an application developer build meego apps? build a qt AND a gtk version??

who is in charge of this thing???

stick a fork in it

Posted Jun 8, 2010 16:58 UTC (Tue) by arjan (subscriber, #36785) [Link]

Applications for MeeGo are written in Qt, period.

Some of the UI elements like the Window manager might not use Qt themselves, but that's a different story and does not impact applications.

stick a fork in it

Posted Jun 10, 2010 10:30 UTC (Thu) by liljencrantz (guest, #28458) [Link]

Meh. People used the same argument against Android less than a year ago - too late, RIM and Apple already own the market. The key to success for Nokia is managing to get their Symbian users to move to MeeGo. If Nokia manages to provide a really smooth migration strategy from Symbian (Same applications, trivial to migrate your whole profile, etc.), and if they manage to push out multiple phones with different feature sets, form factors and price points all running MeeGo, and if the first MeeGo phones are significantly more polished than the n900 UI-wise, then Nokia will succeed.

Those are a lot of ifs, but Nokia has a lot of talented people working for them these days. They still have a shot.

Playing with MeeGo 1.0

Posted Jun 8, 2010 7:29 UTC (Tue) by jku (subscriber, #42379) [Link] (1 responses)

The issue with the sliding switches is a truly embarrassing bug that was the result of last minute style changes. I'm sure the switch state is going to be a lot more evident after the first update.

Playing with MeeGo 1.0

Posted Jun 8, 2010 12:46 UTC (Tue) by nedrichards (subscriber, #23295) [Link]

Yep, it's fixed in git, along with a few other annoying visual tweaks.

Playing with MeeGo 1.0

Posted Jun 8, 2010 18:49 UTC (Tue) by oak (guest, #2786) [Link] (1 responses)

> The MeeGo project - the result of the merger between Moblin and Maemo

Does "the result" mean that the merger of these two has already finished? And whatever is publicly done in maemo.gitorious.org and meego.gitorious.org aim for the same distro?

Playing with MeeGo 1.0

Posted Jun 10, 2010 8:19 UTC (Thu) by Robin.Hill (subscriber, #4385) [Link]

Maemo 5 is still a separate platform, so ongoing work on that will presumably be being done in maemo.gitorious.org.

Playing with MeeGo 1.0

Posted Jun 10, 2010 10:27 UTC (Thu) by Lovechild (guest, #3592) [Link] (2 responses)

I've been using MeeGo 1.0 on my netbook since it was released. Outside being frightfully easy to crash and the abrt reporter being much less handy than apport it still lacks some creative tools. I really miss a "zone" for tomboy like document editing with exporting to my blog. For those coffee shop writing sessions it remains the largest missing piece in the MeeGo ntbook puzzle for me.

I don't care about twitter or facebook but I do care about having some form of handy offline capable light text editing. Tomboy here seems to be a perfect tool to build on since it is very well suited for the job and adds some desirable interlinking functionality.

Playing with MeeGo 1.0

Posted Jul 1, 2010 9:36 UTC (Thu) by kraftman122 (guest, #65942) [Link] (1 responses)

Thanksfully MeeGo is mono and bloated tomboy free. This is even too bloated to use on the desktop and you want this on a phone? :) Btw. I never find this useful. Thanksfully MeeGo uses Qt.

Playing with MeeGo 1.0

Posted Jul 1, 2010 11:42 UTC (Thu) by Darkmere (subscriber, #53695) [Link]

Huh? Doesn't MeeGo use Banshee, which is built in Mono/gtk#?

OT: Alternative to Meego for N900 etc.?

Posted Jun 10, 2010 22:05 UTC (Thu) by debacle (subscriber, #7114) [Link] (2 responses)

I'm not too interested in Meego. For personal taste I prefer Gtk+ and .deb over Qt and .rpm. So is there any work going on with the traditional Maemo path?

OT: Alternative to Meego for N900 etc.?

Posted Jun 11, 2010 2:30 UTC (Fri) by TRS-80 (guest, #1804) [Link] (1 responses)

Linaro has promise for Gtk+ and .deb lovers like you and me.

OT: Alternative to Meego for N900 etc.?

Posted Jun 12, 2010 9:37 UTC (Sat) by vachi (guest, #67512) [Link]

But what about people who like Qt and .deb like me? :-)

Playing with MeeGo 1.0

Posted Jun 15, 2010 14:41 UTC (Tue) by Trelane (subscriber, #56877) [Link]

Count me as waiting on the first MeeGo phone. The n810 is very nice; programming with native code makes life suck much less.

What is the purpose of MeeGo?

Posted Jun 17, 2010 12:14 UTC (Thu) by odie (guest, #738) [Link] (1 responses)

Why are Nokia pursuing a new OS instead of building on Symbian? There are already tons of applications and developers for Symbian and it's free software. What benefits do they foresee with switching to MeeGo?

What is the purpose of MeeGo?

Posted Jun 17, 2010 14:49 UTC (Thu) by macson_g (guest, #12717) [Link]

Symbian is dead. Nokia is really fed with this old, obsolete and unmaintainable mess it became.

They current strategy is to make a Qt to be The Symbian API, and then port all applications with as little effort as possible to other (Linux-based) platforms. This seems to be quite a good strategy, if you'd ask me, and even if they fail, the entire community will benefit in the process from improved Qt (and other stuff as well).


Copyright © 2010, Eklektix, Inc.
This article may be redistributed under the terms of the Creative Commons CC BY-SA 4.0 license
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds