Difference between revisions of "Activity Team/Obsolete/Services Gui"
| Line 19: | Line 19: | ||
! Notes/Status | ! Notes/Status | ||
|- | |- | ||
| − | | | + | | [http://download.sugarlabs.org/services/toolkit/feed.xml 0] |
| − | | | + | | 0.82 - 0.86 |
| − | | | + | | |
|- | |- | ||
|} | |} | ||
Revision as of 08:46, 19 December 2009
Summary
A set of first level widgets and misc components to simplify process of activity creation.
Contacts
Current status
| Major[1] version/0install link | Sugar range | Notes/Status |
|---|---|---|
| 0 | 0.82 - 0.86 |
Detailed Description
Service is intended to be glucose agnostic as much as possible, not by strong intention of its developers but by design i.e. service doesn't not include wrappers for sugar services(like sugar-toolkit does) and contains as less as possible glucose depended code. Service is designed to support mostly GUI aspects of activity development process.
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