m (→MeeGo Platform API) |
m (→Planned improvements for later releases) |
||
| Line 18: | Line 18: | ||
=== Planned improvements for later releases === | === Planned improvements for later releases === | ||
| - | According to the recommended usage of the libraries, | + | According to the recommended usage of the libraries, the API will be divided into the following categories for future releases of MeeGo: |
* Common (APIs such as WRT, Gstreamer, Pulseaudio) | * Common (APIs such as WRT, Gstreamer, Pulseaudio) | ||
| Line 24: | Line 24: | ||
* IVI | * IVI | ||
* Netbook | * Netbook | ||
| + | * Other device categories as needed | ||
The categories will reflect the contents of sysroots and images provided with MeeGo SDK releases. | The categories will reflect the contents of sysroots and images provided with MeeGo SDK releases. | ||
//Draft for review. Text to be added to Platform API main page, here: http://apidocs.meego.com/1.1-api-preview/platform/html/index.html//
MeeGo 1.1 includes additional libraries that can be used when creating applications. The APIs listed here are not in the scope of MeeGo API and have no forward compatibility promise. The APIs listed here are considered stable and may be useful for some application developers, specifically for game development and complex multimedia applications.
NOTE: Application developers are recommended to use MeeGo API. MeeGo API and Qt scope will continue to evolve. Future releases of MeeGo API shall cover some of the capabilities listed on this page.
MeeGo Platform API for MeeGo 1.1 consists of:
NOTE: In MeeGo 1.1 release, MTF is included in the core sysroot containing the MeeGo API libraries. Thus, MTF library does not need to be installed, separately.
According to the recommended usage of the libraries, the API will be divided into the following categories for future releases of MeeGo:
The categories will reflect the contents of sysroots and images provided with MeeGo SDK releases.
NOTE: Qt, QML, and Qt Mobility are the recommended technologies to use for all development, when possible. As the multimedia support provided by these frameworks continues to improve, linking directly with MeeGo Platform API libraries will eventually be unnecessary.