5,705
edits
Changes
Jump to navigation
Jump to search
Line 13:
Line 13: − + − + − + Line 33:
Line 33: − + Line 41:
Line 41: − + − + − + − + − + − +
no edit summary
[[File:polyol.png|500px]]
[[File:polyol.png|500px]]
=== Glucose processes ===
==== Glucose processes ====
Sugar core processes and dbus services.
Sugar core processes and dbus services.
=== DBus ===
==== DBus ====
All communication between glucose level and activity process goes via dbus.
All communication between glucose level and activity process goes via dbus.
=== Polyol group ===
==== Polyol group ====
Intermediate level libraries:
Intermediate level libraries:
* 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 ===
==== 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.
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.
All libraries are C based and could contain bindings for various programming languages.
All libraries are C based and could contain bindings for various programming languages.
=== [[Activity_Team/Services/Env|env]] ===
==== [[Activity_Team/Services/Env|env]] ====
Access to various sugar environment settings.
Access to various sugar environment settings.
=== [[Activity_Team/Services/Shell|shell]] ===
==== [[Activity_Team/Services/Shell|shell]] ====
Compatibility level library to sugar-shell.
Compatibility level library to sugar-shell.
=== [[Activity_Team/Services/Collab|collab]] ===
==== [[Activity_Team/Services/Collab|collab]] ====
High level client API for what activity developers might need to code collab activities.
High level client API for what activity developers might need to code collab activities.
=== [[Activity_Team/Services/Ds|ds]] ===
==== [[Activity_Team/Services/Ds|ds]] ====
High level client API to sugar-datastore.
High level client API to sugar-datastore.
=== [[Activity_Team/Services/Gui|gui]] ===
==== [[Activity_Team/Services/Gui|gui]] ====
A set of first level GUI widgets to simplify process of activity creation.
A set of first level GUI widgets to simplify process of activity creation.
=== [[Activity_Team/Services/Toolkit|toolkit]] ===
==== [[Activity_Team/Services/Toolkit|toolkit]] ====
Everything what developers need to start developing native sugar activities. Library depends on all other Polyol components and contains glue level code that simplify creating sugar activities from scratch. This library (and all its dependencies) is an analog of python based sugar-toolkit library.
Everything what developers need to start developing native sugar activities. Library depends on all other Polyol components and contains glue level code that simplify creating sugar activities from scratch. This library (and all its dependencies) is an analog of python based sugar-toolkit library.
Bindings for this library (in contrast with bindings for other Polyol components) could contain not only wrappers for library itself, but also particular language specific code that makes process of creating sugar activities in this language more comfortable.
Bindings for this library (in contrast with bindings for other Polyol components) could contain not only wrappers for library itself, but also particular language specific code that makes process of creating sugar activities in this language more comfortable.