Difference between revisions of "Activity Team/Obsolete/Services Gui"
| Line 53: | Line 53: | ||
== Sources == | == Sources == | ||
| − | * [http://git.sugarlabs.org/projects/ | + | * [http://git.sugarlabs.org/projects/polyol] |
Revision as of 18:37, 2 June 2010
Summary
A set of first level GUI widgets to simplify process of activity creation.
This library is a part of Polyol group.
Contacts
Current status
| Branch [1] | Sugar range | Support status/Notes |
|---|---|---|
| 0 | 0.82 - 0.86 |
Detailed Description
It is a graphics part of sugar-toolkit project.
Service is intended to be glucose agnostic as much as possible by design i.e. service doesn't not include wrappers for sugar services(like sugar-toolkit does), contains as less as possible glucose depended code and use Shell service in other cases. Service is designed to support mostly GUI aspects of activity development process.
Code of this service is written in Vala and will contain bindings for scripting languages.
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