5,705
edits
Changes
Jump to navigation
Jump to search
Line 21:
Line 21: − + + + Line 42:
Line 44: + + + + + + + +
→Libraries
* Activity - 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 - 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.
== Libraries ==
== Core libraries ==
All core libraries are C based and could contain bindings for various programming languages.
=== [[Activity_Team/Services/Env|env]] ===
=== [[Activity_Team/Services/Env|env]] ===
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.
== Programming language glue libraries ===
These are not C based but written in specific programming language libraries. They are glue level libraries that contain programming language specific code to start developing sugar activities. Libraries don't contain bindings for core, bindings are part of particular core library.
=== [[Activity_Team/Services/Toolkit-python|toolkit-python]] ===
Everything what developers need to start developing sugar activities in Python.