Difference between revisions of "Find help"

Ideas for How to present Sugar.
Tech Coordinator Guide and other training materials prepared by Teaching Matters(R) for OLPC in NYC
Turtle Art tutorials by Tony Forster and Mokurai.
Tutorials.iso - An off-line collection of .pdf copies of some of the tutorials on this wiki.

Tutorials

Screenshots
Introduction to the Sugar Interface
Connecting to the Internet
Chatting with the Chat Activity
Chatting with the IRC Activity
Copy with drag & drop
Send a file to a friend
Backup & restore Journal

Capturas de pantalla
Introducción a la interfaz de Azúcar
Conexión a Internet
Charlando con la Actividad Chat
Charlando con la Actividad IRC
Copia con un simple arrastrar y soltar

Installation
Install SoaS in VirtualBox
Install SoaS in VMware Player
Import a VirtualBox Appliance
Importar un aparato de VirtualBox
Install with `liveinst`
Instalar con `liveinst`
Install & use liveusb-creator
Netinstall Fedora with Sugar Desktop
Burn a CD.iso on a Mac

Videos

Annotated screenshot guides to Sugar

Click on the following links to go to wiki pages with annotated screenshots covering these topics.

Introduction to the Sugar Interface

Chatting with the Chat Activity

Communicate with others on Sugar.
A good example of collaboration on a shared Activity.

Chatting with the IRC Activity

Communicate with developers and others with IRC.

Send file to friend

Note: Requires a special version of Sugar.
A nice way to sent a file to a friend.

Backup & restore Journal

Backup & restore to an attached hard drive or USB device.
Also works to save & retrieve individual files from the Sugar Journal that have been copied to a USB device.

Captura de pantalla comentadas en español

Haga clic en los siguientes enlaces para ir a las páginas wiki con capturas de pantalla comentadas que cubren estos temas.

Introducción a la interfaz de Azúcar

Charlando con la Actividad Chat

Comunicarse con los demás de Azúcar.
Un buen ejemplo de la colaboración en una actividad compartida.

Charlando con la Actividad IRC

Comunicarse con los desarrolladores y otras personas con IRC.

Copia con un simple arrastrar y soltar

Fotos de exportación
Importación / install <activity> archivo. XO

Installation

Installing and using liveusb-creator in Sugar

Make a bootable, persistent, Live USB device from a Fedora .iso file in SoaS.

* Windows: Create a SoaS v7 Live USB

Liveusb-creator in Microsoft Windows

* Windows: Run SoaS with VMware Player

Install VMware Player in Microsoft Windows and run SoaS.

Fedora^®
Fedora and the Infinity design logo are trademarks of Red Hat, Inc.

Install SoaS in VirtualBox using Fedora 18 Beta Anaconda

Install_using Anaconda f18 RC1 DVDx86_64

newUI Anaconda

New version of the installer for Fedora 18

Testing Dextrose in VirtualBox

VirtualBox simulation of XO-1 software

Build_A_Fedora_Custom_Live_CD/DVD_Remix

Build a Live CD/DVD .iso file with a customized kickstart file and livecd-tools in Fedora

How to Import a VirtualBox Appliance

with links to Virtual Appliances to download.

Cómo importar un aparato de VirtualBox

traducciones a través de http://translate.google.com/#auto%7Ces%7C Por favor, haga las correcciones por errores en la wiki.

Install from a booted Live CD/USB with `liveinst`

The Fedora-16-Live-SoaS.iso file is a 443 MB download.
Installs to a 4 GB USB stick or VirtualBox 4 GB hard drive. (The procedure is adaptable for installation to a regular hard drive.)

Fedora 25 Install of Soas from a booted Live CD/USB with `liveinst` :NEW

Instalar desde una calzada Live CD/USB con `liveinst`

El archivo Fedora-16-en vivo-SoaS.iso es una descarga de 443 MB.

Anotado de fotografías en pantalla de una instalación

Se instala a 4 GB de memoria USB o VirtualBox 4 GB de disco duro. (El procedimiento es adaptable para la instalación de un disco duro normal.)

