UVF exception: 0.4 to 0.6
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
goocanvas (Ubuntu) |
Fix Released
|
Undecided
|
Sebastien Bacher |
Bug Description
There is a new 0.6 version available:
GooCanvas 0.6 (Feb 17 2007)
=============
o Major rewrite to make the model optional, so people can choose to have
either a simple canvas or a model/view canvas. The standard items can be
used in either scenario.
o Added support for cascading style properties (things like fill color, stroke
width, font etc.). Properties use a GQuark for a unique identifier, and a
GValue for the property value, so they are very flexible.
o Added GooCanvasTable item to layout child items.
o Made it much easier to create new items, by subclassing GooCanvasItemSimple
which handles most of the work. See demo/demo-item.c for a simple item.
o Added support for different units - pixels, points, inches or millimeters,
and allow setting of vertical and horizontal resolution (dpi).
o Added workaround for cairo's 16-bit limit, to support large canvases.
o Added demo/scalabilit
It takes a few seconds to create all the items, but once created it seems
to work fast enough.
o Improved the animation code, supporting relative or absolute values for
the x, y, scale and rotation.
o Added "clip-path" and "clip-fill-rule" to specify a clip path for an item.
The package is used only by python-goocanvas so updating should be fine (and would allow to update python-goocanvas which would make upstream happy problably)
I'm fine with updating although it's a complete rewrite because of the reasoning given on IRC:
<seb128> dholbach: the update is non trivial but nothing uses it basically, and pygoocanvas upstream uses launchpad for bugs and would probably be happy to have 0.6 for feisty
<seb128> and some program start using pygoocanvas and having it update would be nice for people who want to build them, etc