Development Team/Obsolete/sugar-port: Difference between revisions

(4 intermediate revisions by 2 users not shown)

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}}

== Goal ==

Line 9:

Line 13:

* 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 ==

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 ==

@@ 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 ==
@@ Line 9: / Line 13: @@
 * 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 ==
-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 ==