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 and(if activity targeted to sugars w/o [[Features/Zero_Install_integration|Zero Install integration]]) pure python library to initial launch of Services infrastructure. 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 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.

=== Service developers ===

=== Service developers ===