76
edits
Changes
Development Team/Almanac/Activity Bundles (view source)
Revision as of 16:52, 5 September 2008
, 16:52, 5 September 2008no edit summary
contents.sig
contents.sig
mimetypes.xml
mimetypes.xml
permissions.info (optional; '''not a stable API''')
icons/
icons/
Make sure to add your shell script and any native libraries to the MANIFEST before you package your bundle. You can also accomplish the same thing by throwing all your libraries in the root folder of the bundle, like the [[Map_(activity)|Map activity]] does, but if you have more than a few libraries to include it can get quite cluttered.
Make sure to add your shell script and any native libraries to the MANIFEST before you package your bundle. You can also accomplish the same thing by throwing all your libraries in the root folder of the bundle, like the [[Map_(activity)|Map activity]] does, but if you have more than a few libraries to include it can get quite cluttered.
== activity/permissions.info ==
'''Note: the API described in this section is NOT STABLE and will probably be change in future releases; perhaps drastically.'''
Bitfrost describes a variety of security-related settings which activity authors can specify about their activity. At the option of the activity author, these settings can be described in a file called 'permissions.info' which can be placed alongside 'activity.info' in the 'activity' directory of the bundle.
As of rainbow-0.7.21, writing the single line
constant-uid
into the permissions.info file will result in your activity being launched with the same uid each time it is run. (This is option is mainly used by activities based on the xulrunner codebase.)
== Other Technologies Comparison ==
== Other Technologies Comparison ==