Difference between revisions of "Features/Sugar Activity Library on a Stick"

Revision as of 21:29, 21 June 2010

Summary

140 plus activity.xo files to download and copy to a USB stick. The stick is used to install these application.xo files, by drag-drop to the Journal of a running Soas USB or CD

Owner

This should link to your home wiki page so we know who you are

Name: [Tom Gilliard]

Email: satellit@bendbroadband.com

Current status

Targeted release: (Soas-v4)
Last updated: (06/21/2010)
Percentage of completion: 50%

Detailed Description

140 plus activity.xo files to download and copy to a USB stick. The stick is used to install these application.xo files, by drag-drop to the Journal of a running Soas USB or CD
Includes a Open Office Spreadsheet for a key to Compatible Applications for different versions of Soas.

Benefit to Sugar

Allows sneaker-net installs and installs behind firewalls in schools.
Saves Multiple Downloads of Applications.
Can add and remove activities on demand without web connectivity.
Use and pass on the stick, locally.

Scope

Already in existence. just has to be updated as new Applications and versions are made available on ASLO.

UI Design

N/A

How To Test

On your PC:

Download ASLOxo.iso from http://people.sugarlabs.org/Tgillard/ASLOxo-2+ss.tar.bz2
transfer the contents of the extracted folder to 2nd 1GB USB ASLOxo stick

Boot a Soas USB or a running Soas CD

insert ASLOxo USB into a USB slot, wait for it to mount.
select journal on top of sugar's frame.
drop down to bottom left corner of screen, the frame will retract and show 2 USB Icons.
select the 2nd (right) USB (ASLOxo)
drag-drop the desired application.xo (hold down the left button and drag the entry) from the listing into the sugar-journal on the bottom (left USB icon) corner of the monitor.
OR double click on application.xo in the list of the ASLOxo USB.

The Application

should start normally.
shut down normally
Collaborate if that is a feature
resume from the saved journal

All behavior should be identical to a download in Browse from Activities (ASLO)
http://activities.sugarlabs.org/en-US/sugar/

User Experience

Faster Installs, easy customization of Applications on Soas USB

Dependencies

None

Contingency Plan

None Needed already implemented

Documentation

Release Notes

http://people.sugarlabs.org/Tgillard/ASLOxo-2_ssREADME.txt

Comments and Discussion

See discussion tab for this feature

@@ Line 6: / Line 6: @@
 </noinclude>
-'''Comments and Explanations:'''
-There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy|Feature Policy Page]] for a more detailed explanation of the new-feature process. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes!  DO NOT EDIT THIS TEMPLATE.'''
-<!-- All fields on this form are required to be accepted.
- We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
-<!-- The actual name of your feature page should look something like: Features/Your Feature Name.  This keeps all features in the same namespace -->
 == Summary ==
-''A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release.''
+plus activity.xo files to download and copy to a USB stick. The stick is used to install these application.xo files, by drag-drop to the Journal of a running Soas USB or CD
 == Owner ==
@@ Line 22: / Line 14: @@
 * Name: [[http://wiki.sugarlabs.org/go/User:Satellit| Tom Gilliard]]
-''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''
 * Email: satellit@bendbroadband.com
@@ Line 31: / Line 23: @@
 == Detailed Description ==
-''Expand on the summary, if appropriate.  A couple of sentences suffices to explain the goal, but the more details you can provide the better.''
+* 140 plus activity.xo files to download and copy to a USB stick. The stick is used to install these application.xo files, by drag-drop to the Journal of a running Soas USB or CD
+* Includes a Open Office Spreadsheet for a key to Compatible Applications for different versions of Soas.
 == Benefit to Sugar ==
-''What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''
+* Allows sneaker-net installs and installs behind firewalls in schools.
+* Saves Multiple Downloads of Applications.
-''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.''
+* Can add and remove activities on demand without web connectivity.
+* Use and pass on the stick, locally.
 == Scope ==
-''What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?''
+Already in existence. just has to be updated as new Applications and versions are made available on ASLO.
 ==UI Design==
-''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''
+N/A
 == How To Test ==
 {{:{{PAGENAME}}/Testing}}
 == User Experience ==
-''If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice.''
+* Faster Installs, easy customization of Applications on Soas USB
 == Dependencies ==
-''What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time?  Other upstream projects like Python?''
+None
 == Contingency Plan ==
-''If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''
+None Needed already implemented
 == Documentation ==
-''Is there upstream documentation on this feature, or notes you have written yourself?  Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''
 == Release Notes ==
-''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the release team and shipped with the release.''
+http://people.sugarlabs.org/Tgillard/ASLOxo-2_ssREADME.txt
 == Comments and Discussion ==
 * See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page. -->