How to make a SoaS.img file for repeated installs

Netinstall of Fedora with the Sugar Desktop Environment

Note: Requires a high speed Internet connection!
Install to a hard disk or USB device.

Install sugar-desktop in Fedora with anaconda-19.6

Install of sugar 0.98.2 in VirtualBox

Testing of Anaconda anaconda-19.6-boot.iso

Burning a CD from an .iso file on a Mac

Videos

More videos

We have tried hard to make it easy for children to discover what they can do with Sugar software without being told. But that isn't always possible. So we have a list of things that teachers should know about, and be able to demonstrate. If you find some feature of the software incomprehensible, please add it to the list, and we will see what we can do for you and everybody else who runs into the same problem. Sometimes the answer is a click of the mouse away, but not always. We are, after all, introducing children to all of human knowledge. They will inevitably need help with much of it. It took all of our ancestors many years to get this far, so it is alright if children spend a few years hitting the highlights, and getting help to do it.

OLPC Project Help and Information

For general help and information about the OLPC Project, please see these links at the The OLPC Wiki:

Official OLPC FAQ, Support FAQ, for questions about the XO laptop and its use, Support, for more support mechanisms, :Category:OLPC FAQ, and Ask OLPC a Question (in roughly that order).

Request new features

Please use our Request New Features page.

If you can't find your answer, please request one or supply one! below:

Help Requests:

Click on an [edit] link next to a topic paragraph below to enter your request or an answer (you will see more instructions on the edit form). But first, if possible, login or register on the wiki, leave an email address (secured by your login password), and then you can choose to 'Watch' any page on the wiki (such as this one) by clicking the 'Watch tab', and you will receive an email if the page changes. Plus, others can respond to you privately by using the 'E-mail this user' link in the sidebar of your user page.

There are also links for new questions on the Category:FAQ pages.

on Usage

First, see the help links above.

on the Wiki

First, see the Wiki Team/Resources page.

on Submitting a bug

Please report problems or bugs on Submit Bugs/Problems page.

on Releases

First, see this page, 0.114/Roadmap.

on Distributions

First, see the Downloads and Supported systems pages.

Live CD in Spanish
Purport: I see as one of the selling points of Sugar that a non-expert user can use computers "off the bat". It has been reported to me that currently the LiveCD requires some tweaking at startup to adjust it to a given locale, which I feel is to ask too much precisely from users that are not skilled.
Goal: a LiveCD version that is localized in Spanish from startup, with no tweaking required, to be distributable among the Spanish-speaking public.
Contact: yamaplos at bolinux.org

on Sugar hardware ports

First, see the Supported systems page.

on Sugar activities

First, see the Activity Team pages.

on Sugar deployments

First, see the Deployment Team pages.

on Sugar Labs

See the Sugar Labs page. Sugar Labs was created to provide a mechanism for supporting the Sugar community of volunteers. These volunteers are engaged in a variety of activities: some are writing software to improve Sugar; some are porting Sugar to new platforms; some are developing new activities that run in Sugar; some are helping to debug Sugar and help with quality assurance; some are writing documentation for Sugar developers and for those who use Sugar in the field; some are developing new scenarios for learning with Sugar; some are using Sugar and reporting upon their experiences to the community; and some are providing help and support.

Since we started Sugar Labs, we have been receiving a number of requests for help: porting Sugar to new distributions; tuning Sugar on a specific hardware platform; developing specific Sugar activity; helping with support in specific deployments, etc. Please use this page both to make requests and respond to requests for help.

