Move child API into GooCanvasContainer
@murrayc
Submitted by Murray Cumming Link to original bug (#556145)
Description
I think I've had a conversation about this on a mailing list, but I can't find it now, and I don't remember a good answer. Sorry if I'm wrong.
I think the child API (get_child(), etc) should be moved into the GooCanvasContainer, instead of the GooCanvasItem, because that obviously makes more sense. Openismus is likely to provide a patch for that.
Version: svn trunk