AI Plug-in Management APIChanges in AI Plug-in Management API documentation
PurposeThe purpose of the AI Plug-in Management API is to provide a collection of functions and definitions for controlling content publisher plug-in life-cycle, i.e. loading and destroying plug-ins, and suspending and resuming publishing. API descriptionAI Plug-in Management API can be categorized as a framework API. It provides interfaces that clients of the API implement as well as the enumerations and constant definitions that are shared between the clients and UI Controllers. The clients of this API are the instances implementing the content publisher plug-ins. The implementations must meet the requirements of ECom architecture as the Idle Framework (Idle FW) loads the instances using ECom. The main interface is a content publisher interface that provides Idle Framework with lifetime control over the content publishers as well as information passing from attached content observers in the form of settings and events. In addition, the AI Plug-in Management API contains a publisher information interface that encapsulates required information of a content publisher. Use casesThe most important use cases of the AI Plug-in Management API are:
API class structureA simplified class diagram of the Plug-in Management API is shown below.
Related APIs
Using the AI Plug-in Management APIContent publisher clients implement the
The following functions are provided:
Calls to the above methods may come in any order and, therefore, no assumptions should be made in content publisher implementation about the order of the plug-in state guiding method calls. Use casesStarting a plug-inA sequence diagram of a content publisher plug-in creation is shown below.
UI Controller first calls Idle FW, which starts an active object for loading
a content publisher(s) asynchronously. A plug-in itself is constructed through
the ECom interface, as depicted in the diagram. Once the plug-in is created,
the Idle FW calls
Related APIs
Deleting a plug-inA sequence diagram of a content publisher plug-in destruction is shown below.
UI Controller first calls Idle FW, which starts an active object for destroying
a content publisher plug-in asynchronously. The Idle FW stops the plug-in
by calling
Related APIs
Error handlingThe API uses standard Symbian error handling practises. However, content publisher developer should pay extra attention to the error handling. If construction of a content publisher fails, the whole widget is interpreted as a faulty widget and it is removed from the screen and also from the Home screen view configuration. Furthermore, if a content publisher crashes, it makes the whole Home screen process to crash. Extensions to the APIAlthough
Related APIs
Related APIs
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. License: EPL
|


