Platform Team/Polyol: Difference between revisions

Line 13:

[[File:polyol.png|500px]]

~~'''~~Glucose processes~~''' Sugar core processes and dbus services.~~

=== Glucose processes ===

~~'''DBus''' All communication between glucose level~~ and ~~activity process goes via~~ dbus.

Sugar core processes and dbus services.

~~'''~~Polyol group~~''' ~~Intermediate level libraries:

=== DBus ===

All communication between glucose level and activity process goes via dbus.

=== Polyol group ===

Intermediate level libraries:

* Glucose compatibility libraries (ds, shell, collab) will support several (popular among sugar deployments) glucose releases

* Other libraries are not tied to glucose directly

Key features of this level:

* All libraries are written in Vala, i.e., based on pure GObjects, and could be used by non-python-based activities.

Line 26:

Line 33:

* Activities (mostly not native sugar activities) could use only one library e.g. activity could use only ''ds'' library thus do not fetch additional dependencies like telepathy (via ''collab'') and gtk+ (via ''gui'').

~~'''~~Activity process~~''' ~~Regular activities would not use glucose directly, rather they would only access glucose through the Polyol level. There is no need to code special activities, the sugar-toolkit API will be preserved, and activity developers will benefit because Polyol will support the recent sugar-toolkit API, e.g., they could use the new toolbars design even on Sugar 0.82.

=== Activity process ===

Regular activities would not use glucose directly, rather they would only access glucose through the Polyol level. There is no need to code special activities, the sugar-toolkit API will be preserved, and activity developers will benefit because Polyol will support the recent sugar-toolkit API, e.g., they could use the new toolbars design even on Sugar 0.82.

== Components ==

@@ Line 13: / Line 13: @@
 [[File:polyol.png|500px]]
-'''Glucose processes'''<br>Sugar core processes and dbus services.
+=== Glucose processes ===
-'''DBus'''<br>All communication between glucose level and activity process goes via dbus.
+Sugar core processes and dbus services.
-'''Polyol group'''<br>Intermediate level libraries:
+=== DBus ===
+All communication between glucose level and activity process goes via dbus.
+=== Polyol group ===
+Intermediate level libraries:
 * Glucose compatibility libraries (ds, shell, collab) will support several (popular among sugar deployments) glucose releases
 * Other libraries are not tied to glucose directly
 Key features of this level:
 * All libraries are written in Vala, i.e., based on pure GObjects, and could be used by non-python-based activities.
@@ Line 26: / Line 33: @@
 * Activities (mostly not native sugar activities) could use only one library e.g. activity could use only ''ds'' library thus do not fetch additional dependencies like telepathy (via ''collab'') and gtk+ (via ''gui'').
-'''Activity process'''<br>Regular activities would not use glucose directly, rather they would only access glucose through the Polyol level.<br>There is no need to code special activities, the sugar-toolkit API will be preserved, and activity developers will benefit because Polyol will support the recent sugar-toolkit API, e.g., they could use the new toolbars design even on Sugar 0.82.
+=== Activity process ===
+Regular activities would not use glucose directly, rather they would only access glucose through the Polyol level.<br>There is no need to code special activities, the sugar-toolkit API will be preserved, and activity developers will benefit because Polyol will support the recent sugar-toolkit API, e.g., they could use the new toolbars design even on Sugar 0.82.
 == Components ==