Changes

'''Note:''' This article is about running standard GNU/Linux applications inside Sugar by using the Activities icon panel rather than starting them from the Terminal.

'''Note:''' This article is about running standard Linux applications inside Sugar by using the Activities icon panel rather than starting them from the Terminal.

==Sugar Coating==

==Sugar Coating==

Many standard Linux programs can be run within Sugar, but without the collaboration and other Sugar integration programmed into them. The process of adding an icon to the Sugar Activities panel is called "Sugar Coating".

Many standard GNU/Linux programs can be run within Sugar, but without the collaboration and other Sugar integration programmed into them. The process of adding an icon to the Sugar Activities panel is called "Sugar Coating".

A simple script to automate the process was created by a woman named CatMoran. The script:

A simple script to automate the process was created by a woman named CatMoran. The script:

*has be confirmed to work with Firefox, Seamonkey, Midnight Commander, TuxType2, TuxPaint and Totem. It it presumed to work with many other Linux programs.

*has be confirmed to work with Firefox, Seamonkey, Midnight Commander, TuxType2, TuxPaint and Totem. It it presumed to work with many other GNU/Linux programs.

*only works with programs that use the same command every time (i.e., a single command with no qualifiers). It doesn't work for roto's current mplayer configuration, because the mplayer command requires an input file name to start the program.

*only works with programs that use the same command every time (i.e., a single command with no qualifiers). It doesn't work for roto's current mplayer configuration, because the mplayer command requires an input file name to start the program.

===To setup (one time):===

===To setup (one time):===

<li>Start a Terminal activity.</li>  

<li>Start a Terminal activity.</li>  

<li>Enter the following commands:</li>  

<li>Enter the following commands:</li>  

  su

  mkdir sugarize

  wget http://www.catmoran.com/olpc/libsugarize.so

  wget http://dl.dropbox.com/u/1203534/sugarize/libsugarize.so

  chmod 755 libsugarize.so

  chmod 755 libsugarize.so

  wget http://www.catmoran.com/olpc/sug

  wget http://dl.dropbox.com/u/1203534/sugarize/sug

  chmod 755 sug

  chmod 755 sug

