https://wiki.sugarlabs.org/api.php?action=feedcontributions&user=66.92.74.189&feedformat=atomSugar Labs - User contributions [en]2024-03-19T10:37:55ZUser contributionsMediaWiki 1.35.2https://wiki.sugarlabs.org/index.php?title=Supported_systems/Technical_considerations&diff=6431Supported systems/Technical considerations2008-06-20T02:19:13Z<p>66.92.74.189: /* Integration */ minor edit</p>
<hr />
<div><noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude><br />
{{Stub}}<br />
There are a number of technical considerations for providing Sugar support.<br />
<br />
==Integration==<br />
<br />
Sugar is designed to be started as a desktop option<br />
alongside Gnome and KDE rather than a plain "start menu"<br />
application. This means that we should consider a "switch<br />
desktop" function if it is a requirement to ship multiple environments.<br />
<br />
==Applications==<br />
<br />
In order to provide a consistent environment,<br />
Sugar activities need to implement a number of custom APIs to<br />
access documents and perform collaborative work over the<br />
network. There is some degree of interoperability with<br />
ordinary GNU/Linux applications (which needs improvement),<br />
but "sugarizing" software is really the only way to provide<br />
a nice user experience for little children. This doesn't<br />
imply duplicating all code: our Browse activity is really<br />
a thin shell around Firefox's engine.<br />
<br />
==Packaging==<br />
<br />
At this time, we have alpha-quality packages<br />
for Fedora, Debian and Ubuntu. Seamless integration would<br />
require additional packaging work, especially for the<br />
networking features. Packaging Sugar for other distributions would be<br />
done in collaboration; appropriate contacts within those communities would be necessary.<br />
<br />
==Software stacks==<br />
<br />
Sugar is based on quite a different set<br />
of components than the native PC desktop. Most code is<br />
written in Python and uses Cairo and GTK as its UI library.<br />
However, we also have a few activities written in C++,<br />
Small Talk and even C#, using disparate software stacks.<br />
If you are already supporting GTK based applications, <br />
the footprint of Sugar should be reasonably small.<br />
<br />
==Vendor customization==<br />
<br />
Sugar is moving to become an upstream<br />
project with respect to hardware and software distributors.<br />
We are glad to accept vendor-specific contributions back in<br />
our codebase, subject to peer review and a general usefulness<br />
criteria.<br />
<br />
==Engineering support==<br />
<br />
We are aware that Sugar still requires<br />
much more engineering work to polish the user interface,<br />
stabilize the codebase, and complete missing features. Since<br />
we started the Sugar Labs, we have already<br />
attracted fresh volunteers. But we'd appreciate hardware<br />
vendors (and others) assigning resources to work with us and make things happen<br />
faster.<br />
<br />
==Community involvement==<br />
<br />
We are in contact with several government<br />
organizations and grassroots groups which adopt laptops for<br />
primary education. They might want to run pilots using a<br />
variety of hardware in their respective countries. We are happy to assist<br />
in this process.<br />
<br />
==Content==<br />
<br />
We are also looking for localized open content. Industry partners<br />
might be able to help here.<br />
<br />
==Design proposals==<br />
<br />
We'd appreciate feedback and marketing input<br />
from hardware manufacturers (and others) to enhance our environment.</div>66.92.74.189