On Mon, Jan 03, 2005 at 05:58:27AM -0600, Derek P. Moore wrote:
Does the file really need to be broken up?
I think so, yes.
I think you're going to have to make other plans. :(
I didn't imagine that writing a script to explode icons.svg into its separate files would be that complicated. I mean, Inkscape already does some fashion of this in C using Inkscape's render.
It's not simple. Some of the icons depend on eachother (for their elements or gradients, clones, etc), and the offset/size information comes from the rendered bounding box. That was one of the reasons for merging them into a single file; it's easier to maintain a certain look/feel.
The only problem right now with porting sp_icon_image_from_svg() to the Gtkmm codebase and its use of IconSource/IconSet/IconFactory is that the Gtkmm code doesn't yet have the Inkscape renderer.
? With separate svg files how were you going to render those?
All I can do right now in the Gtkmm code is have GTK+ load each icon separately based on filename and have it automagically rendered via librsvg where ever its required according to the StockID it's associated with.
Is that just temporary? I thought we wanted to use Inkscape's renderer. If you're going to do something temporarily, I would recommend writing a quick hack to inkscape to export all the icons from icons.svg into separate png files and just use those until your tree is merged.
Besides, parsing icons.svg complicates the code quite a bit more than simple repeated calls to IconSource::set_filename().
I've attached the script I made, but it's not very robust. I worry you'll spend more time making the broken-up icons look right than just putting everything into the main branch and using the renderer.