Changes

Jump to navigation Jump to search
m
no edit summary
Line 39: Line 39:  
=== GNU/Linux distributions ===
 
=== GNU/Linux distributions ===
   −
The [[0.86/Platform_Components|Sugar Platform]] cannot grow endlessly e.g. installing sugar from packages should not fetch a half of all available packages including several UI toolkits, several programming languages etc., so components like Qt or OO4Kids are (at least at present) out of Sugar Platform list. But with Sugar Services, activities can still use such dependencies by installing them from native packaging systems by demand and without bundling binaries.
+
The [[0.86/Platform_Components|Sugar Platform]] cannot grow endlessly e.g. installing sugar from packages should not fetch a half of all available packages including several UI toolkits, several programming languages etc., so components like Qt or Ruby are (at least at present) out of Sugar Platform list. But with Sugar Services, activities can still use such dependencies by installing them from native packaging systems by demand and without bundling binaries.
    
See [[Documentation_Team/Services/Native_packages_usage|Native packages usage]] to know how to utilize native packages in your activity or service.
 
See [[Documentation_Team/Services/Native_packages_usage|Native packages usage]] to know how to utilize native packages in your activity or service.
Line 54: Line 54:  
So, developers use a set of services that have their own [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|API changes based]] schedules. Glucose [[Activity Team/Services/Glucose|could be]] [[Documentation Team/Services/Native packages usage|wrapped]] to regular service(s) with proper [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|versioning scheme]] as well e.g. if glucose's activity API wasn't backwards compatibility broken since 0.82(glucose-0.x service) all activities that requires ''glucose 0'' will be launched but instead of launching activities with requirements ''glucose 1'', user will be warned about outdated sugar environment.
 
So, developers use a set of services that have their own [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|API changes based]] schedules. Glucose [[Activity Team/Services/Glucose|could be]] [[Documentation Team/Services/Native packages usage|wrapped]] to regular service(s) with proper [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|versioning scheme]] as well e.g. if glucose's activity API wasn't backwards compatibility broken since 0.82(glucose-0.x service) all activities that requires ''glucose 0'' will be launched but instead of launching activities with requirements ''glucose 1'', user will be warned about outdated sugar environment.
   −
The corner stone of Sugar Services proposal is [[Activity_Team/Services/Saccharin|Saccharin]] library. This library provides installing/upgrading (via 0install) mechanism for services. The rest of services is just variety of libraries/applications/native-packages. Saccharin could be a part of glucose (some of its releases) or bundled to .xo otherwise.
+
The corner stone of Sugar Services proposal is [[Activity_Team/Services/Saccharin|Saccharin]] service. This service provides installing/upgrading (via 0install) mechanism for services. The rest of services is just variety of libraries/applications/native-packages. Saccharin could be a part of glucose (some of its releases) or bundled to .xo otherwise.
    
== FAQ ==
 
== FAQ ==

Navigation menu