Difference between revisions of "Development Team/Obsolete/sugar-port"
< Development Team | Obsolete
Jump to navigation
Jump to search
(→Goal) |
(→Usage) |
||
| Line 11: | Line 11: | ||
== Usage == | == Usage == | ||
| − | In most cases, to prevent dependencies issue, sugar-port could be embedded to activity's directories tree. | + | In most cases, to prevent dependencies issue, sugar-port could be embedded to activity's directories tree.<br> |
| + | 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 others. | ||
== Restrictions == | == Restrictions == | ||
Revision as of 18:48, 17 April 2009
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
Usage
In most cases, to prevent dependencies issue, sugar-port could be embedded to activity's directories 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 others.
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.