Changes
Jump to navigation
Jump to search
Line 6:
Line 6: − + + + Line 24:
Line 26: − − Activities should _NOT_ rely on the activity bundle's base directory name (in this case, "Web.activity") being remaining the same. Sugar may rename the activity bundle base directory at any time to prevent bundle conflicts. Line 41:
Line 41: − default_type = _web_olpc._udp
Development Team/Almanac/Activity Bundles (view source)
Revision as of 09:59, 4 September 2006
, 09:59, 4 September 2006Fix up bits about bundle directory names and sugar
= Location =
= Location =
Activities are installed and removed automatically by [[Sugar]], in response to user actions. Sugar places activities in directory of its choice, currently $(prefix)/share/sugar/activities. Activities should not rely on being installed in a specific location, and should use relative paths where paths are necessary (i.e., for shared library linkage, activity resources such as images, sounds, etc). Sugar will automatically generate and remove the .service files necessary to launch the activity through D-Bus service activation when the activity is installed or removed.
Activities are installed and removed automatically by [[Sugar]], in response to user actions. Sugar places activities in directory of its choice. Activities should not rely on being installed in a specific location, and should use relative paths where paths are necessary (i.e., for shared library linkage, activity resources such as images, sounds, etc). They should also not rely on the bundle's base directory name remaining the same. Sugar may rename the activity bundle base directory at any time to prevent bundle conflicts.
Sugar will automatically generate and remove the .service files necessary to launch the activity through D-Bus service activation when the activity is installed or removed.
Activities should also NEVER store local state or preferences in the activity bundle itself. These should always be stored in an activity-specific directory in the user's sugar profile, available through the SUGAR_PROFILE environment variable.
Activities should also NEVER store local state or preferences in the activity bundle itself. These should always be stored in an activity-specific directory in the user's sugar profile, available through the SUGAR_PROFILE environment variable.
The 'localized' directory contains localizations of the activity bundle's name. It must be present.
The 'localized' directory contains localizations of the activity bundle's name. It must be present.
= .info File Format =
= .info File Format =
python_module = BrowserActivity.BrowserActivity
python_module = BrowserActivity.BrowserActivity
exec = super-duper-web-browser
exec = super-duper-web-browser
show_launcher = yes
show_launcher = yes