For example in case of sugar-toolkit, it could be splited to:
For example in case of sugar-toolkit, it could be splited to:
−
* move all shell related API to shell itself to have one solid service - shell
+
* move all shell related API to shell itself to have one solid service - shell and provide dbus API for all shell related needs e.g. getting information about sugar environment
* toolkit service, list of widgets that use stable API from shell service and mostly are shell independent
* toolkit service, list of widgets that use stable API from shell service and mostly are shell independent
* move all datastore related code to sugar-datastore - datastore service
* move all datastore related code to sugar-datastore - datastore service
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).
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).