10,579
edits
Changes
Platform Team/Package Management System (view source)
Revision as of 08:59, 20 December 2009
, 08:59, 20 December 2009→Work flows
== Work flows ==
== Work flows ==
Services looks different depending upon your point of view:
=== Users ===
=== Users ===
In case of poor internet connection(and implemented [[Features/Zero_Install_integration|Zero Install integration]] feature), user can switch to offline mode and won't encounter any changes in regular workflow. Switching to online mode brings additional progress bar to launch dialog for activities that have pending/not-yet-downloaded/out-dated activity dependencies.
In case of poor internet connection (and implemented [[Features/Zero_Install_integration|Zero Install integration]] feature), user can switch to offline mode and won't encounter any changes in regular workflow. Switching to online mode brings additional progress bar to launch dialog for activities that have pending/not-yet-downloaded/out-dated activity dependencies.
=== Activity developers ===
=== Activity developers ===
Sugar Services makes sense only for activities that have non Sugar Platform dependencies or support more then one Sucrose release cycles.
Sugar Services makes sense only for activities that have non-Sugar Platform dependencies or support more then one Sucrose release cycle.
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 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.
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 in activities ===
=== Use of non-Sugar Platform dependencies in activities ===
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.
The Sugar Platform cannot grow endlessly and components like Qt or OO4Kids are (at present) out of Sugar Platform list. But activities can still use such dependencies by installing them from native packaging systems without bundling 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 Guide|create and share]] proper feed which could be used [[Activity Team/Documentation/Services/Activity Developers Guide|by activity developers]].
To create new service, developer 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 ===
The whole Sugar Services feature is nothing but just a sugarized UI around [http://0install.net/ 0install] e.g. feed files that are beeing used in activity bundles are just regular 0install local feeds, so could be used to install/upgrade any software(including sugar core components).
The whole Sugar Services feature is nothing but just a Sugarized UI around [http://0install.net/ 0install] e.g. feed files that are being used in activity bundles are just regular 0install local feeds, so could be used to install/upgrade any software(including sugar core components).
== Detailed Description ==
== Detailed Description ==