Supported systems/Technical considerations - Revision history

KachachanC at 05:06, 19 December 2016

2016-12-19T05:06:07Z

← Older revision		Revision as of 01:06, 19 December 2016
Line 1:		Line 1:
			{{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>		<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}}		{{Stub}}{{TOCright}}

FGrose at 17:07, 6 June 2009

2009-06-06T17:07:27Z

← Older revision		Revision as of 13:07, 6 June 2009
Line 22:		Line 22:
	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
Line 28:		Line 28:
	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==

FGrose at 19:14, 26 March 2009

2009-03-26T19:14:25Z

← Older revision		Revision as of 15:14, 26 March 2009
Line 1:		Line 1:
	<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>		<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}}		{{Stub}}{{TOCright}}
	There are a number of technical considerations for providing Sugar support.		There are a number of technical considerations for providing Sugar support.

66.92.74.189: /* Integration */ minor edit

2008-06-20T02:19:13Z

Integration: minor edit

← Older revision		Revision as of 22:19, 19 June 2008
Line 5:		Line 5:
	==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

Cjl at 06:06, 12 June 2008

2008-06-12T06:06:21Z

← Older revision		Revision as of 02:06, 12 June 2008
Line 1:		Line 1:
			<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}}		{{Stub}}
	There are a number of technical considerations for providing Sugar support.		There are a number of technical considerations for providing Sugar support.

Dfarning-bot: Robot: Removing from Category:Developer

2008-06-07T18:23:33Z

Robot: Removing from Category:Developer

← Older revision		Revision as of 14:23, 7 June 2008
Line 74:		Line 74:
	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.

	~~[[Category:developer]]~~

Dfarning: Consistently using Sugar Labs across the wiki

2008-05-28T20:53:16Z

Consistently using Sugar Labs across the wiki

← Older revision		Revision as of 16:53, 28 May 2008
Line 52:		Line 52:
	much more engineering work to polish the user interface,		much more engineering work to polish the user interface,
	stabilize the codebase, and complete missing features. Since		stabilize the codebase, and complete missing features. Since
	~~when~~ we started the ~~Sugarlabs project~~, we have already		we started the Sugar Labs, we have already
	attracted ~~a few~~ fresh volunteers. But we'd appreciate hardware		attracted fresh volunteers. But we'd appreciate hardware
	vendors (and others) assigning resources to work with us and make things happen		vendors (and others) assigning resources to work with us and make things happen
	faster.		faster.

Marcopg at 23:13, 27 May 2008

2008-05-27T23:13:41Z

← Older revision		Revision as of 19:13, 27 May 2008
Line 2:		Line 2:
	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 desktop option
Line 9:		Line 9:
	desktop" function if it is a requirement to ship multiple environments.		desktop" function if it is a requirement to ship multiple environments.

	==~~APPLICATIONS~~==		==Applications==

	In order to provide a consistent environment,		In order to provide a consistent environment,
Line 21:		Line 21:
	a thin shell around Firefox's engine.		a thin shell around Firefox's engine.

	==~~PACKAGING~~==		==Packaging==

	At this time, we have alpha-quality packages		At this time, we have alpha-quality packages
Line 29:		Line 29:
	done in collaboration; appropriate contacts within those communities would be necessary.		done in collaboration; appropriate contacts within those communities would be necessary.

	==~~SOFTWARE STACKS~~==		==Software stacks==

	Sugar is based on quite a different set		Sugar is based on quite a different set
Line 39:		Line 39:
	the footprint of Sugar should be reasonably small.		the footprint of Sugar should be reasonably small.

	==~~VENDOR CUSTOMIZATIONS~~==		==Vendor customization==

	Sugar is moving to become an upstream		Sugar is moving to become an upstream
Line 47:		Line 47:
	criteria.		criteria.

	==~~ENGINEERING SUPPORT~~==		==Engineering support==

	We are aware that Sugar still requires		We are aware that Sugar still requires
Line 57:		Line 57:
	faster.		faster.

	==~~COMMUNITY INVOLVEMENT~~==		==Community involvement==

	We are in contact with several government		We are in contact with several government
Line 65:		Line 65:
	in this process.		in this process.

	==~~CONTENT~~==		==Content==

	We are also looking for localized open content. Industry partners		We are also looking for localized open content. Industry partners
	might be able to help here.		might be able to help here.

	==~~DESIGN PROPOSALS~~==		==Design proposals==

	We'd appreciate feedback and marketing input		We'd appreciate feedback and marketing input

Walter at 23:09, 27 May 2008

2008-05-27T23:09:19Z

← Older revision		Revision as of 19:09, 27 May 2008
Line 1:		Line 1:
			{{Stub}}
	There are a number of technical considerations for providing Sugar support.		There are a number of technical considerations for providing Sugar support.

Walter: generalization of a Bernie memo to ASUS

2008-05-27T23:06:14Z

generalization of a Bernie memo to ASUS

New page

There are a number of technical considerations for providing Sugar support.

==INTEGRATION==

Sugar is designed to be started as desktop option
alongside Gnome and KDE rather than a plain "start menu"
application. This means that we should consider a "switch
desktop" function if it is a requirement to ship multiple environments.

==APPLICATIONS==

In order to provide a consistent environment,
Sugar activities need to implement a number of custom APIs to
access documents and perform collaborative work over the
network. There is some degree of interoperability with
ordinary GNU/Linux applications (which needs improvement),
but "sugarizing" software is really the only way to provide
a nice user experience for little children. This doesn't
imply duplicating all code: our Browse activity is really
a thin shell around Firefox's engine.

==PACKAGING==

At this time, we have alpha-quality packages
for Fedora, Debian and Ubuntu. Seamless integration would
require additional packaging work, especially for the
networking features. Packaging Sugar for other distributions would be
done in collaboration; appropriate contacts within those communities would be necessary.

==SOFTWARE STACKS==

Sugar is based on quite a different set
of components than the native PC desktop. Most code is
written in Python and uses Cairo and GTK as its UI library.
However, we also have a few activities written in C++,
Small Talk and even C#, using disparate software stacks.
If you are already supporting GTK based applications,
the footprint of Sugar should be reasonably small.

==VENDOR CUSTOMIZATIONS==

Sugar is moving to become an upstream
project with respect to hardware and software distributors.
We are glad to accept vendor-specific contributions back in
our codebase, subject to peer review and a general usefulness
criteria.

==ENGINEERING SUPPORT==

We are aware that Sugar still requires
much more engineering work to polish the user interface,
stabilize the codebase, and complete missing features. Since
when we started the Sugarlabs project, we have already
attracted a few fresh volunteers. But we'd appreciate hardware
vendors (and others) assigning resources to work with us and make things happen
faster.

==COMMUNITY INVOLVEMENT==

We are in contact with several government
organizations and grassroots groups which adopt laptops for
primary education. They might want to run pilots using a
variety of hardware in their respective countries. We are happy to assist
in this process.

==CONTENT==

We are also looking for localized open content. Industry partners
might be able to help here.

==DESIGN PROPOSALS==

We'd appreciate feedback and marketing input
from hardware manufacturers (and others) to enhance our environment.

[[Category:developer]]