Archived:Capability requirements for Flash Lite Viewer API
extkbeditor1
(Talk | contribs) m |
hamishwillee
(Talk | contribs) m (moved TSS000512 - Capability requirements for Flash Lite Viewer API to Archived:Capability requirements for Flash Lite Viewer API) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{Archived|timestamp=20120314043953|user=roy.debjit| }} | |
| − | + | [[Category:Symbian C++]][[Category:Flash Lite]][[Category:S60 3rd Edition FP1]] | |
| − | {{ | + | |
| − | {{ | + | {{ArticleMetaData <!-- v1.2 --> |
| − | | | + | |sourcecode= <!-- Link to example source code (e.g. [[Media:The Code Example ZIP.zip]]) --> |
| − | |platform=S60 3rd Edition | + | |installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) --> |
| − | |devices= | + | |devices= <!-- Devices tested against - e.g. ''devices=Nokia 6131 NFC, Nokia C7-00'') --> |
| − | | | + | |sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Nokia Qt SDK 1.1]) --> |
| − | | | + | |platform= S60 3rd Edition |
| − | |creationdate= | + | |devicecompatability= <!-- Compatible devices (e.g.: All* (must have GPS) ) --> |
| − | | | + | |dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 --> |
| + | |signing= <!-- Empty or one of Self-Signed, DevCert, Manufacturer --> | ||
| + | |capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. --> | ||
| + | |keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase --> | ||
| + | |language= <!-- Language category code for non-English topics - e.g. Lang-Chinese --> | ||
| + | |translated-by= <!-- [[User:XXXX]] --> | ||
| + | |translated-from-title= <!-- Title only --> | ||
| + | |translated-from-id= <!-- Id of translated revision --> | ||
| + | |review-by= <!-- After re-review: [[User:username]] --> | ||
| + | |review-timestamp= <!-- After re-review: YYYYMMDD --> | ||
| + | |update-by= <!-- After significant update: [[User:username]]--> | ||
| + | |update-timestamp= <!-- After significant update: YYYYMMDD --> | ||
| + | |creationdate= 20061130 | ||
| + | |author= [[User:Technical writer 1]] | ||
| + | <!-- The following are not in current metadata --> | ||
| + | |subcategory= | ||
| + | |id= TSS000512 | ||
}} | }} | ||
| Line 16: | Line 32: | ||
== Description == | == Description == | ||
| − | According to the S60 3rd Edition FP1 SDK, the new Flash Lite Viewer API requires that the stub application using it has NetworkControl capability. This implies that every standalone Flash application has to be Symbian Signed.<br>The information provided in the API documentation is incorrect, NetworkControl is not an unconditional capability requirement.<br>The purpose of the API is to provide a flexible mechanism for Flash Lite applications to be presented to the user in the phone | + | According to the S60 3rd Edition FP1 SDK, the new Flash Lite Viewer API requires that the stub application using it has NetworkControl capability. This implies that every standalone Flash application has to be Symbian Signed.<br>The information provided in the API documentation is incorrect, NetworkControl is not an unconditional capability requirement.<br>The purpose of the API is to provide a flexible mechanism for Flash Lite applications to be presented to the user in the phone's application list (menu) with a customized icon and with its own platform security context. This is done by creating a basic Symbian OS application skeleton whose document would in fact be an instance of the Flash Light engine rendering a specified Flash animation (that can be for security reason installed in the application's own data cage). With regards to the Platform Security context the application will have its own SecureID, VendorID, and a capability set designed to fit the requirements of the Flash application. That means that if, for example, the only capability-controlled functionality that the Flash application implements is Internet access, then declaring the NetworkServices capability for the stub Symbian OS application would be enough to satisfy the security policies. In this scenario submitting your application for certification is recommended but not mandatory. |
| − | + | ||
| − | + | ||
Latest revision as of 09:24, 14 June 2012
Article Metadata
Compatibility
Article
Overview
Capability requirements for Flash Lite Viewer API
Description
According to the S60 3rd Edition FP1 SDK, the new Flash Lite Viewer API requires that the stub application using it has NetworkControl capability. This implies that every standalone Flash application has to be Symbian Signed.
The information provided in the API documentation is incorrect, NetworkControl is not an unconditional capability requirement.
The purpose of the API is to provide a flexible mechanism for Flash Lite applications to be presented to the user in the phone's application list (menu) with a customized icon and with its own platform security context. This is done by creating a basic Symbian OS application skeleton whose document would in fact be an instance of the Flash Light engine rendering a specified Flash animation (that can be for security reason installed in the application's own data cage). With regards to the Platform Security context the application will have its own SecureID, VendorID, and a capability set designed to fit the requirements of the Flash application. That means that if, for example, the only capability-controlled functionality that the Flash application implements is Internet access, then declaring the NetworkServices capability for the stub Symbian OS application would be enough to satisfy the security policies. In this scenario submitting your application for certification is recommended but not mandatory.
