Line 5: |
Line 5: |
| This page is targeted at beginners, more experienced users may find reading [[Activities/Turtle Art/Patching]] , [[Activity_Team/Resources]] and [[Activity_Team/Creating_a_New_Activity]] useful. | | This page is targeted at beginners, more experienced users may find reading [[Activities/Turtle Art/Patching]] , [[Activity_Team/Resources]] and [[Activity_Team/Creating_a_New_Activity]] useful. |
| | | |
− | The activities are stored at ''/home/olpc/Activities'' and you can use the browser as a "file manager" to browse the file system using the URL prefix ''file://'' | + | The activities are stored at ''/home/olpc/Activities'' and you can use Browse as a "file manager" to browse the file system using the URL prefix ''file://'' |
| | | |
| For example, type ''file:///home/olpc/Activities/TurtleArt.activity'' into the browser address bar to see the Python files that make up the TurtleArt activity. Click on one of the *.py files to inspect the code. | | For example, type ''file:///home/olpc/Activities/TurtleArt.activity'' into the browser address bar to see the Python files that make up the TurtleArt activity. Click on one of the *.py files to inspect the code. |
| | | |
− | You can view the code but not edit it in the browser. | + | You can view the code but not edit it in Browse. |
| | | |
| There are the following options for file editing | | There are the following options for file editing |
Line 15: |
Line 15: |
| In terminal type | | In terminal type |
| vi ''filename'' | | vi ''filename'' |
− | The syntax of vi is obscure for the unfamiliar | + | The syntax of vi is obscure for the unfamiliar. |
| | | |
| ===The GNOME desktop on dual desktop laptops=== | | ===The GNOME desktop on dual desktop laptops=== |
− | Double click on "Computer" to navigate, double clicking a file will open it in GEdit | + | Double click on "Computer" to navigate, double clicking a file will open it in GEdit. |
| | | |
− | ===Using GEdit from terminal=== | + | ===Using GEdit from Terminal=== |
| GEdit will be found on dual desktop systems, notably the [http://people.sugarlabs.org/bernie/olpc/f11-xo1-0.88/ Paraguay builds]. | | GEdit will be found on dual desktop systems, notably the [http://people.sugarlabs.org/bernie/olpc/f11-xo1-0.88/ Paraguay builds]. |
− | If used as above, it does not allow editing in directories above /home/olpc | + | If used as above, it does not allow editing in directories above /home/olpc. |
| To access the higher level directories run GEdit from Terminal in either Sugar or GNOME and use the su or sudo commands. (If editing OLPC system level files, it is wise to have backed up important work and know how to [http://wiki.laptop.org/go/Clean-install_procedure reflash the operating system]). | | To access the higher level directories run GEdit from Terminal in either Sugar or GNOME and use the su or sudo commands. (If editing OLPC system level files, it is wise to have backed up important work and know how to [http://wiki.laptop.org/go/Clean-install_procedure reflash the operating system]). |
| su | | su |