Changes

''Are not these following benefits for activity developers?''

''Are not these following benefits for activity developers?''

 

* providing libraries or applications that are not intended to be included to [[0.86/Platform_Components|Sugar Platform]]

* providing libraries or applications that are not intended to be included to [[0.86/Platform_Components|Sugar Platform]]

** including libraries that are used by only a few activities; or

** including libraries that are used by only a few activities; or

** have shorter or longer release/support schedules than Sucrose;

** have shorter or longer release/support schedules than Sucrose;

* deploying dependencies that are specific to particular activity; for example, some Python activities include C libraries—by using Services, an activity developer need not bundle all the binaries that Sugar supports; links can be provided links to any binaries that have been build, Services will build additional C libraries from source on user side where they are required.

* deploying dependencies that are specific to particular activity; for example, some Python activities include C libraries—by using Services, an activity developer need not bundle all the binaries that Sugar supports; links can be provided links to any binaries that have been build, Services will build additional C libraries from source on user side where they are required.

See [[Activity Team/Documentation/Services/Service Developers Guide|Service Developers Guide]] to learn how to create Sugar Services.

See [[Activity Team/Documentation/Services/Service Developers Guide|Service Developers Guide]] to learn how to create Sugar Services.