(What do those commands do? They log you in as root, gets a copy of Albert Cahalan's compiled libsugarize file, and gets the script CatMoran created.)

(What do those commands do? They log you in as root, gets a copy of Albert Cahalan's compiled libsugarize file, and gets the script CatMoran created, modified by akiwiguy.)

 

Optional, if you want to use one of the icons CatMoran created:

Optional, if you want to use one of the icons CatMoran created:

  wget http://www.catmoran.com/olpc/plain.svg

 

  wget http://www.catmoran.com/olpc/ff.svg

  wget http://ia341002.us.archive.org/3/items/Sugarize/plain.svg

  wget http://www.catmoran.com/olpc/l.svg

  wget http://ia341002.us.archive.org/3/items/Sugarize/ff.svg

  wget http://ia341002.us.archive.org/3/items/Sugarize/l.svg

</ol>

</ol>

===To Run (once per program that you want to Sugar Coat):===

===To Run (once per program that you want to Sugar Coat):===

<li>Enter the following commands, to log in as root and execute the sug script. T quit the script at any time, just enter nothing at the prompt and hit the Enter button.</li>

<li>Enter the following commands, to log in as root and execute the sug script. T quit the script at any time, just enter nothing at the prompt and hit the Enter button.</li>

 

  ./sug

  ./sug

First, you'll be prompted for an activity name. Enter a short, descriptive name with no spaces or punctuation, such as BibleTime, Firefox, or MC.

First, you'll be prompted for an activity name. Enter a short, descriptive name with no spaces or punctuation, such as BibleTime, Firefox, or MC.

Second, you'll be prompted for an icon file to copy into the new task. Enter the [[DocumentationTeam/Glossary|full path and filename]] of any .svg file. If the icon is in the same directory as the sug file, you can enter just the filename.

Second, you'll be prompted for an icon file to copy into the new task. Enter the [[Documentation Team/Glossary|full path and filename]] of any .svg file. If the icon is in the same directory as the sug file, you can enter just the filename.

Next, you'll be prompted for the command to start the program. This is the command you type at the Terminal prompt to start the program, such as firefox, totem, or mc.

Next, you'll be prompted for the command to start the program. This is the command you type at the Terminal prompt to start the program, such as firefox, totem, or mc.

The script will give you a success message. Reboot Sugar by pressing Ctrl-Alt-Erase (the Control, Alt and Erase buttons) at the same time. When Sugar restarts you will now see the new icon in the Sugar taskbar. A simple click on the icon will start the newly Sugar Coated program, like any other Sugar Activity.

The script will give you a success message. Reboot Sugar by pressing Ctrl-Alt-Erase (the Control, Alt and Erase buttons) at the same time. When Sugar restarts you will now see the new icon in the Sugar taskbar. A simple click on the icon will start the newly Sugar Coated program, like any other Sugar Activity.

</ol>

</ol>

===Sugar Coat Script Mirror Servers===

===Sugar Coat Script Mirror Servers===

'''Source''' - [http://olpcnews.com/forum/index.php?topic=1555.0 http://olpcnews.com/forum/index.php?topic=1555.0]

'''Look at:''' http://people.sugarlabs.org/Tgillard/sugarize/wiki-sugarize.txt

I haven't been able to get this to work in Update.1 --leetcharmer

I haven't been able to get this to work in Update.1 --[[leetcharmer]]

Rob - I modified the script to work in Update 1 for SeaMonkey, but it requires an effective disabling of security.  The crux of the problem is that Rainbow runs your application as a totally new user each time (never as "olpc"), and that these "on-the-fly" users don't have write access to their home directories.    All of these users are created in the same persistent group, and all share write access to a common "data" directory for the group.  (The preceding is just a paraphrase of the Rainbow docs - should likely be a link).  In the case of non-Sugar apps, the application has no idea that the usual role of a user has been migrated to a group, and so the application is unlikely to create it's data files with the correct permissions.

Rob - I modified the script to work in Update 1 for SeaMonkey, but it requires an effective disabling of security.  The crux of the problem is that Rainbow 1) runs your application as a totally new user each time (never as "olpc"), 2) these "on-the-fly" users don't have write access to their home directories, and 3) these "on-the-fly" users are destroyed on reboot.    All of these users are created in the same persistent group, and all share write access to a common "data" directory for the group.  (The preceding is just a paraphrase of the Rainbow docs - should likely be a link).  In the case of non-Sugar apps, the application has no idea that the usual role of a user has been migrated to a group, and so the application is unlikely to create it's data files with the correct permissions.  Further, since the "on-the-fly" users are destroyed on each reboot, if the username appears in persistent data (e.g., absolute pathnames), the application will fail after a reboot.  All of these issues are addressed in the following for the SeaMonkey application.

'''Note Well:'''  ''The following instructions essentially remove all security on your machine.  If you have set passwords on any of the machine accounts (root, olpc, etc.), likely you don't want to execute these instructions.''

'''Note Well:'''  ''The following instructions essentially remove all security on your machine.  If you have set passwords on any of the machine accounts (root, olpc, etc.), likely you don't want to execute these instructions.''

# Causes SeaMonkey to put the .mozilla directory in a

# Causes SeaMonkey to put the .mozilla directory in a

# place that is writable, and also where Rainbow wants

# place that is writable, and also where Rainbow wants

# it.  SUGAR_ACTIVITY_ROOT is not suitable since it

# it.  SUGAR_ACTIVITY_ROOT/data is not directly suitable

# contains a reference to a user that will be destroyed

# since it contains a reference to a user that will  

# on reboot.

# be destroyed on reboot, and SeaMonkey stores absolute

export HOME="/home/olpc/isolation/1/gid_to_data_dir/$GROUPS"

# pathnames in its persistent data.

export HOME=`/bin/ls -l $SUGAR_ACTIVITY_ROOT/data | /usr/bin/awk '{ print $10 }'`

# libgnomevfs ignores the HOME environment variable,

# libgnomevfs ignores the HOME environment variable,

exec /usr/bin/seamonkey

exec /usr/bin/seamonkey

</pre>

</pre>