Changes

For such activities development focus is shifting from Sucrose to API of services they are using. More over activity could be stuck to particular service API version(of course if service developers still support this branch) and Sugar Services will support several branches for the same service simultaneously.

For such activities development focus is shifting from Sucrose to API of services they are using. More over activity could be stuck to particular service API version(of course if service developers still support this branch) and Sugar Services will support several branches for the same service simultaneously.

To utilize Services benefits, activity developer just need to [[Activity Team/Documentation/Services/Activity Developers HOWTO|mention all services(or pure 0install feeds)]] that activity is using. Services infrastructure will provide specified services(and specified versions) for activity and will export environment variables, like LD_LIBRARY_PATH or PYTHONPATH, to activity session, so activity developer shouldn't adapt code to Services.

To utilize Services benefits, activity developer just need to [[Activity Team/Documentation/Services/Activity Developers Guide|mention all services(or pure 0install feeds)]] that activity is using. Services infrastructure will provide specified services(and specified versions) for activity and will export environment variables, like LD_LIBRARY_PATH or PYTHONPATH, to activity session, so activity developer shouldn't adapt code to Services.

=== Use non Sugar Platform dependencies ===

=== Use non Sugar Platform dependencies ===

Sugar Platform could not grow endlessly and components like Qt or OO4Kids will be out of Sugar Platform list. But activities can still use such dependencies by installing them from native packaging systems and do not bundle binaries. See [[Activity_Team/Documentation/Services/Non_Sugar_Platform_Dependencies_HOWTO|Non Sugar Platform Dependencies HOWTO]] to know how to use 0install features.

Sugar Platform could not grow endlessly and components like Qt or OO4Kids will be out of Sugar Platform list. But activities can still use such dependencies by installing them from native packaging systems and do not bundle binaries. See [[Activity_Team/Documentation/Services/Non_Sugar_Platform_Dependencies_Guide|Non Sugar Platform Dependencies Guide]] to know how to use 0install features.

=== Service developers ===

=== Service developers ===

* 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

* 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 which could be used [[Activity Team/Documentation/Services/Activity Developers HOWTO|by activity developers]].

To create new service, developper needs to [[Activity Team/Documentation/Services/Service Developers Guide|create and share]] proper feed which could be used [[Activity Team/Documentation/Services/Activity Developers Guide|by activity developers]].

=== Geeks ===

=== Geeks ===