Teacher. I want to reproduce something like I did here.

ongoing issues

Ck out the project here: http://www.sugarlabs.org/ -ctrl + shift in emulator is a real pain -pippy doesn't load examples -no indication in the UI that a save has taken place -copy and paste out of the emulator does not work -can't name chats -no indication in the UI to let me know if someone is sharing/editing with me (?) -announcements to neighborhood to indicate 'let's play/work together' -control over edits to shared docs?

don't work at all

scratch
cartoonbuilder

links

irc://irc.freenode.net#sugar

p8 is short for private chat

http://wiki.sugarlabs.org/go/Special:RecentChanges

http://wiki.laptop.org/go/1_hour_smoke_test

One tester's attempt at installing SoaS

testing machines

Compaq TC4400
4 gigs Ram
- dual boot XP and edubuntu 9.04
  - unnecessary after 17aug jhbuild DISPLAY=:0 ./sugar-jhbuild run

jhbuild

One tester's jhbuild experience 23Aug9 ./sugar-jhbuild update ; ./sugar-jhbuild depscheck ;./sugar-jhbuild build ; ./sugar-jhbuild run

dgd> this worked right out of the box: ./sugar-jhbuild update ; ./sugar-jhbuild depscheck ;./sugar-jhbuild run <silbe> dgd: great!

<dgd> silbe, yes! very good news!

<silbe> dgd: i still wonder why the DISPLAY=:0 changed anything for you

<silbe> dgd: but it's more important that it works now - reproducible, i hope :)

<dgd> silbe is this a better command ./sugar-jhbuild update ; ./sugar-jhbuild depscheck ;./sugar-jhbuild build ; ./sugar-jhbuild run

<silbe> dgd: i wouldn't recommend updating before every run

<dgd> silbe, may I ask why?

<dgd> and does the build command help/hurt?

<silbe> dgd: and if you chain depscheck in there, you can't read it's output (it won't do anything by itself, it just tells you to install packages)

<dgd> not before every run of course! I understand that... but once a day if I want the latest/greatest/most broken ;)

<silbe> dgd: it's hard to reproduce bugs if you update in the middle of your session :)

videos

Goal: Test Sugar on a stick. Get screencasts working so that I can begin to document Sugar for proof that it'll work (for me). Ultimately want to be installing Sugar or something like it in schools and NPOs.

part I This is after messing with the BIOS for a few minutes. Unfortunately, most teachers wouldn't know how to do this. A WUBI like dual boot option at the beginning of startup might be a better option for the Aunt Tillies of the world.

part II This is where I figure out that F1 is the network view key. Thanks to the friendly people at the IRC!

part III F1 to see network view.

part IV This is probably where everything starts to go wrong with the install. Habit of downloading updates I believe is what broke Sugar on a Stick. I was trying to get RecordMyDesktop to work... which I did... but there doesn't appear to be any way to play .flv or .ogv or .swf in the default install package of Sugar on a stick. Not acceptable IMHO for a piece of software that's supposed to work in a school.

part V Sugar on a stick has seized. You can see what happens when stuff almost stops working entirely. Browser, IRC, writer are all dead. Far right hand corner to try and shutdown... no joy there.

part VI Trying to copy error messages from the terminal. No joy. The activities have seized.