On Tue, 2008-03-11 at 04:22 -0700, Krzysztof Kosiński wrote:
I had a look at the stream classes used to output SVG to flies and memory while working on fixing the clipboard bug. The functionality of those classes is largely the same as std::iostream and the related class hierarchy. I think Inkscape could switch from its own stream implementation to the standard library streams. This would, among other things, reduce the complexity of the application and the size of the codebase.
Is there some good reason Inkscape uses its own stream implementation instead of the standard streams?
I think for most things switching to gio probably makes the most sense, but I do agree that would be best. std where gio doesn't make sense. Problem is that GIO is rather new to the Glib stack, so I'm not sure when we'll update to it.
I think the best thing to do is propose a patch. Less code in Inkscape is always a good thing.
--Ted