5,705
edits
Changes
→Concepts
[[File:polyol.png|500px]]
[[File:polyol.png|500px]]
=== Glucose processes ===
Sugar core processes and dbus services.
=== 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
* Glucose compatibility libraries (ds, shell, collab) will support several (popular among sugar deployments) glucose releases
* Other libraries are not tied to glucose directly
* Other libraries are not tied to glucose directly
Key features of this level:
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.
* All libraries are written in Vala, i.e., based on pure GObjects, and could be used by non-python-based activities.
* 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'').
* 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.<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 ==
== Components ==