132
edits
Changes
Supported systems/Technical considerations (view source)
Revision as of 00:06, 19 December 2016
, 00:06, 19 December 2016no edit summary
{{Stub}}
{{Outdated}}
<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>
{{Stub}}{{TOCright}}
There are a number of technical considerations for providing Sugar support.
There are a number of technical considerations for providing Sugar support.
==Integration==
==Integration==
Sugar is designed to be started as desktop option
Sugar is designed to be started as a desktop option
alongside Gnome and KDE rather than a plain "start menu"
alongside Gnome and KDE rather than a plain "start menu"
application. This means that we should consider a "switch
application. This means that we should consider a "switch
a thin shell around Firefox's engine.
a thin shell around Firefox's engine.
==Packaging==
==[[Packaging Team|Packaging]]==
At this time, we have alpha-quality packages
At this time, we have alpha-quality packages
require additional packaging work, especially for the
require additional packaging work, especially for the
networking features. Packaging Sugar for other distributions would be
networking features. Packaging Sugar for other distributions would be
done in collaboration; appropriate contacts within those communities would be necessary.
done in collaboration; see [[Packaging Team]], appropriate contacts within those communities are welcome to join.
==Software stacks==
==Software stacks==
We'd appreciate feedback and marketing input
We'd appreciate feedback and marketing input
from hardware manufacturers (and others) to enhance our environment.
from hardware manufacturers (and others) to enhance our environment.