![](https://secure.gravatar.com/avatar/3cec223a8f3cba594098fb34a2075f42.jpg?s=120&d=mm&r=g)
Am Dienstag, den 04.01.2005, 14:57 -0400 schrieb bulia byak:
On Tue, 04 Jan 2005 12:33:51 -0600, Derek P. Moore <derekm@...606...> wrote:
Ideally it would be permanent. It's the Right Way To Do It(tm);
You haven't convinced me still.
- rsvg is broken. Talk people who are drawing icons in Inkscape to be
rendered by rsvg (e.g. Brisgeek). There are lots of complaints. I don't want this problem for us.
The only problem I have with it is the text support. But I would not call it broken.
- Drawing icons consistently is much easier when they are in one file.
Jep, thats right.
- Loading them from one file is faster too.
Some lines below you wrote: "Even with our current slow-as-hell renderer, rendering icons are in no way a speed bottleneck."
- Don't Fix What Is Not Broken (TM). I see no real problems with the
current implementation. If it was possible to use it with GTK, I'm sure it's possible to use it with gtkmm as well. With the necessary support code, passing an id to get an icon is just as easy as passing a filename.
Don't reinvent the wheel (TM). Why think about something, that is solved in 1000 other apps, just let gtk care about the icons. And doesn't inkscape already use gtk-stock-icons in some places?
Yes, of course it is nice to use our renderer for the icons just because we can do it, but that is not the goal of the program. We even don't render the buttons with our renderer. ;-) With the the standard GTK icon facilities you can use PNGs or SVGs directly, you just don't need to care about it.
Tobias