Development Team/Almanac/Activity Bundles: Difference between revisions
→.info File Format: Update exec option description |
m →.info File Format: add Activity API link |
||
| Line 73: | Line 73: | ||
exec = myfactory myoptions | exec = myfactory myoptions | ||
: The exec key is used when [[Sugar]] installs the activity. It specifies the executable which [[Sugar]] runs to start the activity's factory service. A factory service spawns instances of the actual activity. The executable name must be a path relative to the bundle's top level directory. Environment variables given on the exec line are expanded, in particular, <tt>$SUGAR_BUNDLE_PATH</tt> expands to the absolute path of the bundle directory. | : The exec key is used when [[Sugar]] installs the activity. It specifies the executable which [[Sugar]] runs to start the activity's factory service. A [[Activity Factory DBus API|factory service]] spawns instances of the actual activity. The executable name must be a path relative to the bundle's top level directory. Environment variables given on the exec line are expanded, in particular, <tt>$SUGAR_BUNDLE_PATH</tt> expands to the absolute path of the bundle directory. | ||
class = browseractivity.BrowserActivity | class = browseractivity.BrowserActivity | ||