Changes

Jump to navigation Jump to search
Line 28: Line 28:  
* 3rd party applications that are not included to Sugar Platform e.g. Qt
 
* 3rd party applications that are not included to Sugar Platform e.g. Qt
 
* applications that were not included to all deployed Sugar Platforms e.g. gst-espeak came only from 0.84 and Services will let gst-espeak based activities work even in 0.82 environment
 
* applications that were not included to all deployed Sugar Platforms e.g. gst-espeak came only from 0.84 and Services will let gst-espeak based activities work even in 0.82 environment
* dependencies that are specific to particular activity e.g. some python activities have C libraries, using Services, activity developer should not bundle all binaries that sugar supports but provide binaries that he can build and let Services build C libraries from sources on user side in the rest of cases
+
* dependencies that are specific to particular activity e.g. some python activities have C libraries, using Services, activity developer should not bundle all binaries that sugar supports but provide links to binaries that he managed to build and let Services build C libraries from sources on user side in the rest of cases
    
To create new service developper needs to [[Activity Team/Documentation/Services/Service Developers HOWTO|create and share]] proper feed file which url could be used in activity developers [[Activity Team/Documentation/Services/Activity Developers HOWTO|feed files]].
 
To create new service developper needs to [[Activity Team/Documentation/Services/Service Developers HOWTO|create and share]] proper feed file which url could be used in activity developers [[Activity Team/Documentation/Services/Activity Developers HOWTO|feed files]].

Navigation menu