Difference between revisions of "Activity Team/Obsolete/Services Gui"
| Line 25: | Line 25: | ||
== Detailed Description == | == Detailed Description == | ||
| − | + | Service which assimilates various sugar-toolkit releases changes e.g. let activity developers use new toolbars even in 0.82 environment and do not use many ''ifs'' in code. | |
== Dependencies == | == Dependencies == | ||
Revision as of 15:24, 15 December 2009
Summary
A sugar-toolkit service wrapper.
Contacts
Current status
| Major version/0install link | Notes/Status |
|---|---|
| 0 | is comming |
Detailed Description
Service which assimilates various sugar-toolkit releases changes e.g. let activity developers use new toolbars even in 0.82 environment and do not use many ifs in code.
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.
How To Test
Activity Team/Obsolete/Services Gui/Testing