Documentation Team/Glossary: Difference between revisions
~ instead of /home/olpc is more general |
|||
| Line 60: | Line 60: | ||
;content:books, music, movies, photographs, drawings, etc. that are created on the laptop or downloaded to the laptop | ;content:books, music, movies, photographs, drawings, etc. that are created on the laptop or downloaded to the laptop | ||
;content library:content that is created on the laptop is accessed through the Journal; preloaded content is stored in a library and is accessed through the Browse activity | ;content library:content that is created on the laptop is accessed through the Journal; preloaded content is stored in a library and is accessed through the Browse activity | ||
;bundle/activity bundle:a “zip” file with a .xo suffix used to package and distribute activities; bundles are installed in | ;bundle/activity bundle:a “zip” file with a .xo suffix used to package and distribute activities; bundles are installed in ~/Activities | ||
;content bundle/collection: a “zip” file with a .xol suffix used to package and distribute content; bundles are installed in | ;content bundle/collection: a “zip” file with a .xol suffix used to package and distribute content; bundles are installed in ~/Library | ||
;sugar coat or sugar coating: A process for making Linux apps run under the Sugar desktop (i.e. making them to run in the Sugar interface, without the collaboration and other Sugar integration programmed into them). | ;sugar coat or sugar coating: A process for making Linux apps run under the Sugar desktop (i.e. making them to run in the Sugar interface, without the collaboration and other Sugar integration programmed into them). | ||
;sugarizing: A process of re-engineering Linux applications to run as native Sugar activities which take advantage of Sugar's collaboration capabilities and interface. | ;sugarizing: A process of re-engineering Linux applications to run as native Sugar activities which take advantage of Sugar's collaboration capabilities and interface. | ||