@@ Line 1: / Line 1: @@
+<noinclude>{{Translations | [[Sugar help|english]] &#124; [[Sugar help/lang-pt|português]] &#124; [[Sugar help/lang-es|español]] &#124; }}
+{{TOCright}}</noinclude>
+==Finding answers to help==
+For general help on Sugar or about Sugar Labs, please see also
+'''&rarr;''' '''[[Getting Started | Getting started]]'''
+'''&rarr;''' '''[[Sugar Labs/FAQ | Sugar Labs FAQ]]''' - a compilation of the team FAQs
+'''&rarr;''' '''[[:Category:FAQ]]''' - an index to all FAQ pages ('''with links for new questions''')
+'''&rarr;''' '''[[:Category:Help]]''' - pages tagged as 'Help'
+'''&rarr;''' '''[[:Category:HowTo]]''' - pages tagged as 'HowTo'
+'''&rarr;''' '''http://getsatisfaction.com/sugarlabs''' - our community-powered support site
+'''&rarr;''' '''http://launchpad.net/soas''' - our Sugar on a Stick project support site
+'''&rarr;''' '''[[Sugar_Labs/Contacts#Forums|Community Forums]]''' - on-line forums with lots of topics
+===The Sugar Learners' manual===
+{| class="wikitable"
+|-
+|<span class="plainlinks"> [http://flossmanuals.net/Sugar http://wiki.sugarlabs.org/images/4/40/Sugarlabs_mainpage_07.png]</span>
+|available as: <span class="plainlinks">[http://en.flossmanuals.net/Sugar HTML] or [{{FlossmanualPDF}} .pdf] 128 pages, 8.3 MBytes (for saving or printing).</span>
+|}
+===Sugar [[Glossary|glossary]]===
+: There is a [[Glossary|glossary with commonly used acronyms available here]].
+{{:Tutorials}}
+===[[The Undiscoverable]]===
+: We have tried hard to make it easy for children to [[Discovery|discover]] what they can do with Sugar software without being told. But that isn't always possible. So we have a list of things that teachers should know about, and be able to demonstrate. If you find some feature of the software incomprehensible, please add it to the list, and we will see what we can do for you and everybody else who runs into the same problem. Sometimes the answer is a click of the mouse away, but not always. We are, after all, introducing children to all of human knowledge. They will inevitably need help with much of it. It took all of our ancestors many years to get this far, so it is alright if children spend a few years hitting the highlights, and getting help to do it.
+----
+===OLPC Project Help and Information===
+: For general help and information about the OLPC Project, please see these links at the [[olpc:The OLPC Wiki|The OLPC Wiki]]:
+: [[OLPC:Official OLPC FAQ | Official OLPC FAQ]], [[OLPC:Support FAQ|Support FAQ]], for questions about the XO laptop and its use, [[OLPC:Support|Support]], for more support mechanisms, [[OLPC::Category:OLPC FAQ|:Category:OLPC FAQ]], and [[OLPC:Ask OLPC a Question | Ask OLPC a Question]] (in roughly that order).
+----
+===[[Request_New_Features| Request new features]]===
+: Please use our [[Request_New_Features|Request New Features page]].
+: If you can't find your answer, please request one or ''supply one!'' below:
+== Help Requests:==
+:Click on an '''[edit]''' link next to a topic paragraph below to enter your request or an answer (you will see more instructions on the edit form).  '''But first''', if possible, login or register on the wiki, leave an email address (secured by your login password), and then you can choose to 'Watch' any page on the wiki (such as this one) by clicking the 'Watch tab', and you will receive an email if the page changes.  Plus, others can respond to you privately by using the 'E-mail this user' link in the sidebar of your user page.
+:There are also links for new questions on the [[:Category:FAQ]] pages.
+===on Usage ===
+:First, see the help links above.
+* <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem.  LEAVE the leading asterisk in the first column AND a blank line before and after your question.  Use the [Show preview] button, below the edit window, to check the formatting.  Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results.  (You may click the {Cancel} link to back out with no changes.)  Be bold, we will fix up any mistakes or problems that may occur. -->
+===on [[Wiki_Team/Resources | the Wiki]] ===
+:First, see the [[Wiki Team/Resources]] page.
+* <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem.  LEAVE the leading asterisk in the first column AND a blank line before and after your question.  Use the [Show preview] button, below the edit window, to check the formatting.  Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results.  (You may click the {Cancel} link to back out with no changes.)  Be bold, we will fix up any mistakes or problems that may occur. -->
+===on Submitting a bug===
+:Please report problems or bugs on '''[[Submit_Bugs/Problems| Submit Bugs/Problems page]]'''.
+* <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem.  LEAVE the leading asterisk in the first column AND a blank line before and after your question.  Use the [Show preview] button, below the edit window, to check the formatting.  Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results.  (You may click the {Cancel} link to back out with no changes.)  Be bold, we will fix up any mistakes or problems that may occur. -->
+===on Releases===
+:First, see this page, [[{{Upcoming Stable Release}}/Roadmap]].
+* <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem.  LEAVE the leading asterisk in the first column AND a blank line before and after your question.  Use the [Show preview] button, below the edit window, to check the formatting.  Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results.  (You may click the {Cancel} link to back out with no changes.)  Be bold, we will fix up any mistakes or problems that may occur. -->
+===on Distributions===
+:First, see the '''[[Downloads]]''' and '''[[Supported systems]]''' pages.
+* <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem.  LEAVE the leading asterisk in the first column AND a blank line before and after your question.  Use the [Show preview] button, below the edit window, to check the formatting.  Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results.  (You may click the {Cancel} link to back out with no changes.)  Be bold, we will fix up any mistakes or problems that may occur. -->
+* Live CD in Spanish
+*:Purport: I see as one of the selling points of Sugar that a non-expert user can use computers "off the bat".  It has been reported to me that currently the LiveCD requires some tweaking at startup to adjust it to a given locale, which I feel is to ask too much precisely from users that are not skilled.  <br> Goal: a LiveCD version that is localized in Spanish from startup, with no tweaking required, to be distributable among the Spanish-speaking public.
+*::Contact: yamaplos at bolinux.org
+=== on Sugar hardware ports===
+:First, see the '''[[Supported systems]]''' page.
+* <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem.  LEAVE the leading asterisk in the first column AND a blank line before and after your question.  Use the [Show preview] button, below the edit window, to check the formatting.  Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results.  (You may click the {Cancel} link to back out with no changes.)  Be bold, we will fix up any mistakes or problems that may occur. -->
+=== on Sugar activities===
+:First, see the [[Activity Team]] pages.
+* <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem.  LEAVE the leading asterisk in the first column AND a blank line before and after your question.  Use the [Show preview] button, below the edit window, to check the formatting.  Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results.  (You may click the {Cancel} link to back out with no changes.)  Be bold, we will fix up any mistakes or problems that may occur. -->
+=== on Sugar deployments===
+:First, see the [[Deployment Team]] pages.
+* <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem.  LEAVE the leading asterisk in the first column AND a blank line before and after your question.  Use the [Show preview] button, below the edit window, to check the formatting.  Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results.  (You may click the {Cancel} link to back out with no changes.)  Be bold, we will fix up any mistakes or problems that may occur. -->
+=== on Sugar Labs===
+: See the '''[[Sugar Labs]]''' page. Sugar Labs was created to provide a mechanism for supporting the Sugar community of volunteers. These volunteers are engaged in a variety of activities: some are writing software to improve Sugar; some are porting Sugar to new platforms; some are developing new activities that run in Sugar; some are helping to debug Sugar and help with quality assurance; some are writing documentation for Sugar developers and for those who use Sugar in the field; some are developing new scenarios for learning with Sugar; some are using Sugar and reporting upon their experiences to the community; and some are providing help and support.
+:Since we started Sugar Labs, we have been receiving a number of requests for help: porting Sugar to new distributions; tuning Sugar on a specific hardware platform; developing specific Sugar activity; helping with support in specific deployments, etc. Please use this page both to make requests and respond to requests for help.
+* <!--COPY this paragraph block, PASTE it into the blank space just below this paragraph and before any other questions in this section, then replace the copy with your question or problem.  LEAVE the leading asterisk in the first column AND a blank line before and after your question.  Use the [Show preview] button, below the edit window, to check the formatting.  Sign your submission by entering ~~~~ (4 squiggles) after your entry, then click the [Save page] button, when you are happy with the results.  (You may click the {Cancel} link to back out with no changes.)  Be bold, we will fix up any mistakes or problems that may occur. -->
+[[Category:General public]]
+[[Category:Help]]