              
Qt Mobility Project APIs Overview |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Bearer Management | An API to control the system's connectivity state. |
|---|---|
| Contacts | An API enabling clients to request contact data from local or remote backends. |
| Location | The Location API provides a library for distributing and receiving location data using arbitrary data sources. |
| Messaging | The Messaging API enables access to messaging services. |
| Multimedia | Provides a set of APIs to play and record media, and manage a collection of media content. |
| Publish and Subscribe | The Publish and Subscribe API, containing Value Space, enables applications to read item values, navigate through and subscribe to change notifications. |
| Qt Service Framework | A set of Qt APIs to that allows clients to discover and instantiate arbitrary services. |
| Sensors API | The Sensors API provides access to sensors. |
| System Information | A set of APIs to discover system related information and capabilities. |
| Versit API | An API to manage Versit documents. |
These APIs give the developer a range of desirable functions for a mobile platform, but now these functions become possible on platforms not traditionally associated with some of the features. A mobile device using the Qt Mobility Project API would be able to
- Locate services on-board or remotely. Find an optimal connection to the network for the particular service.
- Services built on top of these APIs would include Internet applications such as email and web browsing.
- Multimedia features enable image and video capture with audio , audio recording, and the playing of music or video clips.
- Location will make the device aware of its geographical location to support GIS applications.
- Publish-Subscribe enables communication between separate objects whether local or remote to the device.
The New Qt APIs deliver to developers an enabling package. It will be used by developers to build a variety of applications and services that are mobile capable or familiar to mobile users, irrespective of whether the platform is mobile or not. This means that there is the possibility of easy transfer of user experience from PC to phone or vice versa.
Namespace
The QtMobility APIs are placed into the QtMobility namespace, with the important exception of Multimedia. This is done to facilitate the future migration of Mobility APIs into Qt.
See the Quickstart guide for an example on how the namespace impacts on application development.
Getting Started
To get started with Qt Mobility see the
For users on the supported Symbian platforms, shown at the bottom of this page, see the instructions at the Qt For Symbian Developer's Library
Known Issues
For a list of known issues and an additional details on feature supported see Release Notes of the QtMobility Project 1.0.2 patch release.
For a overview of Platform Compatibility see Platform Compatibility.
The New Qt APIs
Bearer Management
Although not a network manager, this component manages the connectivity state of the device to the network. So it does not manage network configurations, which are the role of the platform provider, but it does allow the user to start or stop network interfaces. Some higher level management of the connection session may also be possible as well depending on the platform.
Some platforms can have a set of grouped access points perhaps based on a common purpose. Bearer Management allows comparison and prioritization of the access and use of these points.
The aim of Bearer Management is to reduce the need for the developer to be concerned about trying to locate the best connection from a list of possible IP bearers and 3G connections. The user can select the best or it can be selected transparently so that WLAN roaming can occur seemlessly.
Some examples of the Bearer Management functionality,
- On demand use of the appropriate Access Point. When a user starts to use a browser, the appropriate access point is selected from those available and a connection is transparently made.
- Always-on applications such as email or IM roam automatically between cellular packet data and WLAN networks. The application developer is in control and for example the application can gracefully close TCP connections over the old bearer after setting up new TCP connections over the new bearer.
- Application developer can create a settings user interface, where the user can select a certain connection to be used with the application
- A connection manager application can be implemented with Qt. This application enumerates available connections, shows counters, and allows the user to connect or disconnect
For more details, see the Bearer Management API overview.
Contacts
The structure and retrieval of contact data from local or remote backends. It includes the ability to create, edit, list, delete and lookup contact information whether it is stored locally or remotely.
For more details, see the Contacts API overview.
Publish and Subscribe
Will enable context sensitive access to information in future releases. Data is organized as a tree, with data being able to 'shadow' other data with the 'same key', a string specifying the leaf or node. The context is an example of a context ontology, a defined set of relationships. As the context changes the values of the objects change but the relationships remain the same. It is intended to be an enabling technology, the basis of a range future applications.
At this stage the API is intended to act as a common communications method between applications, whether local or remote.
For more details, see the Publish and Subscribe API overview.
Location
The C++ API is one layer of this feature. This API provides an easy to use interface that encapsulates basic geographical information obtained from satellite or other sources about the user, including latitude and longitude, bearing, speed and altitude. It will enable a range of geographical applications, for example, maps.
For more details, see the Location API overview.
Messaging
A common interface for handling SMS, MMS, MIME Email and TNEF Email messages. Enables access to messaging services to search and sort messages, notify of changes to messages stored, send messages with or without attachments, retrieve message data, and launch the preferred messaging client to either display an existing message, or compose a message.
For more details see the Messaging API overview.
Multimedia
An API to play audio and video of various formats. Record audio. The playing and managing of an FM radio. This includes the typical functionality you would find on a music and video player, combined with an FM radio.
For more details see the Multimedia API overview.
Sensors
An API for accessing hardware sensors. This covers both high-level sensors such as screen orientation (portrait, landscape) and low-level, real-time sensors such as accelerometer data.
For more details see the Sensors API overview.
Service Framework
A platform independent method of finding Services. A 'service' is an independent component that allows a client to perform a well-defined operation.
The services are implemented as plugins installed on the device and can look for supporting external services running on a central server. E.g. weather, local tourist attractions etc. Default applications can use the layer to locate servers.
Since this is an abstraction layer then the app does not need to be concerned with the underlying protocol, where the servers are, the hardware peculiarities with networking and other low level details.
For more details see the Service Framework API overview.
System Information
An API to discover system related information and capabilities. Information available will cover software version numbers, hardware features, network connection types and status, display, data storage devices, device information and the screensaver.
For more details see the System Information API overview.
Versit
An API to manage Versit ® documents, such as vCards.
For more details see the Versit API overview.
The QtMobility Namespace
The QtMobility APIs are placed into the QtMobility namespace. This is done to facilitate the future migration of Mobility APIs into Qt. See the Quickstart guide for an example on how the namespace impacts on application development.
Platform Compatibility
| Color | Explanation |
| A functional backend for the API on the platform is complete. | |
| A functional backend for the API on the platform is being worked however it is not functionally complete. | |
| A functional backend for the API on the platform is being worked on. At this point it is far from functionally complete or there is no platform specific code inside QDF source code. | |
| A functional backend for the API on the platform is not being worked on. It is possible for others to implement and integrate support. |
Tier 1 Platforms
Primary platforms are the main focus of Mobility API. There platforms are frequently tested by our unit test suite and other internal testing tools. However, the timeline of availability for each backend is subject to change.
Tier 2 Platforms
Secondary platforms include future direction of Qt Mobility API. Contributions to these platforms are welcome.
| API Maturity Level | Tier 1 Platforms | Tier 2 Platforms | ||||||||
| S60 3rd Edition, Feature Pack 1 | S60 3rd Edition, Feature Pack 2 | S60 5th Edition | Symbian^3 | Maemo 5 | Windows CE/Mobile | Windows XP/Vista | Linux | Mac OS X | ||
| Service Framework (in-process) | FINAL | |||||||||
| Messaging | FINAL | |||||||||
| Bearer Management | FINAL | |||||||||
| Publish and Subscribe | FINAL | |||||||||
| Contacts | FINAL | |||||||||
| Location | FINAL | |||||||||
| Multimedia | FINAL | |||||||||
| System Information | FINAL | |||||||||
| Sensors | FINAL | |||||||||
| Versit | FINAL | |||||||||
Email any inquiries and feedback about Qt Mobility to qt-mobility-feedback@trolltech.com And please report any bugs you may find to http://bugreports.qt.nokia.com The icheck tool uses the following third-party component: Open Source front-end for C++ (MIT license), Roberto Raggi <roberto.raggi@gmail.com>, QTMOBILITY/tools/icheck/parser/src
Feedback and bug reports
Acknowledgements
Best Of
Actualités les plus lues
- « Quelque chose ne va vraiment pas avec les développeurs "modernes" », un développeur à "l'ancienne" critique la multiplication des bibliothèques 54
- Créer des applications avec un style Metro avec Qt, exemples en QML et C++, un article du blog Digia traduit par Thibaut Cuvelier 0
- Orientation de l'écran en QML, un article de Christophe Dumez traduit par Thibaut Cuvelier 0
- « Quelque chose ne va vraiment pas avec les développeurs "modernes" », un développeur à "l'ancienne" critique la multiplication des bibliothèques 53
- Les développeurs ignorent-ils trop les failles découvertes dans leur code ? Prenez-vous en compte les remarques des autres ? 17
- Apercevoir la troisième dimension ou l'utilisation multithreadée d'OpenGL dans Qt, un article des Qt Quarterly traduit par Guillaume Belz 0
- BlackBerry 10 : premières images du prochain OS de RIM qui devrait intégrer des widgets et des tuiles inspirées de Windows Phone 0
- Quelles nouveautés de C++11 Visual C++ doit-il rapidement intégrer ? Donnez-nous votre avis 10
- Adieu qmake, bienvenue qbs : Qt Building Suite, un outil déclaratif et extensible pour la compilation de projets Qt 17
- La rubrique Qt a besoin de vous ! 1
- Linus Torvalds : le "C++ est un langage horrible", en justifiant le choix du C pour le système de gestion de version Git 100
- Comment prendre en compte l'utilisateur dans vos applications ? Pour un développeur, « 90 % des utilisateurs sont des idiots » 229
- Quel est LE livre que tout développeur doit lire absolument ? Celui qui vous a le plus marqué et inspiré 96
- Apple cède et s'engage à payer des droits à Nokia, le conflit des brevets entre les deux firmes s'achève 158
- Nokia porte à nouveau plainte contre Apple pour violation de sept nouveaux brevets 158
- Quel est le code dont vous êtes le plus fier ? Pourquoi l'avez-vous écrit ? Et pourquoi vous a-t-il donné autant de satisfaction ? 83
- Le Draft final de la norme C++ 0X validé 181
Le Qt Quarterly au hasard
Implémenter un mutex en lecture et en écriture
Communauté
Ressources
- 91 cours et tutoriels Qt
- F.A.Q. Qt : 200 questions et réponses
- 48 Qt Quarterly, 35 Qt Labs et 22 Qt DevNet en français
- 43 outils Qt
- 99 sources Qt
- 26 binaires Qt
- 6 livres Qt et 9 critiques
- La documentation de Qt 4.7 en français : 157 classes, 70 concepts et 24 modules
- 3 certifications Qt
Liens utiles
Contact
- Vous souhaitez rejoindre la rédaction ou proposer un tutoriel, une traduction, une question... ? Postez dans le forum Contribuez ou contactez-nous par MP ou par email (voir en bas de page).
Qt dans le magazine
| Cette page est une traduction d'une page de la documentation de Qt, écrite par Nokia Corporation and/or its subsidiary(-ies). Les éventuels problèmes résultant d'une mauvaise traduction ne sont pas imputables à Nokia. | Qt qtmobility-1.0 | |
| Copyright © 2012 Developpez LLC. Tous droits réservés Developpez LLC. Aucune reproduction, même partielle, ne peut être faite de ce site et de l'ensemble de son contenu : textes, documents et images sans l'autorisation expresse de Developpez LLC. Sinon, vous encourez selon la loi jusqu'à 3 ans de prison et jusqu'à 300 000 E de dommages et intérêts. Cette page est déposée à la SACD. | ||
| Vous avez déniché une erreur ? Un bug ? Une redirection cassée ? Ou tout autre problème, quel qu'il soit ? Ou bien vous désirez participer à ce projet de traduction ? N'hésitez pas à nous contacter ou par MP ! | ||
Copyright © 2000-2012 - www.developpez.com