1. By Team Yogurt

2. Creative Writing Multiplayer Collaboration Fun!

3. Players take turns writing the lines of a story But they can only see the previously written line A shared image gives the story focus.

4. Two modes of play One laptop Many children One story Many laptops Many children Many stories

5. Player 1 Return to menu Story is done Players Join Players Write Lines Options are chosen

6. The finished story is uploaded to a central server, where the stories can then be read by the teacher. HTML File and Story Image

7. Model View Controller Image Library Player Story PyGTK uses encapsulates

8. Players broadcast Pipe-delimited Strings to everyone. “LNE|Cory Bart|A line from the story” 3-letter identifying code Name of sender Message Data Other players read the message, and decide if they should act on it or ignore it.

9. A folder in the OLPCA Activity directory stores all the PNG files. 0.png 1.png 2.png 3.png 4.png …./imgLib/ Current Caveats: All *.png files can only have numbers in their names The files need to be the same across instances of the Activity. “0.png” “1.png” “2.png” “3.png” “4.png” … A list in ImageLibrary

10. Original version had a play mode using the Mesh. The Mesh option was dropped after testing revealed poor network performance.

11. Our instructions were originally a wall of text. Had to do our best to “whittle it down” to something that kids could understand.

12. Images were chosen by guys, and were unintentionally geared towards boys. Goes to show that guys never know what girls want.

13. Use a host-specified image in the story Spruce up User Interfaces to make them more appealing. Have a “Display All Previous Lines” mode (versus only one line) More fancy HTML output. Leftover BugsFeature Ideas Potentially asynchronized Image Libraries across multiple instances Users with multiple names lead to GUI glitches. Instructions are questionable Multiple Children/Laptops/Stories mode is hard to set up.