Re: [Goocanvas-devel] GooCanvas Roadmap
Status: Beta
Brought to you by:
dachaplin
From: Damon C. <da...@ka...> - 2007-03-02 14:53:01
|
On Wed, 2007-02-28 at 23:30 +0100, Gian Mario Tagliaretti wrote: > 2007/2/27, Damon Chaplin <da...@ka...>: > > > So now is the time for people to point out anything wrong with the > > current API, or anything very important that they think is missing. > > I think we should fix the gdk_cairo_create () problem, that's quite important. For people who don't know, the problem is that if we call gdk_cairo_create() before the canvas widget is realized we get a NULL cairo_t. So we can't do layout calculations and things like get_item_at(). And currently we just SEGV. I'm not really sure what the best thing to do is. We could create a temporary image surface and create a cairo_t from that. I'm just a bit concerned that the resulting layout may be slightly different, or that it may cause other problems. > I would like to point out again that it's probably better to avoid > having a cairo_t as parameter in a few functions, that can be done > internally with goo_canvas_create_cairo() which can (should?) be made > public. As we discussed privately, nearly all of those functions are for implementing new canvas items, and not for applications to call. I'll document that better. But you are right that goo_canvas_create_cairo() should be public. > > (Though note that I don't really want to spend much more time on 1.0 > > myself.) > > Are you not going to enhance the code with new API and other > interesting stuff that will most likely come up from the applications? > you will only do bug fixes? I wouldn't mind adding the occasional new function or incorporating patches from others. But I don't want to spend weeks or months on it as I have in the past. (One thing I might look at is a port of GtkTextView. Though that looks pretty hard to do.) Damon |