according to the list you've provided goocanvas and ccc are only candidates for being the Gtk+ canvas shouldn't one of them be taken for long term support projects? On Wed, Apr 9, 2008 at 9:51 PM, Emmanuele Bassi <ebassi@xxxxxxxxx> wrote: > > On Wed, 2008-04-09 at 19:06 +0200, Giovanni Funchal wrote: > > Hi, > > > > I've asked about a gtk canvas sometime ago and someone pointed me to > > goocanvas but it is still beta and I'm affraid of using it because it > > might disapear. Is there any recent progress? Will gtk ever have a > > standard canvas? > > as I said here: > > http://log.emmanuelebassi.net/archives/2008/03/berlin3/ > > the choice is between either to get one of the current canvases and give > it "the gtk+ seal of approval" or completely reimplement it inside gtk. > > there are various canvases available: > > http://live.gnome.org/ProjectRidley/CanvasOverview > > each with its own strengths and disadvantages. if you plan on relying on > hardware acceleration, and you don't plan on embedding gtk+ widgets (not > yet, at least), the Clutter: > > http://www.clutter-project.org > > might be a good choice. > > if you're worried about a dependency might disappear you can import it > straight inside your project, by the way; it's a maintenance burden, but > if you are actively maintaining a project then you shouldn't worry about > dependencies disappearing. > > ciao, > Emmanuele. > > -- > Emmanuele Bassi, > W: http://www.emmanuelebassi.net > B: http://log.emmanuelebassi.net > > > > _______________________________________________ > gtk-list mailing list > gtk-list@xxxxxxxxx > http://mail.gnome.org/mailman/listinfo/gtk-list > _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
