Journal: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 13: | Line 13: | ||
==Description & Goals== |
==Description & Goals== |
||
{{Users}} |
|||
The Journal activity is an automated diary of everything a child does with his or her laptop. The Journal can be used by children to organize work or revisit a past project, and by teachers and parents to assess a child's progress. |
|||
⚫ | |||
===Summary=== |
|||
⚫ | |||
{{Developers}} |
|||
The Journal is also a key component of the [[Bitfrost]] security specification. The document [[Journal and Overlays]] discusses one possible implementation strategy for the Journal and auto-population while using (particularly legacy) activities. |
The Journal is also a key component of the [[Bitfrost]] security specification. The document [[Journal and Overlays]] discusses one possible implementation strategy for the Journal and auto-population while using (particularly legacy) activities. |
||
See the [[OLPC_Human_Interface_Guidelines/The_Laptop_Experience/The_Journal| Human Interface Guidelines]] for theoretical discussion. |
|||
===Goals=== |
|||
===Collaboration=== |
|||
=Visual Design= |
=Visual Design= |
Revision as of 18:57, 9 December 2007
This page is monitored by the OLPC team.
For the general public
see more templates or propose new |
Description & Goals
For the general public
The Journal activity is an automated diary of everything a child does with his or her laptop. The Journal can be used by children to organize work or revisit a past project, and by teachers and parents to assess a child's progress.
The Journal activity provides an intuitive interface for viewing projects and files saved by the XO user.
For Developers
The Journal is also a key component of the Bitfrost security specification. The document Journal and Overlays discusses one possible implementation strategy for the Journal and auto-population while using (particularly legacy) activities.
See the Human Interface Guidelines for theoretical discussion.
Visual Design
Media
Document | Description |
---|---|
No media | --- |
Screenshots
Development
Source
RPMs
- none available
Resources
Functional Test
Basic
- The Journal comes up running when the XO is powered on.
- The basic functional test is to create an Abiword document and Paint file, exit, then ensure that they show up in the journal.
- From the journal interface you should be able to resume these activities right where you left off.
Secondary
- Journals are properly archived and can be restored from the school server.
- Sharing?