5,705
edits
Changes
Jump to navigation
Jump to search
Line 34:
Line 34: + + + + + + + − ...+ − The major idea is instead of having 6 months to have a solid core (with stable release cycle) <=> dbus-API/sugar-toolkit-API (ideally, only dbus) <=> unlimited number of activities that use core functionality and do not follow 6 months release cycle (which could be overmuch for activity).+ − − It could looks like: − * '''core''' - glucose, six months (or so) release cycle, w/o any activities, only API − ** in ideal, it should have only dbus API − * '''bridge''' - [[Development_Team/sugar-port|sugar-port]] for example, between all (in ideal) already deployed sugars and activities, i.e., it provides backwards compatibility (so the same activity code will work on all Sugars) and at the same time provides features from newest sugar (so the same activity code will use last Sugar's features). − ** We could write this level in vala to provide core functionality for wide range of programming languages. − * '''world''' - the rest of Sugar world, i.e., Fructose/Honey (but now there are no differences between them) that use core directly, if all deployed Sugars have the same API for desired functionality (for example, in case of preselected mime type, ObjectsChooser has different API for 0.82-0.86), or use bridge otherwise.<br>imho another point to have activities outside of core release cycle - activities have a shorter release cycle then the core has. − And of course deployers can form any sets from these components+ − Core Bridge World + − +------------+ +------------++ − | Sugar-0.82 |---+ +---| Activity A | − +------------+ | +---------------------------+ | +------------+ − +------------+ | | sugar-port | | +------------+ − | ... |--dbus--| do not fail on 0.82 |---+---| ... | − +------------+ | | but uses all 777 features | | +------------+ − +------------+ | +---------------------------+ | +------------+ − | Sugar-777 |---+ +---| Activity Z | − +------------+ +------------+
Platform Team/Package Management System (view source)
Revision as of 07:25, 14 December 2009
, 07:25, 14 December 2009→Detailed Description
So, developers use a set of services that have theirs own API changes based schedules. Existed glucose could be treated as a big service and splited to several components but thats not a task for this proposal. Instead, it's about proposing basic infrastructure of Sugar Services and several services that are not part of glucose.
So, developers use a set of services that have theirs own API changes based schedules. Existed glucose could be treated as a big service and splited to several components but thats not a task for this proposal. Instead, it's about proposing basic infrastructure of Sugar Services and several services that are not part of glucose.
The corner stone of Sugar Services proposal is Saccharin service. This service provides installing/upgrading mechanism for all other services. The rest of services is just variety of sugar libraries/dbus-services.
=== List of services ===
* ''saccharin'', core service
* ''widgets'', UI layer which could assimilate various sugar releases changes e.g. let activity developers use new toolbars even in 0.82 environment and do not use many ''ifs'' in code
* ''bugsreport''
* ''sugargames''
* ...
=== Versioning scheme ===
Each service has API changes based versioning scheme
<major-version>.<minor-version>
* the major version starts from ''0''(premature state) and describes API backwards compatibility breakage
* the minor version is for bugfixes and features that don't break backwards compatibility
== Benefit to Sugar ==
== Benefit to Sugar ==