Changes

1,452 bytes added , 03:22, 22 December 2011

the sweet "base/x11-libs" had a bug that was found in mint

Line 6: Line 6:

:http://wiki.sugarlabs.org/go/Community/Distributions/Sweets_Distribution

:works fine for 11.04 Linux Mint 11 I did this and it worked but alsroot wanted me to not put it on the wiki. It installs sweets-sugar 0.94.1 [[User:Satellit]] 9 Dec 2011

+

::Link: [[Talk:Platform_Team/Guide/Sugar_via_Sweets#Installing_sweets-sugar_from_Fedora_16_GNOME_3_Terminal|Installing_sweets-sugar_from_Fedora_16_GNOME_3_Terminal]]

+

:http://wiki.sugarlabs.org/go/Sugar_Creation_Kit/sck/Advanced_Topics#Sweets

+

== Exploring extra documentation ==

−

Expanding central section of [[~~Platform_Team~~/Guide/~~Sweets_Usage~~]]] ...

+

Expanding central section of [[Platform Team/Guide/Sweets Usage]]] ...

=== Aim of this paper ===

Line 14: Line 17:

=== Install ===

Imagine you are now reading [[Sweets/Getting started]]

+

Pre-introductory paragraphs explain what an emulator will look like, and the reasons for experimenting with it.

Introductory paragraph will have "fully" covered distro-non-specific apt-get update.

Line 21: Line 26:

Then "packagekit" and issues, then download and run script "installer.sh"

−

Then, "After installing PackageKit, you need to restart the DBus system bus." or "Relogin from X session"

+

Then, "After installing PackageKit, you need to restart the DBus system bus," "Relogin from X session," or "Restart the machine"

−

: Minor issue 1. a) "Restart the machine" seems clumsy. b) distro-non-specific instructions ~~I guess are~~ too difficult. It might be nice to include, say, the best available outside tutorial, even if only to demonstrate good practice?

+

: Minor issue 1. a) "Restart the machine" seems clumsy. b) I guess distro-non-specific instructions may be too difficult? It might be nice to include, say, the best available outside tutorial, even if only to demonstrate good practice?

''Alternatively, {{Code|sweets}} might be run from the [[Platform_Team/Guide/Sweets_Packaging#Run_Sweets_from_sources|sources]].''

:Issue 2. This idea needs dealing with at an appropriate level. Is this an alternative for our reader? Under what conditions would the reader start on this method?

+

=== Upgrade ===

Line 43: Line 49:

The file is displayed in your terminal, you get out of the file by pressing "q" for quit.

+

'''What about a negative response to your initial {{code|sweets}} command?'''

+

An example of a negative response at this stage is:

+

sweets: command not found.

+

If you are in this situation - did you restart either {{code|dbus}} or the computer before you gave the first {{code|sweets}} command?

+

You could restart the computer. If you still get a negative response from

+

sweets upgrade

+

and

+

sweets -h

+

then you need to work through the instructions above this point again.

==== What Sugar to launch ====

Line 56: Line 75:

Another's '''name''' (alternate usage ''<SWEET>'') is dextrose/sugar.

+

<s>look at : [[Talk:Platform_Team/Guide/Sugar_via_Sweets#Notes_on_how_to_start_0.88_or_0.94| How to start 0.88 or 0.94 Sweets Sugar]]--[[User:Satellit|Satellit]] 15:42, 21 December 2011 (EST). Thanks, added in next paragraph.</s>

: These lines aim to draw attention a perceived difficulty in nomenclature. Improved wording welcome.

<s>Both Sugars can be used in the same way. This guide uses {{Code|dextrose/sugar}} ... and may use {{Code|sdk/sugar}}</s>

+

== Launch ==

Line 73: Line 95:

sweets -S dextrose/sugar:emulator

−

~~: adding~~ -S ~~forces ... wording is not~~ to ~~hand.~~

+

To explain,

+

we add an option, -S ( = --force-suggested) to force, using suggested dependencies

Hopefully one of those commands opened Sugar for you.

Line 83: Line 107:

sweets -S sdk/sugar:emulator

+

we can also add an option to the emulator, for example,

+

sweets sdk/sugar:emulator -f

+

will ask the emulator to open, full screen.

+

'''If you have Sugar running - Explore'''

Line 99: Line 128:

the command {{Code|sweets -R sdk/sugar:emulator}} invoked a massive download of packages - @alsroot what changed?

+

: Snip from IRC #sugar-newbies, [21:25] <alsroot> the sweet "base/x11-libs" had a bug that was found in mint

+

'''What would an experienced user do next?'''

+

I think it is worth discussing, and I am not sure about this, some investigatory commands gave misleading answers, I feel because the whole toolbox was not present.

−

~~'''What would an experienced user do next~~?~~'''~~

+

Have I drawn the wrong conclusion?

−

~~I think it is worth discussing, and I am not sure about this, in this situation (in my experience) many investigatory commands gave misleading answers, I feel because the whole toolbox was not present~~. ~~Have I drawn~~ the ~~wrong conclusion~~?

+

A question regarding -R option. Would the -R option eg:

+

sweets -R sdk/sugar:emulator

+

be superfluous straight after {{code|sweets upgrade}}?

I am currently in the above described situation with Sweets on Debian Wheezy. What is suggested here, I will test there.

Line 124: Line 159:

See the [[Platform_Team/Guide/Sugar_via_Sweets|Sugar via Sweets]] guide for real examples of how to use ''Sweets'' to run Sugar Shell.

−

=== Launch~~, as copied from original, Usage page.~~ ===

+

=== Launch ===

To launch a ''sweet'' with verbatim passing of optional {{Code|ARGUMENTS}}:

Inkyfingers

687

edits

Changes

User:Inkyfingers/Testing Sweets (view source)

Revision as of 03:22, 22 December 2011