Sugar Instructions/lang-ja

From OLPC
Jump to: navigation, search
  翻訳された Sugar Instructions 原文  
  english | 日本語   +/- 変更  
This is an on-going translation

Different versions of Sugar behave differently!

The Sugar software is evolving rapidly, so there are different instructions, depending which version you have. The OLPC software comes in "builds", which are loaded into the laptop's firmware (or booted from a CD image, USB key, or SD card). This page documents the Sugar version in the current stable build (Build 385). You can find all versions of this documentation in [Category:Sugar].

Installing

If you have an OLPC laptop, Sugar is already installed. Otherwise you can either use an emulated laptop, which will have Sugar built in, or you can install Python on your desktop PC (see also Category:Installing Sugar for specific platform instructions) and run the Sugar application directly on your PC.

If you are running Sugar from Python then you can skip most of the stuff in the next section, up to choosing your user name.

First Boot on an Emulated OLPC Laptop

{{{1}}}

Choosing a name and colors

{{{1}}}

Getting Started with the Sugar Desktop

Home Mode

{{{1}}}

The Frame Is How You Control Sugar

The dark frame appears when you move the mouse pointer to a corner of the screen. The activities are at the bottom of the frame.

The "Frame", a black border around the edge of the screen, is where many of Sugar's controls are. The frame can appear and disappear, making more room on the screen for activities. It is usually visible on the main screen with the ring, since the edges of that screen aren't used for anything else. If it is not visible, move your mouse pointer to a corner of the screen. The Frame will appear, and will stay visible as long as the mouse pointer doesn't leave the frame area for more than about half a second at a time.

You can also make the Frame appear or disapper by pressing the upper rightmost key on the OLPC keyboard (it has a rectangle on it, like a picture frame).

Opening an Activity

{{{1}}}

Switching View Modes

{{{1}}}

Switching Between Activities

{{{1}}}

Closing or Sharing Activities

{{{1}}}

Internet Access

{{{1}}}

Web Browser

{{{1}}}

Terminal, Shell, or Linux Prompt

You can access a shell in two ways... Either hold down Ctrl+Alt+F1 to leave the Sugar screen and return to the text console's login prompt, or open the Developer Console activity within Sugar and select the terminal tab.

If you use Ctrl+Alt+F1 to leave Sugar, you can return to Sugar with Ctrl+Alt+F3.

If you use the terminal in the Developer Console you won't be logged in as "root" but as "olpc". You need to be logged in as "root" to edit some of the setup files, such as "/boot/grub/grub.conf". You can gain root access by typing "su -". The prompt suffix will change to # which denotes that you are root. You will not be able to start any graphical programs as root using this method.

For example, if you want to edit "/boot/grub/grub.conf" with Write in Sugar, hold down Ctrl+Alt+F1 to leave Sugar, and type "root" for the log in. Type "chmod a+rw /boot/grub/grub.conf". Then return to Sugar by holding down Ctrl+Alt+F3. Now you can open and save that file in Write. However, for system control files, using "vi" in a terminal window is a much better choice than Write.

Some basic shell commands you can use at the prompt are:

  • ls -al (get a list of the files)
  • cd dirname (change to directory dirname)
  • cat filename (show the contents of filename)


Friends View Mode

{{{1}}}

Shortcut Keys

{{{1}}}

Shutting Down the System

{{Translated text| To shut down the whole system, simply push the power button on the bezel; it's below the lower right corner of the screen. This currently only works when the screen is showing graphics (as it is now). The system should leap to action immediately, and turn itself off within half a minute or so. If this doesn't happen, you can also force a power-off by pressing and holding the power button for many seconds.

Sugar Activities

This list provides more information about the activities available or under development.

Under the Hood

See Understanding sugar code.

Detailed description of the Sugar Interface

For more info on the Sugar interface, have a look at the Human User Interface Guidelines.