Difference between revisions of "Development Team/Obsolete/sugar-port"

From Sugar Labs
Jump to navigation Jump to search
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TOCright}}
+
<noinclude></noinclude>
 +
 
 +
{{Obsolete | Project was closed.}}
 +
{{TOCright}}
 +
 
  
 
== Goal ==
 
== Goal ==
Line 8: Line 12:
 
* Run on all sugar platforms beginning from 0.82
 
* Run on all sugar platforms beginning from 0.82
 
* Wrap sugar(like filers in ObjectChooser) and non-sugar(like json issue in python2.5/2.6) differences
 
* Wrap sugar(like filers in ObjectChooser) and non-sugar(like json issue in python2.5/2.6) differences
 +
 +
sugar-port should be a bridge between all(in ideal) already deployed sugar versions and activities i.e. it provides backwards compatibility(so the same activity code will work on all sugars) and at the same time provides features from newest sugar(so the same activity code will use last sugar features).
  
 
== Usage ==
 
== Usage ==
  
−
In most cases, to prevent dependencies issue, sugar-port could be embedded to activity's directories tree.<br>
+
In most cases sugar-port could be embedded to activity's directory tree.
−
There is no need to include the whole sugar-port project only the files you are using directly - sugar-port's files don't import each other.
+
There is no need to include the whole sugar-port project only top level
 +
files/directories you are using directly - sugar-port's top level entities
 +
don't import each other.
  
 
== Restrictions ==
 
== Restrictions ==

Latest revision as of 13:17, 17 April 2010

Stop hand.png NOTE:
The content of this page is considered
DEPRECATED and OBSOLETE
It is preserved for historical research, along with its talk page.
Project was closed.


Goal

A set of sugar components/libraries/etc to simplify writing activities.
Cornerstone purposes for this project:

  • Total backwards compatibility for sugar-port API
  • Run on all sugar platforms beginning from 0.82
  • Wrap sugar(like filers in ObjectChooser) and non-sugar(like json issue in python2.5/2.6) differences

sugar-port should be a bridge between all(in ideal) already deployed sugar versions and activities i.e. it provides backwards compatibility(so the same activity code will work on all sugars) and at the same time provides features from newest sugar(so the same activity code will use last sugar features).

Usage

In most cases sugar-port could be embedded to activity's directory tree. There is no need to include the whole sugar-port project only top level files/directories you are using directly - sugar-port's top level entities don't import each other.

Restrictions

Running on all sugar platforms doesn't mean the same functionality on all sugar versions. It means only running without errors and keeping functionality the same as much as possible.

Resources
Retrieved from "https://wiki.sugarlabs.org/index.php?title=Development_Team/Obsolete/sugar-port&oldid=51288"