Jump to: navigation, search

Features/Sugar Update Control ASLO

465 bytes removed, 14:38, 5 November 2013
no edit summary
<noinclude>{{GoogleTrans-en}}{{TOCright}}[[Category:Feature Accepted 0.86]][[Category:FeatureLanded|Sugar Update Control ASLO]]</noinclude>
== Summary ==
== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[User:dfarning| David Farning]]
''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: <>
== Current status ==
* Targeted release: .86
* Last updated: 30 July 15 August 2009* Percentage of completion: 75100% All basic functionality is present. Needs testing.
== Source ==
== Detailed Description ==
Update enables users to update their installed activities from the Activities Library at is base based on the well -established
Using ASLO the client can request information about updated updates by sending a url URL of the form,
ASLO responds by returning an XML of the form,
<?xml version="1.0" encoding="UTF-8"?>
<RDF:RDF xmlns:RDF="" xmlns:em=""><RDF:Description about="urn:mozilla:extension:org.laptop.WebActivity">
== Benefit to Sugar ==
== Scope ==
Technically the scope is limited. Most of the changes are inside sugar-update-the control panel extension or are in ASLO.
There will not be external api changes.
Over the last several months, ASLO has been improving and proving it's reliability. Many activities are being served via ASLO as their information is marked deprecated on Shifting update to point to also ASLO will require clear communication to end users and developers.
=== Implementation ===
* [ Updater component for control panel]
== How To Test ==
 Click on M Settings -> Software update. Visually verify the "From Version XXX to XXX" is correct for your system. NOTE{{: the updater currently reports information on all activities, not just the ones with valid updates. This is for debug purposes. {{PAGENAME}}/Testing}}
== User Experience ==
Nothing should change from The user point of viewwill be able to check if there are any activity updates that can be fetched and installed.
== Dependencies ==
== Release Notes ==
As of Sugar 0.86, upload will default to the only backend is . Specifying other servers and update formats are out of scope of this specific feature.
== 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 -->
[[Category:Feature Page Incomplete]]
''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''

Navigation menu