SpeakSign

From OLPC
Revision as of 09:05, 29 September 2009 by Danceswithcars (talk | contribs) (Add a rant about duplicate styles of activity definition, on laptop.org vs SugarLabs, dinasour stuff too...)
Jump to: navigation, search

Some Issues with this Page and Development Issues

This page grew out of two different methods, one create an activity (find link), the other wiki 'edit with form', and will hopefully eventually merge into one style, but when have some working code up on a server.

Some issues with development, as wiki.laptop.org and SugarLabs documentation is not exactly synchronized, nor up to date. GITorious on sugarlabs for example, you can create an account, but there is no help/ documentation on creating SSH keys to actually put something up there...

And stuff has changed a bit from the original wiki.laptop.org methods of creating an activity.

So in an environment that I'm currently using, Fedora 11 64 bit (yeah, had a little money at one time, but not any more, and it's not booting from USB, nor virtualization chip support, so don't get me started on needing new, working hardware...)

Have the Sugar desktop install from yum install sugar* type stuff, or yumex, but then sugar-jhbuild environment (the latest is not working, somewhere on metacity?) and another older version that jhbuild is working, all pointing to the same environment ~/Activity files, with different sugar versions, and the little example programs I got doing SOMETHING is wx graphics not pygtk, nor pygame so Sugar isn't liking it, SO FAR...

Hack, swear, hack, hack, learn, mumble about python development tools, (I'm old (45+) but started with Knuth before 16, started with ALGOL, SAIL, MLAB, DEC-10, Fortran, PASCAL, then Symbolics Lisp/ Common Lisp, CLOS, much later Java for undergrad thesis project, etc)

And the 1 Gig is full, annoyed by all the Journal is Full, delete stuff messages, but I rant...

Back to our normally scheduled programming...


|- valign="top" bgcolor="#F9F9Fc" class="olpc-activity-info" | width="5%" id="icon" name="icon" bgcolor="white" | icon for {{{simplename}}} | width="65%" name="description, authors, static metadata"| unknown : Finger spell American Sign Language for teaching and learning minimal sign language. edit
 
Maintainers: [User:DancesWithCars]  ·  License: GPL, Creative Commons Share and Share Alike with Attribution  ·  Mime types: ??
| width="30%" name="versions, builds, locales"| Download v.0.1 ·
Tested in: (trac)
Translate: ? ·    

Background

Type something and see it finger spelled in American Sign Language.

During the ClassActs book sprint at Gallaudet, decided to create a manual American Sign Language application alternative to Speak, which deaf people would not hear. This could be used to teach some basic finger spelling, such as your name in ASL.

Contributors

DancesWithCars

Roadmap and future features

Dialects, beyond just ASL, as Sign Language is rather locale dependent.

Rate of Signing: variable for learning, speed up later, like rate adjust on classic auditory Speak.

All sorts of other ideas as they appear.

Activity Summary

Icon: Sugar icon::http://www.tux.org/~gkwms/SpeakSign/SpeakSign.svg
Genre: Activity genre::Language Learning
Activity group: ,|x|Activity group::x}}
Short description: Short description::Finger spell American Sign Language for teaching and learning minimal sign language.
Description: [[Description::My first Sugar & Python programming attempt for the XO.

Currently, more bugs than features, but learning...]]

Maintainers: ,|x|Contact person::x}}
Repository URL: Source code::http://www.tux.org/~gkwms/SpeakSign/
Available languages: ,|x|Available languages::x}}
Available languages (codes): ,|x|Language code::x}}
Pootle URL:
Related projects: Related projects,|x|Related projects::x}}
Contributors: ,|x|Team member::x}}
URL from which to download the latest .xo bundle Activity bundle::http://www.tux.org/~gkwms/SpeakSign/SpeakSign.xo
Last tested version number: Activity version::0.1
The releases with which this version of the activity has been tested. ,|x|Software release::x}}
Development status: Devel status::1. Planning
Ready for testing (development has progressed to the point where testers should try it out): ,|x|Ready for testing::x}}
smoke tested :
test plan available :
test plan executed :
developer response to testing :