The QOrganizerManagerEngineFactory class provides the interface for plugins that implement QOrganizerManagerEngine functionality. More...
#include <QOrganizerManagerEngineFactory>
This class was introduced in Qt Mobility 1.1.
| virtual | ~QOrganizerManagerEngineFactory () |
| virtual QOrganizerCollectionEngineId * | createCollectionEngineId ( const QMap<QString, QString> & parameters, const QString & engineIdString ) const = 0 |
| virtual QOrganizerItemEngineId * | createItemEngineId ( const QMap<QString, QString> & parameters, const QString & engineIdString ) const = 0 |
| virtual QOrganizerManagerEngine * | engine ( const QMap<QString, QString> & parameters, QOrganizerManager::Error * error ) = 0 |
| virtual QString | managerName () const = 0 |
| virtual QList<int> | supportedImplementationVersions () const |
The QOrganizerManagerEngineFactory class provides the interface for plugins that implement QOrganizerManagerEngine functionality.
This class provides a simple interface for the creation of manager engine instances. Each factory has a specific id associated with it, which forms the managerName parameter when creating QOrganizerManager objects.
More information on writing a organizeritems engine plugin is available in the Qt Organizer Manager Engines documentation.
See also QOrganizerManager and QOrganizerManagerEngine.
A default, empty destructor.
This function is used internally when deserializing an id. It allows the deserialization functions to correctly allocate an engine-specific id for an item, filled with the serialized data engineIdString.
Since the format of the id might be different depending on the construction parameters parameters, these parameters are passed to the factory implementation of this function.
Engine implementers must implement this function, but should not need to call it.
This function was introduced in Qt Mobility 1.1.
This function is used internally when deserializing an id. It allows the deserialization functions to correctly allocate an engine-specific id for a collection, filled with the serialized data engineIdString.
Since the format of the id might be different depending on the construction parameters parameters, these parameters are passed to the factory implementation of this function.
Engine implementers must implement this function, but should not need to call it.
This function was introduced in Qt Mobility 1.1.
This function is called by the QOrganizerManager implementation to create an instance of the engine provided by this factory.
The parameters supplied can be ignored or interpreted as desired.
If a supplied parameter results in an unfulfillable request, or some other error occurs, this function may return a null pointer, and the client developer will get an invalid QOrganizerManager in return. Any error should be stored in the supplied error reference.
This function was introduced in Qt Mobility 1.1.
This function should return a unique string that identifies the engines provided by this factory.
Typically this would be of the form "com.nokia.qt.organizeritems.engines.memory", with the appropriate domain and engine name substituted.
This function was introduced in Qt Mobility 1.1.
This function should return a list of versions of the engine which this factory can instantiate.
This function was introduced in Qt Mobility 1.1.
© 2008-2011 Nokia Corporation and/or its subsidiaries. Nokia, Qt and their respective logos are trademarks of Nokia Corporation in Finland and/or other countries worldwide.
All other trademarks are property of their respective owners. Privacy Policy
Licensees holding valid Qt Commercial licenses may use this document in accordance with the Qt Commercial License Agreement provided with the Software or, alternatively, in accordance with the terms contained in a written agreement between you and Nokia.
Alternatively, this document may be used under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation.