Changes

no edit summary
Line 2: Line 2:  
[[Category:Activity Team]]
 
[[Category:Activity Team]]
 
</noinclude>
 
</noinclude>
 +
 +
== Summary ==
 +
 +
Provides transparent for users and convenient for activity developers, method to support various activity dependencies.
 +
 +
== Work flows ==
 +
 +
How it looks like for:
 +
 +
=== Users ===
 +
 +
In case of pure 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 for startup dialog for activities that have pending/not-yet-downloaded/out-dated activity dependencies.
 +
 +
=== Activity developers ===
 +
 +
=== Service developers ===
    
== Detailed Description ==
 
== Detailed Description ==
Line 17: Line 33:  
Technically, service could be a part of glucose(or some of its releases) but from activity POV it doesn't make much sense, if activity requires some service, [[Activity_Team/Services/Saccharin|Saccharin]] will do nothing if requested service/version is a part of installed glucose or install proper service(via 0install). Various activities on the same system could use various versions of the same service, in that case [[Activity_Team/Services/Saccharin|Saccharin]](via 0install) will just provide proper version to particular activity.
 
Technically, service could be a part of glucose(or some of its releases) but from activity POV it doesn't make much sense, if activity requires some service, [[Activity_Team/Services/Saccharin|Saccharin]] will do nothing if requested service/version is a part of installed glucose or install proper service(via 0install). Various activities on the same system could use various versions of the same service, in that case [[Activity_Team/Services/Saccharin|Saccharin]](via 0install) will just provide proper version to particular activity.
   −
== Versioning scheme ==
+
=== Versioning scheme ===
    
Each service has API changes based versioning scheme
 
Each service has API changes based versioning scheme