Difference between revisions of "Activity Team/Obsolete/Services Gui"
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | {{Obsolete | corresponding project was never created}} | ||
+ | |||
<noinclude>{{GoogleTrans-en}}{{TOCright}} | <noinclude>{{GoogleTrans-en}}{{TOCright}} | ||
[[Category:Activity Team]] | [[Category:Activity Team]] | ||
Line 53: | Line 55: | ||
== Sources == | == Sources == | ||
− | * [http://git.sugarlabs.org/projects/ | + | * [http://git.sugarlabs.org/projects/polyol] |
Latest revision as of 16:43, 25 November 2010
SummaryA set of first level GUI widgets to simplify process of activity creation. This library is a part of Polyol group. ContactsCurrent status
Detailed DescriptionIt 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. DependenciesWhat 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? DocumentationIs 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 TestActivity Team/Obsolete/Services Gui/Testing Comments and DiscussionSources |