5,705
edits
Changes
Jump to navigation
Jump to search
Line 9:
Line 9: − +
Development Team/Obsolete/sugar-port (view source)
Revision as of 23:57, 21 May 2009
, 23:57, 21 May 2009→Goal
* 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 sugars 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).
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 ==