Run with MeeGo
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.
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.
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.
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.
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.
|Designing Electronics with Linux||May 22, 2013|
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- Designing Electronics with Linux
- What's the tweeting protocol?
- Kernel Problem
2 hours 1 min ago
- BASH script to log IPs on public web server
6 hours 28 min ago
10 hours 4 min ago
- Reply to comment | Linux Journal
10 hours 36 min ago
- All the articles you talked
13 hours 19 sec ago
- All the articles you talked
13 hours 3 min ago
- All the articles you talked
13 hours 4 min ago
17 hours 29 min ago
- Keeping track of IP address
19 hours 20 min ago
- Roll your own dynamic dns
1 day 33 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?