Demonstration build: Difference between revisions
Jump to navigation
Jump to search
Alexlevenson (talk | contribs) |
Alexlevenson (talk | contribs) |
||
Line 9: | Line 9: | ||
#*m.youtube / an online source |
#*m.youtube / an online source |
||
#*the best that can be done with mpeg & rm |
#*the best that can be done with mpeg & rm |
||
#**has been done using a completely separate build which was stripped of absolutely |
#**has been done using a completely separate build which was stripped of absolutely everything but the ability to play video (No "OS"/GUI at all), and uses proprietary codecs |
||
everything but the ability to play video (No "OS"/GUI at all), and uses proprietary codecs |
|||
#Audio |
#Audio |
||
#*multichannel audio |
#*multichannel audio |
Revision as of 19:49, 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
- m.youtube / an online source
- the best that can be done with mpeg & rm
- has been done using a completely separate build which was stripped of absolutely everything but the ability to play video (No "OS"/GUI at all), and uses proprietary codecs
- Audio
- multichannel audio
- streaming audio from an online source
- Bookreaders
- pdf (evince)
- js (flipbook, ICDL, jresig)
- Flash
- smooth Flash animation with 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
- Browsers
- 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?