On Sat, 2009-03-14 at 13:20 -0700, Krzysztof Kosiński wrote:
Using GIO could still make some issues easier to solve and understand for others, since it operates on raw byte streams and doesn't even pretend to do formatted IO. The distinction between characters and bytes is pretty clear. In essence we could adapt Writers to GIO streams. They would probably be faster since our current streams write only one per function call, while GIO can write any number.
Again, none of that is specific to GIO.
If we want, we can convert things to use more than one per function call. That's very easy to do, and something I was looking at addressing this weekend even.
My real motivation though is just to push some code out of Inkscape. If we want to integrate properly with Gnome we have to use GIO, so we might use it for our other stream needs as well.
Ah, here we have a main point.
A *KEY* issue is to *NOT* be dependent on GNOME. So where we can do things in a way that works nice with GNOME, that is fine. However if it will cause problems for native Windows or Native OS X (which is actually close to being usable) we don't want to do it.
Remember, OS X and MS Windows need to stay first-class citizens for Inkscape support.
If GTK+ and glib do not have it, then we need to have it in Inkscape.
Oh, and remember. I'm not saying we can't go to GIO. I'm just saying that switching to GIO would not help with these specific problems... in fact it would probably complicate things somewhat.