5,705
edits
Changes
Jump to navigation
Jump to search
Line 6:
Line 6: + + Line 47:
Line 49: − − == Detailed description == − − This proposal assumes that the core of Sugar development (in common sense) is a wide variety of developers, not just those developers who are taking part in Sugar core (glucose) development. It is all about seeing Sugar activity development from an activity/3rd-party developer's point of view. − − From such new core POV, the Sugar development process will consist of: − * a variety of Sugar activities − * that use a variety of Sugar Services − Developers use a set of services that have their own [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|API-changes-based]] schedules. Glucose [[Activity Team/Services/Glucose|could be]] [[Documentation Team/Services/Native packages usage|wrapped]] to service(s) as well; treating Glucose as a normal dependency lets developers target their activity or services for a particular Glucose versions and warn users about outdated Sugar environment. − − The corner stone of Sugar Services proposal is [[Activity_Team/Services/Saccharin|Saccharin]] service. This service provides installing/upgrading (via 0install) mechanism for services. The rest of services is just variety of libraries/applications/native-packages. Saccharin could be included as a part of Glucose (in some releases) or else included in .xo bundles.
Platform Team/Package Management System (view source)
Revision as of 06:16, 10 January 2010
, 06:16, 10 January 2010create explanation page
Sugar Services provides transparency for users and convenience for activity developers across varying platforms (and their varying dependencies) as well as across Sugar releases. Sugar Services is a method to support this variety of activity dependencies and variety of dependency versions. In other words, Services is a common deployment system for activity dependencies; it is lightweight like [[Development_Team/Sugargame|sugargame]] and like Qt.
Sugar Services provides transparency for users and convenience for activity developers across varying platforms (and their varying dependencies) as well as across Sugar releases. Sugar Services is a method to support this variety of activity dependencies and variety of dependency versions. In other words, Services is a common deployment system for activity dependencies; it is lightweight like [[Development_Team/Sugargame|sugargame]] and like Qt.
See [[Editing Documentation Team/Services/Scalable development process|Scalable development process]] page to know more about initial purposes of Sugar Services.
== Workflows ==
== Workflows ==
See [[Documentation_Team/Services/Native_packages_usage|Native packages usage]] to know how to utilize native packages in your activity or service.
See [[Documentation_Team/Services/Native_packages_usage|Native packages usage]] to know how to utilize native packages in your activity or service.
== FAQ ==
== FAQ ==