Home ›

Run with MeeGo

Issue 203

From Issue #203
March 2011

Apr 30, 2011  By Ibrahim Haddad
 in
What's new in 1.1?
MeeGo v1.1 Handsets UX

Today's users are demanding more powerful and feature-rich devices to take with them on the go. Next-generation smartphones allow users to enjoy a rich and dynamic Internet experience, watch HD movies and multitask like never before on a small-form-factor device. The MeeGo platform is specifically designed to enable the application and services ecosystem for these mobile, rich Internet and media-centric devices.

The MeeGo v1.1 Handsets UX (Figure 10) provides a technology snapshot that offers key handset technologies, such as cellular, connectivity, sensors and mobile browsing, as well as a basic development UX for voice calling, SMS messaging, Web browsing, music and video playback, photo viewing and connection management.

With this project release, developers will be able to work on future device and user experience software development, while simultaneously participating in the MeeGo Project to complete the Handset UX in the upcoming 1.2 release.

Figure 10. The MeeGo Handset Dialer (photo credit: meego.com)

MeeGo on Handsets

If you have access to a Nokia N900 handset or an Aava Handset, you can find step-by-step instructions on how to install and run MeeGo on those devices from meego.com/devices/handset. The instructions will guide you through installing the root filesystem on an external micro-SD card. Give it a try, and have fun experimenting with it.

MeeGo SDK 1.1 Beta

The MeeGo SDK 1.1 beta was released on November 10, 2010, and it's available for download along instructions from meego.com/developers. It enables application developers to develop, install and debug applications, as well as run applications on the Nokia N900, Netbook and Aava devices with MeeGo. For developers without reference hardware, QEMU (qemu.org) provides an emulated environment for debugging and testing applications.

The MeeGo Project encourages developers to use the MeeGo API, which currently consists of Qt 4.7 and Qt Mobility 1.0. The MeeGo API comes with a forward-compatibility promise and will be extended in future releases. The final nonbeta version of the SDK will be aligned with the MeeGo compliance specification (being finalized at the time of this writing). More information on MeeGo compliance is available at wiki.meego.com/Quality/Compliance.

Conclusion

MeeGo is an open-source project developed in public under the auspices of the Linux Foundation. Since it was announced in February 2010, the world has been able to watch and participate as the project builds up and delivers the core software stack in addition to three reference user experiences for handsets, IVI systems and Netbooks, with more to come as MeeGo also targets connected TVs and tablets.

The development continues following a six-month release schedule. MeeGo 1.2 is scheduled for April 2011. Currently, there are hundreds of features targeting MeeGo 1.2 that already have been filed in the MeeGo Featurezilla (a tool that tracks feature development). The development tree of MeeGo 1.2 is open, and development is ongoing.

Resources

MeeGo Project: www.meego.com

Developer Resources: meego.com/developers

Mailing Lists: meego.com/community/mailing-lists

IRC Discussions: meego.com/community/irc-channel

MeeGo Source Code: meego.gitorious.org

MeeGo Bugzilla: bugs.meego.com

MeeGo Forums: meego.com/community/forum

Precompiled Images: meego.com/downloads

MeeGo Releases: meego.com/downloads/releases

MeeGo OBS: wiki.meego.com/Build_Infrastructure

Ibrahim Haddad manages the Linux Foundation's Mobile Linux initiatives and works with the community to facilitate a vendor-neutral environment for advancing the Linux platform for next-generation mobile computing devices. Ibrahim is a Contributing Editor at Linux Journal.

______________________

White Paper
More Resources
Fabric-Based Computing Enables Optimized Hyperscale Data Centers

Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.

Learn More

Sponsored by AMD

White Paper
More Resources
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions