Difference between revisions of "How to make screencasts on Sugar"

From Sugar Labs
Jump to: navigation, search
m
(steps)
Line 17: Line 17:
  
 
7)Type:  
 
7)Type:  
  <code>yum install recordmydesktop</code>  
+
  <code>yum install recordmydesktop</code> (Don't use this one unless you are comfortable with the command line.)
 
or  
 
or  
 
  <code>yum install gtk-recordmydesktop</code>
 
  <code>yum install gtk-recordmydesktop</code>
 
  
 
==Why make screencasts?==
 
==Why make screencasts?==

Revision as of 20:22, 3 August 2009

steps

1) Get Sugar installed and internet connection working

2) Go to terminal (can be found in list of activities)

3) Go to root by typing

su

4)Type:

yum update

5)Wait a bit to pull down changes. Keep in mind the size of your drive. Mine is 4Gigs so plenty of room...

6)Accept changes is up to you.

7)Type:

yum install recordmydesktop (Don't use this one unless you are comfortable with the command line.)

or

yum install gtk-recordmydesktop

Why make screencasts?

Video, when done properly, can explain a lot more than text. And video can overcome some of the language barriers by SHOWING people what to do and their expected outcomes.

Possible errors you may encounter

[root@localhost liveuser]# gtk-recordMyDesktop /usr/lib/python2.6/site-packages/recordMyDesktop/rmdMonitor.py:10: DeprecationWarning: The popen2 module is deprecated. Use the subprocess module. import popen2 /usr/lib/python2.6/site-packages/recordMyDesktop/rmdSimple.py:223: DeprecationWarning: os.popen3 is deprecated. Use the subprocess module. (stdin,stdout,stderr)=os.popen3(xwininfo_com,'t') The program 'gtk-recordMyDesktop' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 3927 error_code 11 request_code 53 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

  • No known workaround for this yet.