Intel is holding its developer centric conference, IDF in China and that has brought up some interesting information about MeeGo on handheld devices. We have a handset feature list and a few screenshots of the OS. What is not clear is whether this is what Intel is proposing or something which has been agreed on by Nokia.
If you look at the chart above, under the user experience tab, Display Orientation is mentioned and this is clear indication that portrait mode is being worked upon in MeeGo. All the other core functionality that you would expect in Nokia devices is also present.
These screenshots clearly showcase portrait mode functionality, but what should be kept in mind is that they are in no way depec tive of what the final UI might look like when Nokia launches its devices. It will probably help shape MeeGo 1.0 but what Nokia does to the UI on top of that is anyone’s guess.
As you can see, MeeGo will look very different from what Maemo 5 looks like today. Interesting times.
As promised, Day 1 is here and with it comes the first release of MeeGo for the N900. As of now this release is intended for the experienced N900 hackers only and should be of little interest to the majority of N900 users. Once installed on the N900 you will see that there is no GUI (Graphical User Interface) and the activity is limited to the terminal only.
If you have decided that you absolutely need MeeGo on your N900, there are numerous ways to install it. You can get pre-built images or make one of your own. You can do a native install or a chroot install or try out alternative boot methods mentioned. The ARM wiki for Meego has detailed instructions, depending on the method you choose:
Obtaining MeeGo images for N900
Installing MeeGo on N900
Native installation method is intended only for experienced N900 hackers at this point. If you choose to try it, you are doing it completely on your own risk.
Chroot install is safer way to try MeeGo without erasing Maemo 5 from your N900 device. Still, you need to know what you are doing.
At any point, if you want Maemo 5 back, follow this tutorial:
At the MeeGo announcement there wasn’t much clarity on whether Nokia was going to keep the ‘Maemo 6’ brand for now and then transition into MeeGo, but a simple post from Quim Gil, of Nokia’s Maemo Division requesting the renaming of the Maemo 6 / Harmattan sub forum at Maemo.org to MeeGo / Harmattan has brought much needed clarity to the picture.
In addition to the request he has taken the time to clarify a few aspects which I am sure all of you are very interested in. Below are a few extracts from his post, nothing surprising but still worth a read.
“Maemo 6 will not be used by Nokia as a brand since all the marketing effort around the software platform will be around MeeGo.
To be clear: this is not about “ditching” or “abandoning” any platform. The Harmattan program keeps working with the same plans than last week, no matter the name of the product they will deliver. Maemo 6 and Moblin 2.x merge and have a successor called MeeGo. Current Maemo people will look at it and will say “looks like his mother!”. Current Mblin people will look at it and will say “looks like his father!” (or choose your preferred gender) Of course you will see changes compared to Maemo 5, but these changes were coming anyway with Maemo 6.
What does this mean exactly for Harmattan/MeeGo? It means different things for different people:
- For end users nothing really changes, apart from a name most of them were not aware of anyway.
- For application developers not much changes. Harmattan’s developer offering is based on Qt 4.6 + Qt Creator, Web Runtime + Aptana. Same for MeeGo and btw same for Symbian. Harmattan *might* have extended APIs unique to Nokia devices (e.g. Ovi APIs), but we’ll see and this is part of the MeeGo flexibility anyway. Wait for the SDKs to be released and then we can discuss in more detail. There will be also the APIs available for those willing to use them, provided directly by other open source components in the platform (e.g. GStreamer). Developers will be of course free to use them, at the expense of loosing compatibility with Symbian, and with MeeGo… depends on the component and to be seen as soon as there is a detailed MeeGo architecture public. Then there will be the obvious difference in packaging (deb still for Harmattan, rpm for MeeGo) but this won’t be the big issue and anyway compatibility with Symbian implies specific packaging as well.
- For those caring about the platform in depth, Harmattan =! MeeGo. If we would make Harmattan identical to MeeGo then we would need to postpone dates and, really not for a good reason. Not a reason for app developers (the API is there anyway) and not a good reason for end users, who could not care less about packaging and some obscure middleware components. This is the only reason making Ari Jaaksi refer to Harmattan as a “MeeGo instance” instead of just “MeeGo product”.
This is why we are dropping the “Maemo 6″ *brand* while keeping all the Harmattan development full speed and in the same direction that it was.”