Difference between revisions of "Development Team/Obsolete/sugar-port"
(→Usage) |
|||
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | <noinclude>{{ | + | <noinclude></noinclude> |
+ | |||
+ | {{Obsolete | Project was closed.}} | ||
+ | {{TOCright}} | ||
+ | |||
== Goal == | == Goal == |
Latest revision as of 13:17, 17 April 2010
GoalA set of sugar components/libraries/etc to simplify writing activities.
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). UsageIn 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. RestrictionsRunning 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 |