687
edits
Changes
User:Inkyfingers/Testing Sweets (view source)
Revision as of 02:26, 20 December 2011
, 02:26, 20 December 2011What would an experienced user do next?
insert wording generated by successful upgrade.
insert wording generated by successful upgrade.
If you run into difficulties, Sweets contains a --help file. You get it with the command:
If you run into difficulties, sweets contains a --help file. You get it with the command:
sweets -h
sweets -h
* {{Code|dextrose/sugar}}, for Sugar based on [[Dextrose]].
* {{Code|dextrose/sugar}}, for Sugar based on [[Dextrose]].
The terms we use are currently defined here: [[Platform_Team/Guide/Sweets_Usage#Search]].
The terms we use are currently defined here: [[Platform_Team/Guide/Sweets_Usage#Search]] and [[Platform_Team/Sweets/Glossary]]
The '''name''' of one available sweet (alternate usage ''<SWEET>'' ) is sdk/sugar.
The '''name''' of one available {{code|sweet}} (alternate usage ''<SWEET>'' ) is sdk/sugar.
Another's '''name''' (alternate usage ''<SWEET>'') is dextrose/sugar.
Another's '''name''' (alternate usage ''<SWEET>'') is dextrose/sugar.
<s>Both Sugars can be used in the same way. This guide uses {{Code|dextrose/sugar}} ... and may use {{Code|sdk/sugar}}</s>
<s>Both Sugars can be used in the same way. This guide uses {{Code|dextrose/sugar}} ... and may use {{Code|sdk/sugar}}</s>
== Launch ==
To launch recent stable Sugar in emulator mode, type in Terminal activity or in any other terminal:
sweets dextrose/sugar:emulator
To explain:
: sweets - the command to run sweets
:: dextrose/sugar - the sweet you want
::: :emulator - a command for an emulator.
To make it possible to have additional dependencies involved, e.g., to run Browse activity, use {{Code|-S}} command-line argument:
sweets -S dextrose/sugar:emulator
: adding -S forces ... wording is not to hand.
Hopefully one of those commands opened Sugar for you.
If not, try
sweets sdk/sugar:emulator
or
sweets -S sdk/sugar:emulator
'''If you have Sugar running - Explore'''
=== If you have a negative response to all four commands above ===
So this is the point of this effort!
'''What can we conclude?'''
Go back, review #Upgrade above, If {{Code|sweets upgrade}} and {{Code|sweets -h}} were positive - sweets is installed, no?
What further commands or tools are available at this point?
One possibility, not all required packages are installed?
Referring to my own experience - [[Talk:Platform Team/Guide/Sugar via Sweets#Installation 2]] (which is considerably abbreviated!)
the command {{Code|sweets -R sdk/sugar:emulator}} invoked a massive download of packages - @alsroot what changed?
'''What would an experienced user do next?'''
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?
I am currently in the above described situation with Sweets on Debian Wheezy. What is suggested here, I will test there.
'''Alternatively''', {{Code|sweets}} might be run from the [[Platform_Team/Guide/Sweets_Packaging#Run_Sweets_from_sources|sources]]. This I have tried - I am not sure it adds content if one is stuck at this point?
''' The material below this point has not been edited.'''
''' Please move this marker if you edit, thanks.'''
* Back to original "Usage" page content.
== Usage ==
== Usage ==
See the [[Platform_Team/Guide/Sugar_via_Sweets|Sugar via Sweets]] guide for real examples of how to use ''Sweets'' to run Sugar Shell.
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 ===
=== Launch, as copied from original, Usage page. ===
To launch a ''sweet'' with verbatim passing of optional {{Code|ARGUMENTS}}:
To launch a ''sweet'' with verbatim passing of optional {{Code|ARGUMENTS}}: