Changes
Jump to navigation
Jump to search
Line 48:
Line 48: − + Line 87:
Line 87: + + + + + + + + + +
Development Team/Almanac/Activity Bundles (view source)
Revision as of 13:12, 18 December 2006
, 13:12, 18 December 2006no edit summary
service_name = com.redhat.Sugar.BrowserActivity
service_name = com.redhat.Sugar.BrowserActivity
icon = activity-web
icon = activity-web
exec = sugar-activity-factory com.redhat.Sugar.BrowserActivity BrowserActivity.BrowserActivity
exec = sugar-activity-factory BrowserActivity.BrowserActivity
show_launcher = yes
show_launcher = yes
Keys in the languague-specific '.linfo' files selectively override keys from the 'activity.info' file; if a key is not present in the '.linfo' file the value from the 'activity.info' file is used instead.
Keys in the languague-specific '.linfo' files selectively override keys from the 'activity.info' file; if a key is not present in the '.linfo' file the value from the 'activity.info' file is used instead.
= Other Technologies Comparison =
Activity bundles are similar to OS X bundles or Java JAR files; a simple mechanism to encapsulate everything you need in a single directory that can be moved around independently.
It differs from autopackage, it's not a package management system. There's no central database, no scripts get run on install/uninstall. There also is no special file format.
As compared to klik, it's not intended to replicate a local Unix directory structure inside the package; the activity can still link to system
provided binaries and such. There's also no server-side component other than compressing the archive and sending it over the network.There is also no dependency checking since activities are required to be self-contained.