Accueil Actualités IT Pro
Conception Cycle de vie du logiciel
- Conception
- UML
- Merise
Java Plateforme et langage Java
- Java
- Spring
- Dév. Web Java
- Android
- Eclipse
- NetBeans
.NET Microsoft Framework .NET
Dév. Web Développement Web et Webmarketing
- Développement Web
- AJAX
- Apache
- ASP
- CSS
- Flash / Flex
- JavaScript
- PHP
- Ruby & Rails
- Web sémantique
- Webmarketing
- (X)HTML
EDI Environnements de Développement Intégré
- EDI
- 4D
- Delphi
- Eclipse
- LabVIEW
- NetBeans
- MATLAB
- Visual Studio
- WinDev
- Visual Basic 6
- Lazarus
- Qt Creator
Langages Langages de programmation applicatifs
- Langages
- Assembleur
- C
- C++
- C#
- Pascal
- Perl
- Python
- Visual Basic 6
- VB.NET
- XML
- Autres
SGBD Systèmes de Gestion de Bases de Données
- SGBD & SQL
- 4D
- Access
- DB2
- Firebird
- InterBase
- MySQL
- Oracle
- PostgreSQL
- SQL-Server
- Sybase
Office Bureautique pour l'entreprise
- Microsoft Office
- Access
- Excel
- Word
- Outlook
- PowerPoint
- SharePoint
- Microsoft Project
Solutions d'entreprise Autres logiciels pour l'entreprise
Applications Applications logicielles
Systèmes Logiciels et matériels systèmes
- Systèmes
- Windows
- Linux Professionnel
- Sécurité
- PC
- Mac
- Réseau
- Mobiles
- Green IT
- Virtualisation

RSS
Atom

Accueil Qt
Forum Qt
FAQ Qt
Doc Qt
Tutoriels Qt
Outils Qt
Sources Qt
Livres Qt
Blog Qt
Qt TV
PyQt & PySide

· Page d'accueil · Toutes les classes · Toutes les fonctions · Vues d'ensemble ·

Organizer Synchronous API

Introduction

The Organizer Items Synchronous API enables a client to synchronously fetch, update, or remove item data from an item manager. A synchronous API is of most use to clients who wish to perform simple requests where user interface responsiveness is not critical. Synchronous calls to an item manager will block until they are completed, and therefore should not be performed in the GUI thread (especially if the manager is a frontend to an online service or long-latency datastore). The main advantage of the synchronous API is its simplicity and convenience.

Most operations which may be performed using the synchronous API may also be performed using the asynchronous API. It is recommended for most applications that the asynchronous API be used where possible.

Using The API

The synchronous API offered by the Organizer Items module is available through the QOrganizerManager class. It consists of three major categories:

Organizer Item Manipulation
Item Collection Manipulation
Schema Manipulation

Organizer Item Manipulation

The most common type of operation that clients will perform involves retrieval or modification of organizer items. For in-depth information about item manipulation, please refer to the main Organizer API page.

The QOrganizerManager class provides API for accessing the IDs of items which are stored in the manager:

QOrganizerManager::itemIds()

The synchronous, singular item manipulation functions offered by the QOrganizerManager class are:

The synchronous, batch item manipulation functions offered by the QOrganizerManager class are:

QOrganizerManager::items() which returns persistent and generated items within a given time period
QOrganizerManager::itemsForExport() which returns only persistent items
QOrganizerManager::itemOccurrences() which returns the occurrences of a specific recurring item
QOrganizerManager::saveItems() which may be used to update a recurring item, or save an exceptional occurrence
QOrganizerManager::removeItems() which may be used to remove a recurring item or exceptional occurrence

Item Collection Manipulation

Every item is saved in a collection in a manager. Each collection has various properties which, if the manager supports such operations, may be modified by clients. For in-depth information about collections, please refer to the main Organizer API page.

The synchronous API offers the following functions to manipulate collections:

QOrganizerManager::defaultCollection() returns the default collection of the manager
QOrganizerManager::collections() returns all collections in the manager
QOrganizerManager::saveCollection() updates an existing collection or adds a new collection
QOrganizerManager::removeCollection() removes an existing collection (and deletes any items it contains)

It also offers a convenience function which returns a collection with a given collection id.

Schema Manipulation

The schema supported by a engine is the list of detail definitions which are supported by the engine. For in-depth information about the schema, please refer to the main Qt Organizer Schema page.

The synchronous API offers several functions to retrieve or modify the schema supported by an engine. Engines which support these types of operations must report to clients that they support the QOrganizerManager::MutableDefinitions feature.

QOrganizerManager::detailDefinitions() returns all definitions in the schema for a particular item type
QOrganizerManager::detailDefinition() returns the definition of a particular name from the schema for a particular item type
QOrganizerManager::saveDetailDefinition() which updates or adds a definition to the schema for a particular item type
QOrganizerManager::removeDetailDefinition() which removes a definition from the schema for a particular item type

Error Reporting

When a synchronous operation fails, clients need to be able to retrieve error information associated with that synchronous operation. You can call the QOrganizerManager::error() function directly after a failing synchronous operation to determine why it failed.

For some synchronous operations (for example, batch save or remove operations) it is possible that multiple errors may occur during the operation. In those cases, clients can call QOrganizerManager::errorMap() to retrieve a map of input index to error, which will be filled by the function as required. The QOrganizerManager::error() function will report the overall operation error.

Best Of

Actualités les plus lues

Semaine

Mois

Année

Le blog Digia au hasard

Créer des applications avec un style Metro avec Qt, exemples en QML et C++, un article de Digia Qt traduit par Thibaut Cuvelier

Le blog Digia est l'endroit privilégié pour la communication sur l'édition commerciale de Qt, où des réponses publiques sont apportées aux questions les plus posées au support. Lire l'article.

Communauté

Ressources

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.2
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 !

Responsables bénévoles de la rubrique Qt : Thibaut Cuvelier - Jonathan Courtois -

Developpez.com

Services

Partenaires