Sugarizer: Difference between revisions

(One intermediate revision by one other user not shown)

Line 3:

|- style="vertical-align:top;"

|[[File:Sugarizer_responsive.png|200px|left|link=]]

|Sugarizer is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on [https://github.com/sugarlabs/sugar-web Sugar Web library] ~~that mimic~~ the Sugar UI using HTML5 and CSS3 and ~~reproduce~~ Sugar views (Home, List, ...). Sugarizer ~~reimplement~~ features of Sugar Core (datastore and journal) in JavaScript and ~~integrate~~ a bunch of activities written for Sugar in Sugar Web. So basically, Sugarizer is "just" a launcher of Sugar Web activities. A Sugarizer server ~~part allow~~ collaboration and presence.

|Sugarizer is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on [https://github.com/sugarlabs/sugar-web Sugar Web library], which mimics the Sugar UI using HTML5 and CSS3 and reproduces Sugar views (Home, List, ...). Sugarizer reimplements features of Sugar Core (datastore and journal) in JavaScript and integrates a bunch of activities written for Sugar in Sugar Web. So basically, Sugarizer is "just" a launcher of Sugar Web activities. A Sugarizer server component allows collaboration and presence.

Sugarizer could run any Sugar activities written in HTML5/JavaScript (Gears, Abecedarium, ...) and include a bunch of Sugar activities written initially in Python an ported in HTML5/JavaScript (Physics, Paint, ...).

Sugarizer is distributed in the form of 3 components:

Line 14:

Line 15:

== Thin Client ==

Sugarizer Thin Client is Sugarizer in a browser. Sugarizer Thin Client doesn't need any installation on the device but requires a permanent access to a Sugarizer Server.

Sugarizer Thin Client is Sugarizer in a browser. Sugarizer Thin Client doesn't need any installation on the device but requires permanent access to a Sugarizer Server.

== Client ==

@@ Line 3: / Line 3: @@
 |- style="vertical-align:top;"
 |[[File:Sugarizer_responsive.png|200px|left|link=]]
-|Sugarizer is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on [https://github.com/sugarlabs/sugar-web Sugar Web library] that mimic the Sugar UI using HTML5 and CSS3 and reproduce Sugar views (Home, List, ...). Sugarizer reimplement features of Sugar Core (datastore and journal) in JavaScript and integrate a bunch of activities written for Sugar in Sugar Web. So basically, Sugarizer is "just" a launcher of Sugar Web activities. A Sugarizer server part allow collaboration and presence.
+|Sugarizer is a way to use Sugar on any device using web technologies (HTML5/JavaScript). Strictly speaking, Sugarizer is not a port of Sugar. Sugarizer is based on [https://github.com/sugarlabs/sugar-web Sugar Web library], which mimics the Sugar UI using HTML5 and CSS3 and reproduces Sugar views (Home, List, ...). Sugarizer reimplements features of Sugar Core (datastore and journal) in JavaScript and integrates a bunch of activities written for Sugar in Sugar Web. So basically, Sugarizer is "just" a launcher of Sugar Web activities. A Sugarizer server component allows collaboration and presence.
+Sugarizer could run any Sugar activities written in HTML5/JavaScript (Gears, Abecedarium, ...) and include a bunch of Sugar activities written initially in Python an ported in HTML5/JavaScript (Physics, Paint, ...).
 Sugarizer is distributed in the form of 3 components:
@@ Line 14: / Line 15: @@
 == Thin Client ==
-Sugarizer Thin Client is Sugarizer in a browser. Sugarizer Thin Client doesn't need any installation on the device but requires a permanent access to a Sugarizer Server.
+Sugarizer Thin Client is Sugarizer in a browser. Sugarizer Thin Client doesn't need any installation on the device but requires permanent access to a Sugarizer Server.
 == Client ==