Difference between revisions of "Activity Team/Obsolete/Services Toolkit"
m |
|||
| Line 5: | Line 5: | ||
== Summary == | == Summary == | ||
| − | Everything | + | Everything that developers need to start developing native sugar activities. Library depends on all other Polyol components and contains glue level code that simplify creating sugar activities from scratch. This library (and all its dependencies) is an analog of the python-based sugar-toolkit library. |
| − | Bindings for this library (in contrast with bindings for other Polyol components) could contain not only wrappers for library itself, but also particular language specific code that makes process of creating sugar activities in this language more comfortable. | + | Bindings for this library (in contrast with bindings for other Polyol components) could contain not only wrappers for the library itself, but also particular language-specific code that makes the process of creating sugar activities in this language more comfortable. |
This library is a part of [[Activity_Team/Polyol|Polyol group]]. | This library is a part of [[Activity_Team/Polyol|Polyol group]]. | ||
| Line 19: | Line 19: | ||
''For regular services:'' | ''For regular services:'' | ||
| − | ''How many branches are stable for what Sugar Platforms, note that some activities could be stuck to particular stable branch, so do not delete your stable branches if they still work in declared sugar environments. See [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|Versioning guide]].'' | + | ''How many branches are stable for what Sugar Platforms, note that some activities could be stuck to a particular stable branch, so do not delete your stable branches if they still work in declared sugar environments. See [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|Versioning guide]].'' |
{| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | {| border=1 cellpadding=3 style="border: 1px solid white; border-collapse: collapse; background: #e3e4e5;" | ||
| Line 35: | Line 35: | ||
''For wrappers to native packages:'' | ''For wrappers to native packages:'' | ||
| − | This service is a [[Documentation Team/Services/Native packages usage|wrapper]] for native package thus its versions are versions of accessible packages in current users' environment. | + | This service is a [[Documentation Team/Services/Native packages usage|wrapper]] for native package, thus its versions are versions of accessible packages in the current users' environment. |
== Detailed Description == | == Detailed Description == | ||
Revision as of 09:27, 8 May 2010
Summary
Everything that developers need to start developing native sugar activities. Library depends on all other Polyol components and contains glue level code that simplify creating sugar activities from scratch. This library (and all its dependencies) is an analog of the python-based sugar-toolkit library.
Bindings for this library (in contrast with bindings for other Polyol components) could contain not only wrappers for the library itself, but also particular language-specific code that makes the process of creating sugar activities in this language more comfortable.
This library is a part of Polyol group.
Contacts
Current status
For regular services:
How many branches are stable for what Sugar Platforms, note that some activities could be stuck to a particular stable branch, so do not delete your stable branches if they still work in declared sugar environments. See Versioning guide.
| Branch [1] | Sugar Platforms | Support status/Notes |
|---|---|---|
| 0 | 0.82-1.00 | is comming |
For wrappers to native packages:
This service is a wrapper for native package, thus its versions are versions of accessible packages in the current users' environment.
Detailed Description
Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.
Dependencies
What other services or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does your service depend on completion of another service owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?
Documentation
Is there upstream documentation on this service, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.
If auto-documentation field is set in service.info file, API documentation will be generated on this page:
How To Test
Activity Team/Obsolete/Services Toolkit/Testing