132
edits
Changes
Jump to navigation
Jump to search
Line 84:
Line 84: − +
Development Team/Almanac/Activity Bundles (view source)
Revision as of 10:01, 7 July 2008
, 10:01, 7 July 2008→.info File Format: Moved Patrick's bundle_id naming restriction discussion from Low-Level API here
bundle_id = com.redhat.Sugar.BrowserActivity
bundle_id = com.redhat.Sugar.BrowserActivity
: This is the activity bundle identifier. It is required. It is also used as the activity's default service type when the activity is shared on the network. To determine this type, the distince parts (separated by the '.' character) are reversed, any '.' is replaced by a '_' character, and the type is prefixed by a '_' character. So in this example, the default service type would be "_BrowserActivity_Sugar_redhat_com".
: This is the activity bundle identifier. It is required. The name should conform to the [http://dbus.freedesktop.org/doc/dbus-specification.html#message-protocol-names D-Bus spec] - in particular, hyphens are not allowed (although this wasn't enforced in earlier builds, see [http://dev.laptop.org/ticket/6226 Trac 6226]). In the Python bindings, it is also used as the activity's default service type when the activity is shared on the network. To determine this type, the distince parts (separated by the '.' character) are reversed, any '.' is replaced by a '_' character, and the type is prefixed by a '_' character. So in this example, the default service type would be "_BrowserActivity_Sugar_redhat_com".
icon = activity-web
icon = activity-web