HippoCanvas: Difference between revisions

From OLPC
Jump to navigation Jump to search
mNo edit summary
m (Added category link)
Line 30: Line 30:
* [http://mail.gnome.org/archives/gtk-devel-list/2006-August/msg00168.html A mailing list post] about HippoCanvas.
* [http://mail.gnome.org/archives/gtk-devel-list/2006-August/msg00168.html A mailing list post] about HippoCanvas.
* [http://www.gnome.org/~marco/hippo-canvas-0.2.6.tar.gz HippoCanvas source v. 0.2.6]
* [http://www.gnome.org/~marco/hippo-canvas-0.2.6.tar.gz HippoCanvas source v. 0.2.6]

[[Category:Sugar]]

Revision as of 22:47, 19 February 2007

This article is a stub. You can help the OLPC project by expanding it.

HippoCanvas is a generic user interface element that can draw Cairo graphics, respond to key and mouse events, and lay out other widgets. It is currently used to implement a number of Sugar's custom widgets (toolbars, rounded buttons, etc.) and to lay out the screen.

On the OLPC, HippoCanvas is a GTK widget and it can contain other GTK widgets, so the programmer can freely combine HippoCanvas and other widgets. While Sugar does not require that activities be written using HippoCanvas, those that do can look more visually consistent with other activities.

Rationale

HippoCanvas was originally designed to be a cross-platform UI layer built on top of other windowing systems. It is used in Sugar to work around deficiencies GTK's layout system. [1] HippoCanvas also makes it easier to prototype custom widgets, and its Python interface can be somewhat simpler than native GTK widgets.

Canvas object

CanvasItem object

CanvasBox object

CanvasWidget object

CanvasContext object

CanvasImage object

CanvasText object

CanvasLink object

Links