Send UI Plug-in APIChanges in Send UI Plug-in API documentation
PurposeNew sending services can be added into Send menu using this API. This is a partially alternate and simpler method compared to using Messaging Integration API. API descriptionThis Framework API offers a simple way to create ECOM based sending services that are available in the Send menu. Use casesThe use case explains how to define a new sending service. In practice, this includes implementing the pure virtual functions and setting up the ECOM resource file. API class structureSending service needs to implement the
Related APIs
Using Send UI Plug-in APIDefining a sending serviceThe class derived from
Defining resourcesSending services requires a UID. Its resources are saved into file NNNNNNNNN.rss. In the below example the file name is 12345678.rss.
Implementing pure virtual methodsA sending service provider is given
All the following methods are defined pure virtual by
PopulateServicesListL The most important method to get your service visible is
Sending service provider should fill the parameter array with all provided
sending services. The sending service information is included in the
ServiceProviderId Method
CreateAndSendMessageL Next, implement
The call
Destructor Finally, implement a destructor.
Related APIs
Related APIs
Error handlingIt is guaranteed that Send UI inquires at least once via
Do not raise
Related APIs
Memory overheadThis interface has minimal memory overhead. Memory overhead depends on the deriving class. Security considerationsSend UI first starts a sending service in the process of the hosting application
(with host application capabilities). If this fails due to system security
restriction of loading ECOM plug-ins, then the same service is started from
a process with less capabilities (
Related APIs
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. License: EPL
|