Sugar Labs - User contributions [en]

Design Team/Logo Ideas

2008-09-16T20:22:57Z

81.187.181.168: candy floss

Request New Features

2008-06-28T10:35:13Z

81.187.181.168: /* Please describe new feature requests here */

Sugar Labs/Current Events

2008-06-27T19:29:26Z

81.187.181.168: /* Sugar Digest */

<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
==What's new==

This page is updated each week (usually on Monday morning) with notes from the Sugar Labs community. (The digest is also sent to the community-news at sugarlabs.org list.) If you would like to contribute, please send email to walter at sugarlabs.org by the weekend. An '''archive''' of this digest is available [[Sugar Labs/Current Events/Archive|here]].

=== Sugar Digest ===

1. Latest Sucrose: The new [[Sucrose]] 0.81.3 Development Release is now available. The release has some new features, including: Manual reordering of the Home view icons; a freeform layout of the Home view icons; improved feedback on activity startup; support for custom certificates in Browse; alt+tab activity switching; etc. We are now in feature freeze, so the short-term focus will be on testing, bug triaging and fixes. The community has done a great job in that we achieved practically all the features that we had targeted. Thanks to everyone that made this possible and special kudos to the Sugar release team.

Detailed release notes can be found in the wiki (Please see [[ReleaseTeam/Releases/Sucrose/0.81.3]]); a sugar-jhbuild branch for the release can be found here (http://dev.laptop.org/git?p=sugar-jhbuild;a=shortlog;h=sucrose-0.81.3).

With the release of 0.81.3 we will be in feature freeze ([[ReleaseTeam#Feature_freeze]]): this affects all of the modules included in the release. To request an exception, which will be exceptional, please send mail to sugar at laptop.org, copying release-team at sugarlabs.org; please include the patches you would like to land. For string changes please also copy localization at lists.laptop.org.

2. Making the installation of Activities easier: Dave Farning is working on a web interface to managing activities based upon Mozilla's AMO codebase (addons.mozilla.org). He has successfully used AMO on a local server to install activities on an XO-1 laptop and to install Sugar on a conventional laptop. He has started submitting a series of patches upstream to Mozilla.org with the goal that SugarLabs will be able to use the AMO codebase as maintained by Moxilla. A few areas that require work: (a) Look and feel – applying the sugarlabs stylesheets; (b) Applications – currently, AMO hardcodes application data rather than handled dynamically; (c) Addontypes – AMO can handle several addontypes such as extension, plugins, and and dictionaries, but they are not yet handled dynamically. By modularizing how AMO handles applications and add-on types, we should be able to drop in Sugar application and and addontype code.

The work flow for a developer would be:
* Activity authors register their activity with AMO;
* author uploads latest release into sandbox;
* reviewer verifies new upload works correctly and publishes the upload.

From the user perspective, Activities would then be browseable and downloadable in a manner similar to any Firefox plugin, with very fast, secure, and scalable updates.

Dave is looking for help (the code is being put in https://www.develer.com/gitweb/pub?p=users/dfarning/w.s.o.git;a=summary).

In parallel, there has also been a discussion on the Sugar list regarding development of an activity for updating Sugar and Sugar Activities.

3. courses.sugarlabs.org: David Van Assche is setting up a Moodle installation at http://courses.sugarlabs.org to complement activities.sugarlabs.org. It will house stable versions of activities, together with lesson plans, relevant reading materials, and related activities. The OLE Nepal team, with help from Bernie Innocenti, who is in Kathmandu for the summer, will be fleshing out the site. Please contribute.

4. Usability testing: Carlos Mauro Cárdenas Fernández has begun a pilot usability test of Sugar on the Intel Classmate PC (Please see http://wiki.laptop.org/go/Projects/TestUsabilityOLPC for some details of his plans and initial findings).

=== Community jams and meetups ===

5. Porto Alegre, Brazil: Juliano Bittencourt from Laboratório de Estudos Cognitivos reports that a GameJam was held at FISL 9.0, the largest Latin America free software conference. A short video made during the event is available on YouTube (Please see http://www.youtube.com/watch?v=oWKBdeZUtq0). A team from the Argentian PyGame group was the winner: a game called Falabranaman.

===Tech Talk===

6. Infrastructure: Marco Pesenti Gritti has started a page on the wiki about infrastructure ([[Infrastructure Plan]]) and is seeking your feedback.

7. Journal: Tomeu Vizoso reports that a new version of the Journal activity has been released, with many translation updates and some visual fixes (Download it from http://dev.laptop.org/pub/sugar/sources/journal-activity/journal-activity-92.tar.bz2). New features include:
* Add indications for empty Journal and empty search results (Eben Eliason)
* Translation update for Italian (Carlo Falciola)
* Fix appearance of "no preview" (Eben Eliason)
* Translation update for Khmer (Rit Lim)
* Translation update for Haitian Creole (Diksyone Ayisyen)
* Translation update for German (Markus Schlager)
* Translation update for Marathi (Rupali Sarode)
* Translation update for French (Samy Boutayeb)
* Adapt object chooser to new designs. Some refactoring was needed (Tomeu)
* Adapt UI to right-to-left scripts (Khaled Hosny)

8. Datastore: Tomeu also reports that a new version of the datastore has been released (http://dev.laptop.org/pub/sugar/sources/sugar-datastore/sugar-datastore-0.8.2.tar.bz2). New features include a metadata copy outside the index.

9. USB key boot: The CD-image of the recent XO-LiveCD (Version 080607) contains a script to copy the data on a USB key and make it bootable:
* mount the CD (or ISO-image) on a computer running Linux;
* open a console (shell) and go into the directory tools/;
* insert a usb memory device and
* run the command ./make_usbstick.sh -d <block-device> -m <cd-mount-point>
Hint: ./make_usbstick.sh -h provides more detailed documentation. Please contact Wolfgang Rohrmoser if you have any questions (WolfgangRohrmoser at web.de).

10. Char 41: Morgan Collett has released Chat 41 (Please see http://dev.laptop.org/pub/sugar/sources/chat-activity/Chat-41.tar.bz2 and http://dev.laptop.org/~morgan/bundles/Chat-41.xo). New features include:
* Updated translations: mr, de, ht, km, es, it;
* #6036: Add separator after old chat history;
* #6298: Implement 1-1 private chat with non Sugar Jabber clients.
Morgan also updated the Presence Service with the changes required for non-Sugar Jabber clients to chat with OLPC XO-1 laptops.

11. Fedora 9: Daniel Drake reports that the following packages may make the Fedora-9 build experience a little more bearable:
* a NetworkManager that can actually connect to networks (http://dev.laptop.org/~dsd/NetworkManager-0.6.5-0.11.svn3246.olpc3.i386.rpm);
* fixed keyboard – arrow keys, Alt-Gr and other functionality (http://dev.laptop.org/~dsd/xorg-x11-server-Xorg-1.4.99.901-29.20080415.fc9.i386.rpm)

12. Alt-Tab: Benjamin Berg submitted a number of patches to update Alt-Tab behavior for switching between activities.

13. Measure activity: Arjun Sarwal has been working upon 'Sound' and 'Sensor' contexts within Measure and also, adding a textbox at the bottom that mentions details about the signal/sound input (Please view a screenshot at http://crank.laptop.org/~arjs/sound_sensors.png). Arjun has also been working on a new re-organized wiki page for Measure (Please see http://wiki.laptop.org/go/Measure/New_temp). Suggestions and contributions are very welcome.

14. Home view: Tomeu Visozo has implemented a Home view user interface that allows the user to "drag and drop" activities to desired locations on the screen (freeform) rather than restricting them to the circle. Other activities move nicely out of the way if you try to drop one on top of another.

15. Patches: Marco Pesenti Gritti reviewed patches and more patches. He also packaged xulrunner 1.9 final and adapted the Browse activity to it. Finally he coordinated the Sugar 0.81.3 release and made big progresses on a Fedora 9 based Sugar liveCD. (Note that xulrunner 1.9 final is the version used in Firefox 3, which provides much better memory use than previous versions.)

16. Sugar Almanac: Faisal Anwar of Media Modifications has made progress on an online "Sugar Almanac" of best practices and working code snippets (Please see http://wiki.laptop.org/go/Sugar.activity.activity).

17. Etoys: Bert Freudenberg reports a new etoys release (Please see http://dev.laptop.org/pub/sugar/sources/etoys/etoys-3.0.2029.tar.gz and http://dev.laptop.org/pub/sugar/sources/etoys-activity/etoys-activity-83.tar.gz ; the bundled versions cab be found at http://etoys.laptop.org/rpms/etoys-3.0.2007-1.noarch.rpm and http://etoys.laptop.org/rpms/Etoys-83.xo). Improvements include: Pango fixes (tested with Nepalese), new DBus bindings, updated QuickGuides, a few more strings made translatable.

18. Statistics: ohloh also has some statistics on the Sugar software:
* http://www.ohloh.net/projects/9605/analyses/latest
* http://www.ohloh.net/projects/11601/analyses/latest
* http://www.ohloh.net/projects/sugar-presence-service/analyses/latest
* http://www.ohloh.net/projects/11526/analyses/latest
* http://www.ohloh.net/projects/11636/analyses/latest

=== Sugar Labs ===

19. Self-organizing map (SOM): Gary Martin has generated another SOM from the past week of discussion on the IAEP mailing list (Please see [[:Image:2008-June-14-20-som.jpg]]). The list was relatively quite this week, considering all of the progress, so the map is not very informative – the data being sparse.

==Sugar in the news==
{|
|-
|align=right valign=top|18 June 2008||'''PC World''' – [http://www.pcworld.com/businesscenter/article/147265/olpc_spinoff_developing_ui_for_intels_classmate_pc.html OLPC Spin-off Developing UI for Intel's Classmate PC]
|-
|align=right valign=top|17 June 2008||'''Datamation''' – [http://itmanagement.earthweb.com/osrc/article.php/12068_3753376_1 If Business Succeeds with GNU/Linux, Why Not OLPC?]
|-
|align=right valign=top|11 June 2008||'''LinuxInsider''' – [http://www.linuxinsider.com/story/Sugar-Labs-Walter-Bender-on-the-Sweetness-of-Collaborative-Learning-63354.html The Sweetness of Collaborative Learning]
|-
|align=right valign=top|06 June 2008||'''Bill Kerr''' – [http://billkerr2.blogspot.com/2008/06/untangling-free-sugar-and.html untangling Free, Sugar, and Constructionism]
|-
|align=right valign=top|06 June 2008||'''Open Education''' – [http://www.openeducation.net/2008/06/03/walter-bender-discusses-sugar-labs-foundation/ Walter Bender Discusses Sugar Labs Foundation]
|-
|align=right valign=top|06 June 2008||'''BusinessWeek''' – [http://prod-blogs.businessweek.com/globalbiz/blog/globespotting/archives/2008/06/olpc_the_educat.html OLPC: The Educational Philosophy Controversy]
|-
|align=right valign=top|05 June 2008||'''Code Culture''' – [http://radian.org/notebook/distraction-machine The Distraction Machine]
|-
|align=right valign=top|05 June 2008||'''BusinessWeek''' – [http://www.businessweek.com/globalbiz/blog/globespotting/archives/2008/06/olpc_the_open-s.html OLPC: The Open-Source Controversy]
|-
|align=right valign=top|27 May 2008||'''The New York Times''' – [http://bits.blogs.nytimes.com/2008/05/27/why-walter-bender-left-one-laptop-per-child-edited-hold-for-wed-am/ Why Walter Bender Left One Laptop Per Child]
|-
|align=right valign=top|26 May 2008||'''Ars Technica''' – [http://arstechnica.com/news.ars/post/20080526-former-olpc-software-president-wants-to-expand-sugars-reach.html OLPC software maker splits from X0 hardware, goes solo]
|-
|align=right valign=top|22 May 2008||'''BetaNews''' – [http://www.betanews.com/article/Linux_startup_Sugar_Labs_in_informal_talks_with_four_laptop_makers/1211467857 Linux start-up Sugar Labs in informal talks with four laptop makers]
|-
|align=right valign=top|16 May 2008||'''OSTATIC''' – [http://ostatic.com/162220-blog/olpcs-open-source-sugar-platform-aims-for-new-hardware OLPC's Open Source Sugar Platform Aims for New Hardware]
|-
|align=right valign=top|16 May 2008||'''PCWorld''' – [http://www.pcworld.com/businesscenter/article/146002/bender_forms_group_to_promote_olpcs_sugar_ui.html Bender Forms Group to Promote OLPC's Sugar UI]
|-
|align=right valign=top|16 May 2008||'''MHT''' – [http://masshightech.bizjournals.com/masshightech/stories/2008/05/12/daily35.html Bender jumps from OLPC, founds Sugar Labs]
|-
|align=right valign=top|16 May 2008||'''News.com''' – [http://www.news.com/8301-10784_3-9946242-7.html Sugar Labs will make OLPC interface available for Eee PC, others]
|-
|align=right valign=top|16 May 2008||'''Feeding the Peguins''' – [http://morgancollett.wordpress.com/2008/05/16/the-future-of-sugar/ The future of Sugar]
|-
|align=right valign=top|16 May 2008||'''Sugar list''' – [http://lists.laptop.org/pipermail/sugar/2008-May/005800.html A few thoughts on SugarLabs]
|-
|align=right valign=top|16 May 2008||'''xconomy''' – [http://www.xconomy.com/2008/05/16/bender-creates-sugar-labs-new-foundation-to-adapt-olpcs-laptop-interface-for-other-machines/ Bender Creates Sugar Labs—New Foundation to Adapt OLPC’s Laptop Interface for Other Machines]
|-
|align=right valign=top|16 May 2008||'''BBC''' – [http://news.bbc.co.uk/2/hi/technology/7405346.stm '$100 laptop' platform moves on]
|-
|align=right valign=top|15 May 2008||'''OLPC wiki''' – [http://wiki.laptop.org/go/AnnounceFAQ Dual-boot XO] Claim: OLPC will not work to port Sugar to Windows.
|-
|align=right valign=top|16 May 2008||'''Softpedia''' – [http://news.softpedia.com/news/Bender-Launches-Sugar-Labs-for-Better-Development-of-OLPC-039-s-Sugar-UI-85881.shtml Bender Launches Sugar Labs for Better Development of OLPC's Sugar UI]
|}

==Press releases==
{|
|-
| align="right" valign="top" |  15 May 2008
| [[Sugar Labs/Announcing Sugar Labs]]
|}

[[Category:General public]]

Human Interface Guidelines/The Laptop Experience/The Journal

2007-02-08T01:06:13Z

81.187.181.168: /* Filtering */ fixed typos. Changed flagged to tagged

<div style="background-color: #FFF; margin-left:auto; margin-right: auto; width: 95%;">
{{hig-subnav-intra|p_page=View Source|c_section=The Laptop Experience|c_page=The Journal|n_page=Global Search}}

===The Journal===

====The Notion of "Keeping"====
The traditional "open" and "save" model commonly used for files will fade into abstraction on the laptops, and with it the customary floppy disk icon, as not only will the laptops not have floppy drives, but most likely the children will never see one of these largely obsolete devices. Instead, a much more general notion of what it means to want to keep things prevails. Generally speaking, we keep things that we want to hold on to, and the rest just fades with time. Appropriately, the Journal's primary function as a time based view of the activities a child has done and the objects she's kept reinforces this idea.

Most of us recognize the "save early, save often" mantra; most of us have failed to live it and incurred the consequences. The laptops aim to eliminate constant concern for this type of technicality, making automatic and incremental backups and allowing the children to focus on the activity itself. These incremental backups will occur at regular time intervals, and activity events such as changes in scope, new participants, among others can trigger them as well. In order to cater to the needs of many types of editing environments, activities can also specify "keep-hints" which prompt the system to keep a copy. For instance, a drawing activity may trigger a keep-hint before executing an "erase" operation immediately preceded by a "select all". Of course, a child herself may choose to invoke a keep-hint by selecting the "keep in journal" button, but adequate adoption of this new notion of keeping from activities should virtually eliminate need for this.

Based on the Object model associated with files, each kept Object is, technically speaking, a separate instance of the activity which created it. This eliminates the need to "open" a file from within an activity, replacing the act of opening with the act of resuming a previous activity instance. Of course, a child will have the option to resume a drawing with a different set of brushes, or resume an essay with a different pen, providing "open with" style functionality, but no substitute for an "open" command will exist within an activity's interface.

====Deprecating Hierarchy====

=====Temporal Organization=====
Along with the idea of implicit keeping, the laptops will drastically minimize the hierarchical filesystem as a means for organization, replacing it with a temporally organized list of activities and events, furthering the Journal metaphor. This drastically simplifies the auto-keeping behavior, since it eliminates the need to specify a location in which a newly started activity should be kept; naturally, the newly started activity will appear as the most recent entry in the journal.

Temporal organization functions naturally in the absence of explicit or hierarchical methods, since humankind's intrinsic relationship to time gives them, at the very least, a relative notion of "how long ago" something happened. By moving back through the Journal, a child can simply locate the period in time within which she knows she made something, and then employ additional use of searching, filtering, and sorting to pinpoint exactly what she's looking for.

=====Falloff=====

Due to the laptops' limitations in storage capacity, the potential exists for the Journal to contain so many entries that no more may be written. However, the frequency of such occurrences is limited by temporal falloff, which tidies up the Journal contents and keeps space available for new entries. One might think of this as an intelligent combination of garbage collection and disk defragmentation.

The driving principle here is that of temporal granularity, derived directly from our very capacity for human memory. Our minds, generally speaking, maintain a high level of granularity with respect to very recent events, but only a low granularity for events from several years ago. Moreover, this granularity tends to follow a logarithmic curve, where the past few minutes remain quite clear, the past few hours more blurry, and by last month quite vague. When we look years into the past, only specifically memorable events stand out in our minds.

On the laptops the policies are a bit more strict, but the principle remains the same. With a finite amount of memory, some means of managing what's remembered, or kept, and what's forgotten, or erased must exist. An intelligent algorithm will assist children in identifying "forgotten" entries. Taking into account how old an entry is, how many times she's viewed it, how recently she's worked on it, how many hours she's worked on it, how many people she's worked on it with, its tags, and even more forms of automatically generated metadata, the Journal can suggest to her those entries which it feels can be erased. She will then have the opportunity to review those items prior to their erasure, if she wishes, and can keep any she still feels attached to.

In a time where gigabytes have become cheap, many of us still manage to fill our hard drives. Excepting the cases of multimedia collections of audio or video files, much of that space is consumed by files we either don't remember we ever made, or will never open again. On the laptops, where space is precious, so too will be the objects and entries that remain in the journal years down the road. The temporary, the experimental, the duplicate, and the unwanted files will naturally fall off the bottom, maintaining a browsable history of those that remain important to the children.

====Journal Entries====

=====Implicit=====

Implicit journal entries will be the most common. These appear as the result of many kinds of a child's interactions with her machine, but most commonly when engaging in an activity. Other implicit entries might appear when she takes a photo, or receives a note from a friend, or downloads a file from the Web. In all of these cases, the journal entry itself has a basic format which conveys important information about the event which created it. Most importantly, the associated Object - the photo, the message, the drawing, the story - becomes embedded within the entry. It also includes key metadata, such as its name, when it was made, and who collaborated on it.

The journal entry also provides some means to interact with it. For instance, each entry has a description field where a child can tag it with meaningful related words which will make searching for it in the future a breeze. This field will automatically receive any tags that the activity itself associates with the entry. In addition to this tag field, several buttons will allow direct manipulation of the Object, making it possible to resume the activity, place the Object on the clipboard, send it to a friend, print it, or erase it, among others.

=====Note=====

In addition to implicit ones, children have the opportunity to create several special kinds of entries on their own. The first of these, the Note, has the simplest form. Taking a cue from a traditional journal, a Note entry simply provides a large text entry field. This freeform entry allows the children to write down short descriptions of their day to day experiences, just as one would within a real journal. Providing this layer of personalized entries further emphasizes the idea that the Journal really does provide more than a filesystem, as an actual record of events and interactions of the children with the laptop and with their peers.

In practice, children may also use this feature as a means of jotting down a note to themselves - a reminder. In these instances, a simple control within the entry will turn the note into a "to-do" note. As a to-do entry, it will have a checkbox indicating its completion status. By filtering the Journal to show only these entries, it doubles as a basic to-do list, providing another useful tool for learning organizational skills.

=====Clipping=====

Clippings serve a slightly different purpose in the journal. Similar in spirit to notes, a child can create a clipping from anywhere, or from within any activity on their laptop. As an extension of the copy to clipboard idea, clippings copy a selection - some text from a chat session with a friend, an image from a web page, etc. - directly to the journal for safekeeping. This provides a quick and easy way to keep a quick record of anything that you might want to keep around for future reference: a phone number, a link, a password, etc.

=====Event=====

Taking the temporal aspect of the Journal one step further, Events act like "future" journal entries. By specifying a name for the event, a brief description, and a time, these Journal entries serve as a basic planning system. A control within the entry also enables an audible alert, so that Events can act as alarms. Events also tie in closely with some implicit actions of the laptops. For instance, a child might want to go on a photo safari with her friend after school. While still in class, she sends him an invitation to join a photo capture activity, but schedules a time of 3:00. He then receives an invitation, as usual, but upon accepting it receives an Event entry in the journal, with a reference to the scheduled activity, instead of immediately entering it. When 3:00 arrives, both children receive notifications that their scheduled event is about to start, and join each other both physically outside and virtually in the referenced capture activity.

====The Power of Metadata====

Despite the flatness of the Journal, finding past entries shouldn't prove difficult thanks to a tagging structure built from the ground up for the laptops. By associating relevant descriptive words with each journal entry, searching for an entry becomes as easy as describing it. These descriptions will manifest in two ways, tagging and metadata. The former provide a straightforward manner for the children to describe and organize their stuff, while the latter provides a more technical means by which activities can associate relevant data and tags with all Journal entries they create.

=====Tagging=====

Tagging will become a fundamental process for all types of data and activities on the laptops. Fortunately, children have a natural inclination to describe their world and the things they see and do. This actually aids kids in learning, as they will enjoy describing the drawing they've made, the stories they've written, or the composition they produced, and can learn new vocabulary in doing so. Of course, the kid-like desire to describe things doesn't detract from the usefulness of this tag-based system as they grow older.

As such an integral part of the system, the tagging interface will be exposed in various places. Of course, as mentioned, each journal entry will have a field for tags. Likewise, each open activity instance will have a tag field adjacent to its name field, so that the act of naming a particular activity or Object becomes associated with describing it in their minds. Additionally, activities could offer specific places within the interface for tagging to occur, such as in the description field for a photo the child just took.

=====Metadata=====

Metadata adds an additional level of sophistication to the tagging model. Rather than thinking of this as data about data, consider it a means of tagging tags. Metadata on the laptops will be an extension of the basic tagging model where the tag itself consists of a key:value pair. Or, you could simply consider a tag to be a metadata pair with a null key. Whichever way you look at it, this categorization of tags has powerful implications when it comes to organizing and categorizing data.

The Journal itself assigns a variety of useful metadata tags to entries as they appear. These include the time of the entry, it's sharing scope, who participated in the activity, it size, and more. The Journal will also keep track of other useful metadata, such as the number of times a child views a particular entry, the number of revisions an entry has gone through, etc. Likewise, activities will deal primarily with metadata rather than simple tags. This allows activities to define specific parameters, or keys, that make sense for the Objects they produce, and then assign values to those dynamically. In a music composition activity, for instance, potential keys might be beats per minute, the key the composition is written in, the length of the track, and the composer, among others. See the sorting section to fully understand the usefulness of this metadata within the Journal.

Of course, since tags and metadata both follow a very basic format, children can assign their own metadata associations with Journal entries once they have enough experience simply by typing key:value pairs into the description field.

====Powerful Search, Filter & Sort====

=====Searching=====

The search field provides the most direct means of locating a particular Journal entry, returning instant results as the search is typed, and offering auto-completion for popular tags. In order to find anything on their laptop, a child need merely describe it, since the tags she's associated with it already appear within its description field. Her searches also apply to the metadata associated with the entry by either the Journal or the activity that created it, making it even easier to find things.

For simplicity, the search field will employ OR logic to all terms entered, which ensures the least amount of confusion when used by children who don't yet understand boolean logic. As such, a search for "orange cat" will return a list of everything orange and also every cat. Of course, any entries tagged with both orange and with cat will match more strongly, and will automatically filter to the top of the results. However, in keeping with a primary goal of the laptops, this won't eliminate the possibility for more complex boolean searches. Full support for AND, OR, NOT, and parenthetical grouping of terms will be built into the search engine, providing advanced functionality for those who desire to enter more complex queries.

Since the laptops will find themselves in the hands of many children, additional modifications to the search algorithm will assist them as they grow. The youngest children who receive them will still be learning how to spell, and those that can may still require some time to learn typing skills. For these reasons, a fuzzy match algorithm will assist the children, returning some results even when the corresponding tags don't match what they typed exactly. This algorithm is adaptive, and so as they become more comfortable with their language and with using the technology, the extent of the fuzziness and therefore the number of fuzzy results returned will lessen, preventing false matches from aggravating more advanced users. Several other kinds of fuzziness could also be applied, though such possibilities are only speculation at this point. For instance, fuzzy matches based on thesaurus entries could turn up items tagged with "funny" even when the child searches for "humorous". Likewise, translation fuzziness could return an entry tagged with "cat", even though the child searched for "gato." These advanced fuzziness algorithms could prove invaluable in a laptop community that has been built with sharing and collaboration in mind.

=====Filtering=====

Support for basic filtering also exists within the journal. The search and filter functionality appear together in the toolbar, since searching could also be interpreted as filtering by tags. Additionally, their appearance together allows an easy method for the children to visually construct their query in a sentence-like format, with relevant parts of their query displayed as icons — just as those within the entries themselves — for visual reinforcement.

Several fundamental filters exist. First and foremost, there is an advanced date filter, which can only be expected in a Journal organized temporally by default. This control will present a timeline to the child, with visual indication over the length of the timeline of the number of entries present in the Journal from any given point in time. By expanding and contracting the selected area she can select anything from a single day to all time, and by sliding the selection through time, she can filter out all entries that don't lie within the specified range. Bother basic filters include the activity that the entry represent, and the activity participants.

Other available filters allow children to locate specific kinds of entries. For instance, a child may want to view all entries that have been tagged by the Journal for possible removal when memory becomes low. They may also want to see all their notes, or to-dos, or events. They could also show only starred items, or in progress items, and more. The system will provide adequate flexibility for finding anything in the Journal nearly instantaneously.

=====Sorting.=====

Whereas searching and filtering provide a means of defining what entries get shown in the list of results, sorting determines how those entries are organized. A unique approach to sorting on the laptops makes the metadata associated with entries even more valuable. The sort bar, which the child can expand in order to more precisely control their view of the journal, offers a popup menu from which a number of options such as date, title, activity, size, participants, and others may be chosen. In addition to this fixed list, a dynamic list of options also appears, providing a list of metadata keys that are present in the majority of the entries within the results list, the utility of which will become apparent below.

The true functionality of the system arises from "then by" sorting. When desired, a child can specify up to three levels of sorting hierarchy. This feature shouldn't be overlooked, since it serves as an extraordinarily powerful means of viewing and organizing data hierarchically, even when no hard hierarchy exists. In fact, when used to its full advantage this approach can be more useful than a hard hierarchy, since the order of the hierarchy can be adjusted dynamically to suit the child's needs at the time. And, in conjunction with the intelligently compiled list of metadata keys on which to sort, children can not only find what they're looking for, but can browse through their journal in any way that suits them. Consider, for instance, that a child filters her journal so that all of her music appears in the results. Since nearly every song Object in her Journal has metadata keys for artist, album, track, and year, she could sort by these keys to arrange her music collection for browsing. Sorting by artist, then album, then track she can obtain a traditional view of her music. In order to view a discography for each artist, on the other hand, she could sort by artist, then by album, then by track. Or, to see a timeline of her music, she could sort by year, then by artist.

This powerful sorting method isn't necessarily limited solely to a bunch of songs, or pictures, or other specific type of data. Since many forms of metadata will apply across Object types, the possibilities are nearly limitless.

====Implicit Versioning System====

As mentioned before, the laptops automatically save, or "keep", Objects in the Journal at regular intervals. This eliminates the need for the children to constantly worry about saving, and reduces the chances that an unexpected circumstance will cause data loss. These individual keep events are incremental, meaning that the changes within the file are kept in a nondestructive manner. Therefore, the Journal not only stores Objects as children create them, but also keeps track of the revision history for each one. This allows the Journal to function as a versioned filesystem.

The space limitations on the laptop cause some concern with the mention of revision history. However, the differences between revisions will often be small. Additionally, Objects with large revision histories provide one easy way for the journal to regain valuable space when memory becomes tight, since it can collapse the history, storing only every few automatic revisions in addition to those explicitly kept by the child.

====Automatic Backup and Restore====

Automatic backups to server...

Full restore (temporal)...

Partial restore(by object)...

Temporary restore...

====The Journal as a Progress Indicator====

Two stages for entries...

{{hig-subnav-intra|p_page=View Source|c_section=The Laptop Experience|c_page=The Journal|n_page=Global Search}}