Demonstration build: Difference between revisions
Jump to navigation
Jump to search
Alexlevenson (talk | contribs) (New page: ==Demo Laptop== There are many capabilities of the XO that aren't easy to demonstrate on a standard build. 0) dual-boot with a Fedora/Gnome or Edubuntu setup (via SD card) 0a) with any s...) |
Alexlevenson (talk | contribs) |
||
| Line 1: | Line 1: | ||
==Demo Laptop== |
==Demo Laptop== |
||
There are many capabilities of the XO that aren't easy to demonstrate on a standard build. |
There are many capabilities of the XO that aren't easy to demonstrate on a standard build. The idea for this project is to set up an XO that can show off some of the features described below. |
||
#dual-boot with a Fedora/Gnome or Edubuntu setup (via SD card) |
|||
#*with any simple hacks to speed up launch -- perhaps a dual-boot OpenWRT? |
|||
#full-screen full-motion video (ogg) |
|||
#video from m.youtube / an online source |
|||
#the best that can be done with mpeg & rm |
|||
#multichannel audio |
|||
#streaming audio from an online source |
|||
#bookreaders |
|||
| ⚫ | |||
#*pdf (evince) |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
#*Speak |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
#drawing w/ stylus |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
Eben -- you worked on showing full-screen video for the MOMA exhibit, yes? What setup did you use? |
|||
| ⚫ | |||
| ⚫ | |||
Things I /want/ to show off but don't know how to |
|||
#a plot of battery strength/usage over time, however crude, like what the Prius offers for gas conservation |
|||
#a compressed view for the Journal (or a way to link directly to a compressed view) |
|||
There are also a number of activities whose demos should be focused down to a couple of minutes, whose components could all be set up in advance; I'm thinking about how to effectively walk through them, without waiting to long for each one to load and set up, but without having more than one in memory at a given time. Is there some way to launch an activity while simultaneously demanding/reserving a block of memory, potentially killing other processes when starting up to improve the repeatability of demo length? |
There are also a number of activities whose demos should be focused down to a couple of minutes, whose components could all be set up in advance; I'm thinking about how to effectively walk through them, without waiting to long for each one to load and set up, but without having more than one in memory at a given time. Is there some way to launch an activity while simultaneously demanding/reserving a block of memory, potentially killing other processes when starting up to improve the repeatability of demo length? |
||
What else should we be sure to show off? What other systems might we want to have available to dual-boot? |
|||
Revision as of 19:44, 4 June 2008
Demo Laptop
There are many capabilities of the XO that aren't easy to demonstrate on a standard build. The idea for this project is to set up an XO that can show off some of the features described below.
- dual-boot with a Fedora/Gnome or Edubuntu setup (via SD card)
- with any simple hacks to speed up launch -- perhaps a dual-boot OpenWRT?
- full-screen full-motion video (ogg)
- video from m.youtube / an online source
- the best that can be done with mpeg & rm
- multichannel audio
- streaming audio from an online source
- bookreaders
- pdf (evince)
- js (flipbook, ICDL, jresig)
- smooth Flash animation (Gnash)
- the best that can be done with Adobe Flash
- text-to-speech
- Speak
- videochat or at least audiochat
- drawing w/ stylus
- phun / elements / crayon physics
- Full-fledged firefox
- Opera
- New Sugar UI and config screen
- Faster load time (now in joyride)
- a plot of battery strength/usage over time, however crude, like what the Prius offers for gas conservation
- a compressed view for the Journal (or a way to link directly to a compressed view)
There are also a number of activities whose demos should be focused down to a couple of minutes, whose components could all be set up in advance; I'm thinking about how to effectively walk through them, without waiting to long for each one to load and set up, but without having more than one in memory at a given time. Is there some way to launch an activity while simultaneously demanding/reserving a block of memory, potentially killing other processes when starting up to improve the repeatability of demo length?