Line 66: |
Line 66: |
| host_version = 1 | | host_version = 1 |
| bundle_id = com.redhat.Sugar.BrowserActivity | | bundle_id = com.redhat.Sugar.BrowserActivity |
| + | license = GPLv2+ and BSD |
| icon = activity-web | | icon = activity-web |
| exec = sugar-activity browseractivity.BrowserActivity -s | | exec = sugar-activity browseractivity.BrowserActivity -s |
Line 92: |
Line 93: |
| :* If nothing else is available, even org.laptop.wiki.''YourActivityPageTitle'' is probably a reasonable bundle_id, provided that you create the [[YourActivityPageTitle]] page. Remember, bundle_ids should be unique, so you should double check that the [[YourActivityPageTitle]] page doesn't already exist (and then create it) before using this as your bundle_id. | | :* If nothing else is available, even org.laptop.wiki.''YourActivityPageTitle'' is probably a reasonable bundle_id, provided that you create the [[YourActivityPageTitle]] page. Remember, bundle_ids should be unique, so you should double check that the [[YourActivityPageTitle]] page doesn't already exist (and then create it) before using this as your bundle_id. |
| : In the Python bindings, the bundle_id is also used as the activity's default service type when the activity is shared on the network. To determine this type, the distinct 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". | | : In the Python bindings, the bundle_id is also used as the activity's default service type when the activity is shared on the network. To determine this type, the distinct 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". |
| + | |
| + | license = GPLv2+ and BSD |
| + | : This field names the license used for the activity bundle (the binary .xo file). The contents of this field should conform to the same guidelines as the [http://fedoraproject.org/wiki/Packaging/LicensingGuidelines#License:_field <code>License:</code> field] of an RPM package; consult the [http://fedoraproject.org/wiki/Packaging/LicensingGuidelines Fedora Licensing Guidelines] for more information. A 'license' field naming an entry or entries in the "Good Licenses" table at [http://fedoraproject.org/wiki/Licensing Fedora's Licensing list] is required for any activities distributed by OLPC. |
| | | |
| icon = activity-web | | icon = activity-web |
− | : It points to the activity's icon. The icon is looked up in the activity bundle's 'activity' directory (the same directory the activity.info file is in). It cannot contain a path. When searching for the icon in the activity bundle's 'activity' directory, only a file with the icon name and the extension '.svg' will be looked for. | + | : It points to the activity's icon. The icon is looked up in the activity bundle's 'activity' directory (the same directory the activity.info file is in). It cannot contain a path. When searching for the icon in the activity bundle's 'activity' directory, only a file with the icon name and the extension '.svg' will be looked for. This property is required unless 'show_launcher' is 'no' (see below). |
| | | |
| exec = sugar-activity webactivity.WebActivity | | exec = sugar-activity webactivity.WebActivity |