Framework Developer Tutorials
Framework or Application designers of the plug-in framework understand interface definition design and platform security implications. They define interface definitions, extend interfaces of the framework and also provide the required resolution and upgrading mechanism.
- Writing Interface Definitions
- Filtering Implementations by Vendor ID
The Plug-in framework clients can be restricted to use plug-ins supplied by a particular company. This enables to enhance security and improve functionality of the framework.
- Providing a Custom Resolver
The plug-in framework has a default resolver that selects an appropriate implementation to suit the client requests. If the algorithm used by the custom resolver is inappropriate, an interface definition can provide its own custom resolver.
- Preventing Plug-in Overriding
The plug-in framework supports two methods to prevent a RAM based plug-in from overriding a ROM based plug-in. The first method is to use the ROM-only resolver and the second method is to explicitly prevent a ROM-based implementation from being overridden by a RAM-based implementation.
- Upgrading ROM Plug-ins
Phone manufacturers sometimes require to provide installable upgrades to the existing ROM plug-ins delivered with the phone. The requirement arises to fix defects or add a new functionality.
- Using Extended Interfaces
Framework developers define and publish extension interfaces to the existing interfaces used in the framework. Once an interface extension is published by the framework developer, plug-in developers implement the extension if required.
Copyright ©2010 Nokia Corporation and/or its subsidiary(-ies).
All rights
reserved. Unless otherwise stated, these materials are provided under the terms of the Eclipse Public License
v1.0.