Sugar Learning Environment, Activity Toolkit, GTK 3.
3f10890319
These are just the doc strings I created as I was spelunking
through to see how Sugar manages launching applications. The
resulting auto-documentation is neither polished or finished,
but it should help people reading the code somewhat.
There are a few minor code cleanups:
* activityhandle (replacing C idiom for initialisation with
a Python one)
* bundle registry (using a parameterised directory name so
that it shows up in the documentation)
* validate_activity_id function, use isinstance( item, (str,unicode))
for the query, rather than two separate checks with isinstance
|
||
|---|---|---|
| bin | ||
| browser | ||
| data | ||
| docs | ||
| m4 | ||
| po | ||
| services | ||
| shell | ||
| sugar | ||
| tests | ||
| .gitignore | ||
| autogen.sh | ||
| build-snapshot.sh | ||
| configure.ac | ||
| COPYING | ||
| COPYING.LIB | ||
| Makefile.am | ||
| pylint.sh | ||
| README | ||
| sugar-emulator | ||
Building ======== See: http://wiki.laptop.org/go/Sugar_with_sugar-jhbuild Running multiple instances on the same machine ============================================== You can use the SUGAR_PROFILE command line options. For example: SUGAR_PROFILE=profile-1 sugar SUGAR_PROFILE=profile-2 sugar ... Emulator key bindings ===================== F1 Mesh zoom level F2 Friends zoom level F3 Home zoom level F4 Activity zoom level Alt+f Show the frame Alt+r Rotate the screen Alt+o Toggle overlay visibility Alt+= Open the developer console Alt+0 Open the developer console Alt+q Quit the emulator Ctrl+s Activate sketch mode in chat