Platform Team/Polyol - Revision history

Alsroot at 13:16, 2 July 2012

2012-07-02T13:16:47Z

← Older revision		Revision as of 09:16, 2 July 2012
Line 77:		Line 77:
	* Python binding libraries cannot be linked with C libraries from sugar-toolkit.		* Python binding libraries cannot be linked with C libraries from sugar-toolkit.
	*: Polyol names contain the {{Code\|sugar}} prefix to reuse sugar-artwork as-is.		*: Polyol names contain the {{Code\|sugar}} prefix to reuse sugar-artwork as-is.

			== Sources ==

			* [http://git.sugarlabs.org/sdk/polyol Gitorious project].

Alsroot: /* Build from sources */

2012-03-11T17:28:46Z

Build from sources

← Older revision		Revision as of 13:28, 11 March 2012
Line 57:		Line 57:
	* [http://live.gnome.org/Libgee gee] >= 0.5		* [http://live.gnome.org/Libgee gee] >= 0.5

	Download last [~~http~~://~~download~~.sugarlabs.org/~~sources/external~~/polyol/ tarball].		Download last [https://packages.sugarlabs.org/package/files?package=polyol&project=sdk tarball].

	Build it:		Build it:

Alsroot: /* Pitfalls */

2012-03-11T08:49:56Z

Pitfalls

← Older revision		Revision as of 04:49, 11 March 2012
Line 75:		Line 75:
	== Pitfalls ==		== Pitfalls ==

	~~Currently,~~ Python binding ~~is basing on pygtk and~~ cannot be ~~linking~~ with C libraries from sugar-toolkit.		* Python binding libraries cannot be linked with C libraries from sugar-toolkit.
			*: Polyol names contain the {{Code\|sugar}} prefix to reuse sugar-artwork as-is.

Alsroot at 08:47, 11 March 2012

2012-03-11T08:47:57Z

← Older revision		Revision as of 04:47, 11 March 2012
Line 1:		Line 1:
	~~<noinclude>~~
	~~{{TOCright}}~~
	~~</noinclude>~~

	== Summary ==		== Summary ==

	~~Intermediate level [http://library.gnome.org/devel/gobject/stable/ GObject] based~~ libraries ~~group.~~		A set of C libraries to help with coding non-Python Sugar activities.

	~~See [[Platform Team/Scalable development model\|Scalable development model]]~~ to ~~learn more about the initial intentions of Polyol~~.

	== Concepts ==		== Concepts ==
Line 13:		Line 7:
	[[File:polyol.png\|500px]]		[[File:polyol.png\|500px]]

	~~====~~ Glucose processes ~~====~~		* '''Glucose processes'''
			*: Sugar core processes and dbus services.
	Sugar core processes and dbus services.		* '''DBus'''
			*: All communication between glucose level and activity process goes via dbus.
	~~====~~ DBus ~~====~~		* '''Polyol'''
			*: Intermediate level libraries:
	All communication between glucose level and activity process goes via dbus.		: Glucose compatibility libraries (ds, shell, collab) will support several (popular among sugar deployments) glucose releases
			: Other libraries are not tied to glucose directly
	~~====~~ Polyol ~~group ====~~		*: Key features:
			: All libraries are written in Vala, i.e., based on pure GObjects, and could be used by non-python-based activities.
	Intermediate level libraries:		: Activities (mostly not native sugar activities) could use only one library e.g. activity could use only ''ds'' library thus do not fetch additional dependencies like gtk+ (via ''gui'').
	* Glucose compatibility libraries (ds, shell, collab) will support several (popular among sugar deployments) glucose releases		* '''Activity process'''
	* Other libraries are not tied to glucose directly		*: Regular activities would not use glucose directly, rather they would only access glucose through the Polyol level.

	Key features ~~of this level~~:
	* All libraries are written in Vala, i.e., based on pure GObjects, and could be used by non-python-based activities.
	* ~~Each Polyol component has its own release schedule, i.e., there are no Polyol official releases (it looks like in Gentoo).~~
	* Activities could use these libraries on separate basis e.g. activity could use recent ''gui'' (to get access to last UI widgets) and old version of ''ds'' (because activity was coded against this particular version and new version has backward compatibility breakage in API).
	* Activities (mostly not native sugar activities) could use only one library e.g. activity could use only ''ds'' library thus do not fetch additional dependencies like gtk+ (via ''gui'').

	~~====~~ Activity process ~~====~~

	Regular activities would not use glucose directly, rather they would only access glucose through the Polyol level.<br>There is no need to code special activities, the sugar-toolkit API will be preserved, and activity developers will benefit because Polyol will support the recent sugar-toolkit API, e.g., they could use the new toolbars design even on Sugar 0.82.

	== Components ==		== Components ==

	All libraries are C based and could contain bindings for various programming languages. Libraries use the same [http://git.sugarlabs.org/projects/polyol sources tree] but each component has its own 0install interface and versions (there will be a way to use entirely polyol as single package e.g. for GNU/Linux distribution needs since all benefits of separation vanishes in that case).		All libraries are C based and could contain bindings for various programming languages. Libraries use the same [http://git.sugarlabs.org/projects/polyol sources tree].

	==== env ====		==== env ====
Line 67:		Line 51:
	Bindings for this library (in contrast with bindings for other Polyol components) could contain not only wrappers for library itself, but also particular language specific code that makes process of creating sugar activities in this language more comfortable.		Bindings for this library (in contrast with bindings for other Polyol components) could contain not only wrappers for library itself, but also particular language specific code that makes process of creating sugar activities in this language more comfortable.

	== Build ~~for non-0install usage~~ ==		== Build from sources ==

	Install required dependencies		Install required dependencies
Line 88:		Line 72:

	For each component, Polyol will install ''.pc'' file. So, after installing polyol, be sure that ''pkg-config'' will find ''.pc'' files e.g. setup ''PKG_CONFIG_PATH'' variable before using polyol.		For each component, Polyol will install ''.pc'' file. So, after installing polyol, be sure that ''pkg-config'' will find ''.pc'' files e.g. setup ''PKG_CONFIG_PATH'' variable before using polyol.

			== Pitfalls ==

			Currently, Python binding is basing on pygtk and cannot be linking with C libraries from sugar-toolkit.

Alsroot: /* Build for non-0install usage */

2011-10-19T12:37:43Z

Build for non-0install usage

← Older revision		Revision as of 08:37, 19 October 2011
Line 73:		Line 73:
	* [http://live.gnome.org/Libgee gee] >= 0.5		* [http://live.gnome.org/Libgee gee] >= 0.5

	Download last [http://download.sugarlabs.org/~~services~~/polyol/ tarball].		Download last [http://download.sugarlabs.org/sources/external/polyol/ tarball].

	Build it:		Build it:

Alsroot at 21:43, 25 November 2010

2010-11-25T21:43:12Z

← Older revision		Revision as of 17:43, 25 November 2010
Line 7:		Line 7:
	Intermediate level [http://library.gnome.org/devel/gobject/stable/ GObject] based libraries group.		Intermediate level [http://library.gnome.org/devel/gobject/stable/ GObject] based libraries group.

	See [[~~Documentation~~ Team~~/Services~~/Scalable development model\|Scalable development model]] to learn more about the initial intentions of Polyol.		See [[Platform Team/Scalable development model\|Scalable development model]] to learn more about the initial intentions of Polyol.

	== Concepts ==		== Concepts ==
Line 41:		Line 41:
	All libraries are C based and could contain bindings for various programming languages. Libraries use the same [http://git.sugarlabs.org/projects/polyol sources tree] but each component has its own 0install interface and versions (there will be a way to use entirely polyol as single package e.g. for GNU/Linux distribution needs since all benefits of separation vanishes in that case).		All libraries are C based and could contain bindings for various programming languages. Libraries use the same [http://git.sugarlabs.org/projects/polyol sources tree] but each component has its own 0install interface and versions (there will be a way to use entirely polyol as single package e.g. for GNU/Linux distribution needs since all benefits of separation vanishes in that case).

	==== ~~[[Activity_Team/Services/Env\|~~env]] ====		==== env ====

	Access to various sugar environment settings.		Access to various sugar environment settings.

	==== ~~[[Activity_Team/Services/Shell\|~~shell]] ====		==== shell ====

	Compatibility level library to sugar-shell.		Compatibility level library to sugar-shell.

	==== ~~[[Activity_Team/Services/Collab\|~~collab]] ====		==== collab ====

	High level client API for what activity developers might need to code collab activities.		High level client API for what activity developers might need to code collab activities.

	==== ~~[[Activity_Team/Services/Ds\|~~ds]] ====		==== ds ====

	High level client API to sugar-datastore.		High level client API to sugar-datastore.

	==== ~~[[Activity_Team/Services/Gui\|~~gui]] ====		==== gui ====

	A set of first level GUI widgets to simplify process of activity creation.		A set of first level GUI widgets to simplify process of activity creation.

	==== ~~[[Activity_Team/Services/Toolkit\|~~toolkit]] ====		==== toolkit ====

	Everything what developers need to start developing native sugar activities. Library depends on all other Polyol components and contains glue level code that simplify creating sugar activities from scratch. This library (and all its dependencies) is an analog of python based sugar-toolkit library.		Everything what developers need to start developing native sugar activities. Library depends on all other Polyol components and contains glue level code that simplify creating sugar activities from scratch. This library (and all its dependencies) is an analog of python based sugar-toolkit library.

Alsroot: moved Activity Team/Polyol to Platform Team/Polyol

2010-11-25T21:32:39Z

moved Activity Team/Polyol to Platform Team/Polyol

← Older revision	Revision as of 17:32, 25 November 2010
(No difference)

Alsroot: /* Build for non-0install usage */

2010-06-29T03:49:24Z

Build for non-0install usage

← Older revision		Revision as of 23:49, 28 June 2010
Line 77:		Line 77:
	Build it:		Build it:

	cd <sources-root> && cmake [-D<var-name>=<var-value>] . && make && make install		cd <sources-root> && cmake [<nowiki>-D<var-name>=<var-value></nowiki>] . && make && make install

	Useful cmake variables:		Useful cmake variables:
Line 86:		Line 86:
	* ''COMPONENTS'', '';'' separated list of components to build, default is all components		* ''COMPONENTS'', '';'' separated list of components to build, default is all components
	* ''BINDINGS'', '';'' separated list of bindings to build, default is all bindings		* ''BINDINGS'', '';'' separated list of bindings to build, default is all bindings

			For each component, Polyol will install ''.pc'' file. So, after installing polyol, be sure that ''pkg-config'' will find ''.pc'' files e.g. setup ''PKG_CONFIG_PATH'' variable before using polyol.

Alsroot: /* Build for non-0install usage */

2010-06-29T03:43:58Z

Build for non-0install usage

← Older revision		Revision as of 23:43, 28 June 2010
Line 70:		Line 70:

	Install required dependencies		Install required dependencies
	* [http://cmake.org/ cmake]		* [http://cmake.org/ cmake] >= 2.6
	* [http://live.gnome.org/Libgee gee] > 0.5		* [http://live.gnome.org/Libgee gee] >= 0.5

	Download last [http://download.sugarlabs.org/services/polyol/ tarball].		Download last [http://download.sugarlabs.org/services/polyol/ tarball].
Line 77:		Line 77:
	Build it:		Build it:

	cmake <~~path~~-to-~~sources-root~~> && make && make install		cd <sources-root> && cmake [-D<var-name>=<var-value>] . && make && make install

			Useful cmake variables:
			* ''MAINTAINER_MODE'', set to ''TRUE'' to recreate generated files, default is ''FALSE''
			* ''CMAKE_C_FLAGS''
			* ''CMAKE_INSTALL_PREFIX'', default is ''/usr/local''
			* ''PYTHON_SITEDIR'', path within ''CMAKE_INSTALL_PREFIX'' to install python libraries, default is ''lib''
			* ''COMPONENTS'', '';'' separated list of components to build, default is all components
			* ''BINDINGS'', '';'' separated list of bindings to build, default is all bindings

Alsroot: /* Build for non-0install usage */

2010-06-25T02:06:19Z

Build for non-0install usage

← Older revision		Revision as of 22:06, 24 June 2010
Line 77:		Line 77:
	Build it:		Build it:

	cmake . && make && make install		cmake <path-to-sources-root> && make && make install