Sugar Labs

Platform Team/Sugar Packaging Management System: Difference between revisions

← Older editNewer edit →
Line 28: Line 28:
For example in case of sugar-toolkit, it could be splited to:
For example in case of sugar-toolkit, it could be splited to:


* toolkit-shell, to incapsulate various shell related things
* move all shell related API to shell itself to have one solid service - shell
* toolkit-graphics, list of widgets that use stable API from toolkit-shell and mostly are shell independent
* toolkit service, list of widgets that use stable API from shell service and mostly are shell independent
* toolkit-datastore, to wrap sugar-datastore API and will be released only with sugar-datastore
* move all datastore related code to sugar-datastore - datastore service


Services should be as independent as possible e.g. activity developers could use toolkit-graphics from 0.88 cycle with toolkit-shell from 0.82(since its API wasn't changed).
Services should be independent as much as possible e.g. activity developers could use toolkit service from 0.88 cycle with shell service from 0.82(since its API wasn't changed).
Retrieved from "https://wiki.sugarlabs.org/go/Platform_Team/Sugar_Packaging_Management_System"