Python

Python for S60 on S60 3rd Edition, 28.06.2006 :


Contents:

1. Introduction
2. Overview of PyS60 on S60 3rd Edition
3. Standard development lifecycle in 3rd Edition
3.1 Signing and distribution
3.2 Module level details
4. File locations
5. Capabilities
6. Native extensions
6.1 ABI compatibility
6.2 Porting existing native extensions to PyS60
7. Summary
8. Glossary



This document describes the changes to Python for S60 (hereafter PyS60) needed
in order to support S60 3rd Edition (hereafter also S60 3rdEd). These changes
and advices described are not applicable to PyS60 running on S60 1st or 2nd
Edition and the developers on these platforms are not affected in any way.

The new platform security (hereafter platsec) features in Symbian OS 9.x/EKA2,
and S60 3rdEd onwards require several changes to the whole PyS60 framework.
Without these modifications S60 3rd Edition would not be supported by PyS60. The
implementation alternative selected in order to support PyS60 3rd Edition is
tightly aligned with the common EKA2 platform security framework in order to
minimize the work for a PyS60 developer. At the same time this limits the possible
security threats posed by PyS60.


Overview of PyS60 on S60 3rded :


In 3rdEd devices, platsec is enforced. This means that all the installed SISX
files need to be signed (NB. there might be an option to install unsigned
packages in some devices). Unsigned packages cannot be installed to a device and
neither the old style SIS packages nor the binaries packaged from 2ndEd or 1stEd
are compatible with the 3rdEd.

The software installer (hereafter SWInstall) will check if the application in
the SISX package is signed. For more information about signing, see the Section
"Signing".

A fundamental concept in platsec is 'capability' which is the term used for what
the running process can do in the device - process is the basic insulation
granularity in platsec and capabilities are forced during runtime. A capability
must be held by the executable binary if the process needs to access some
restricted resource.

Since a standalone PyS60 application is no different from a native application
and runs in a separate process it needs to be signed if it uses controlled APIs or
it is distributed via a SISX package.

What a Python standalone application can do will be limited by the capabilities
assigned to the interpreter DLL - these capabilities are listed in Section 5.
"Capabilities". In other words, this is the upper bound for any Python
application which uses the Nokia signed PyS60 distribution. There is of course
the possibility to sign the Python interpreter DLL for special purposes with
larger capabilities if needed but this discussion is left out from this
document.

As the Python application seen from the device main menu, aka script shell, is
also a Python application it needs to be signed. The script shell should not
enable the running of scripts with large capabilities and thus it is not signed
by Nokia with the same capabilities as the interpreter DLL. This should not
cause problems for development - a developer can sign the script shell
application with developer certificate (hereafter devcert). Due to separate
signing needs for the interpreter DLL and the script shell application, there is
need for two separate packages ('X' indicates version number):

* PythonForS60-X_X_X_3rded.SIS - contains the interpreter DLL, all the Nokia
provided native Python extensions and other needed files

* PythonScriptShell-X_X_X_3rded.SIS - contains the script shell application,
does not work without the above package

A developer should keep in mind that the script shell is just a normal
application, similar to the one you wrap with py2sis and subject to the same
security preconditions as described earlier in this document. The interpreter
DLL is the one used by all the standalone Python applications and the entity
that needs to be signed with a large set of capabilities to ensure that
individual Python applications can access the controlled resources as freely as
possible. Notice that the script shell Python application visible in the device
main menu has nothing to do with other standalone Python applications (ie. there
are no logical or conceptual dependencies).




Python for S60 on S60 3rd Edition 1.3.8 RELEASE NOTES, 07.07.2006 :


Product Description:

Python for S60 (hereafter PyS60) is intended for developers looking to create
programs that use the native features and resources of the S60 phones, using the
Python programming language.


About this release:

This release is only meant for S60 3rd Edition devices. For an
overview of how the Symbian platform security enhancements affect
PyS60, please see 'PyS60_3rdEd_README.txt'.

Note on versioning: The versioning scheme in PyS60 releases is such
that releases with an even minor version (1.0.x, 1.2.x ...) are
"stable" and releases with an odd minor version (1.1.x, 1.3.x ...) are
"development" releases. 1.3.8 is thus a development release, meaning
that it includes functionality that has not been tested as extensively
as the stable releases. This release is provided as a preview to
developers who wish to experiment with Python on S60 3rd Edition
before the final stable release.


Documentation:

The PyS60 Library Reference document has not been updated yet to
include the 3rd edition changes. Consult the 1.3.1 version and these
release notes

... ... ...

3 files:

-pythonscriptshell SIS

-pythonfors60 SIS

-FileRemover SIS

Working with my N80 & N95.

signed

[فقط الاعضاء المسجلين هم من يمكنهم رؤية الروابط. اضغط هنا للتسجيل]

Just Sniper

N-Gage User Name : abojasem

[فقط الاعضاء المسجلين هم من يمكنهم رؤية الروابط. اضغط هنا للتسجيل]

[فقط الاعضاء المسجلين هم من يمكنهم رؤية الروابط. اضغط هنا للتسجيل]

[فقط الاعضاء المسجلين هم من يمكنهم رؤية الروابط. اضغط هنا للتسجيل]