You Are Here:

Community: Wiki

This page was last modified on 8 December 2008, at 13:43.

KIS001196 - Restrictions in developing customised Active Idle plug-ins

From Forum Nokia Wiki



ID KIS001196 Creation date December 9, 2008
Platform S60 3rd Edition
S60 5th Edition
Devices All (S60)
Category Symbian C++ Subcategory Architecture/Design


Keywords (APIs, classes, methods, functions): n/a

Overview

The Active Idle framework uses an ECom plug-in-based solution to manage functionality and content visible on the device idle screen. However, there are heavy restrictions on developing such plug-ins.

Description

While the Active Idle framework supports loading custom plug-ins, there are restrictions that prevent 3rd parties from creating them; the APIs required for Active Idle plug-in development are not publicly available. In addition, the (ECom) plug-in DLL must always reside in ROM in order to be loaded by the framework. Therefore, a custom firmware package needs to be always created with Active Idle configuration updated with the new plug-in.


Solution

No solution available for the above reasons (without creating a custom build of the device firmware).

Note that 3rd party applications do have the possibility of managing application shortcuts displayed in the Active Idle, with the ScShortcuts Engine Wrapper API. This API is available for S60 3rd Edition and S60 3rd Edition, Feature Pack 1 platforms, and included in the SDK API Plug-in packages.

See also

KIS000920 - Shortcuts Engine API not available in S60 3rd Edition, Feature Pack 2

Related Wiki Articles

No related wiki articles found

Rate This

 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZidentifierQSxhttpE3aE2fE2fwikiE2eforumE2enokiaE2ecomE2findeE78E2ephpE2fKIJ000103E5fE2dE5fS60E5fprofileE5fsettingsE5fandE5fplayingE5fsoundsE5finE5fMIE44letsX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZKnowledgeBaseContentQ qdcZtypeQUqfntypeZKnownIssueQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqfntypeZWikiContentQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZKnowledgeBaseContentQ qfnZtypeQUqfntypeZKnownIssueQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qfnZtypeQUqfntypeZWikiContentQ qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZKnowledgeBaseContentQ qrdfZtypeQUqfntypeZKnownIssueQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqfntypeZWikiContentQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