×
Namespaces

Variants
Actions
(Difference between revisions)

Archived:Capability requirements for Flash Lite Viewer API

From Nokia Developer Wiki
Jump to: navigation, search
Forum Nokia KB (Talk | contribs)
extkbeditor1 (Talk | contribs)
m
Line 2: Line 2:
 
__NOEDITSECTION__
 
__NOEDITSECTION__
 
{{KBTS}}
 
{{KBTS}}
{|border="2" cellspacing="0" cellpadding="4" width="100%"
+
{{KnowledgeBase
|
+
|id=TSS000512
====Subject:====
+
|platform=S60 3rd Edition
|colspan = "2"|Capability requirements for Flash Lite Viewer API
+
|devices=
|TSS000512
+
|category=Symbian C<nowiki>++</nowiki>
 +
|subcategory=
 +
|creationdate=November 30, 2006
 +
|keywords=
 +
}}
  
|-
+
== Overview ==
|rowspan = "2"|
+
Capability requirements for Flash Lite Viewer API
====&nbsp;====
+
|Platform(s):
+
|colspan = "2"|Device(s), SW version(s):
+
  
|-
+
== Description ==
|S60 3rd Edition
+
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<nowiki>’</nowiki>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<nowiki>’</nowiki>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.
|colspan = "2"|&nbsp;
+
  
|-
 
|
 
====Category:====
 
|colspan = "3"|Symbian C<nowiki>++</nowiki>
 
 
|-
 
|
 
====Subcategory:====
 
|colspan = "3"|-
 
 
|-
 
|
 
====Description:====
 
|colspan = "3"|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<nowiki>’</nowiki>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<nowiki>’</nowiki>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.
 
 
|-
 
|
 
====Creation date:====
 
|colspan = "3"|November 30, 2006
 
 
|-
 
|
 
====Last modified:====
 
|colspan = "3"|-
 
 
|-
 
 
[[Category:Technical Solution]][[Category:Symbian C++]][[Category:Flash Lite]][[Category:S60 3rd Edition, Feature Pack 1]]
 
[[Category:Technical Solution]][[Category:Symbian C++]][[Category:Flash Lite]][[Category:S60 3rd Edition, Feature Pack 1]]

Revision as of 00:20, 4 November 2008


Template:KBTS

Article Metadata
Compatibility
Platform(s): S60 3rd Edition
S60 3rd Edition FP1
Article
Created: (30 Nov 2006)
Last edited: extkbeditor1 (04 Nov 2008)

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.

74 page views in the last 30 days.