The design goals can be found in http://wiki.sugarlabs.org/go/Human_Interface_Guidelines/The_Laptop_Experience/The_Journal
The Keep option preserves the current activity and data in the journal as a separate object. When an activity is quit, another preservation event occurs. I can see a use for Keep in all activities that create journal entries. I can't see a use for Keep in an activity that does not create a journal entry. When Write is closed, the current document is "automatically saved" as you put it, and in this way Write is indentical to the other activities the create journal entries. If you'd like to entertain a design discussion with Sugar Labs about this, then you can certainly engage them ... however any major changes would not appear until the next Sugar version, and we are not currently tracking the latest Sugar version on the OLPC XO-1.5 builds. Remember also that a deployment may choose to remove or change some features of Sugar ... and you aren't testing those changes. It is important that the software that the deployments begin with is tested, after that they can do as they need. -- James Cameron http://quozl.linux.org.au/ _______________________________________________ Testing mailing list [email protected] http://lists.laptop.org/listinfo/testing
