On Sun, 2005-12-25 at 16:46 -0400, bulia byak wrote:

On 12/25/05, David Christian Berg <david@...407...> wrote:

...

Hey guys!

With latest CVS and an experimental Debian the text and font dialogue crashes right on trying to launch it. any clue, what might be wrong?

Works for me. Do you have a backtrace?

Just made one... I don't have any clue, what it means, but it's attached :)

...

Furthermore we're right now trying to do a script that makes it possible to extract the icons form the icons.svg in to single files. Let's see, how it works out.

It will slow it down HUGELY on startup. And make it more difficult to keep icons consistent while editing them. It's been discussed here extensively, did you see that discussion?

I have followed the discussions... the reason for wanting this is that with gtkmmfication inkscape is getting it's icons rendered by librsvg and I do appreciate this step. This means though, that single files are needed. Furthermore it will make it easier for using more stock icons and adding inkscape icons into the stock icons. So while I suggest to change anything with inkscape as it is right now, it is a small step towards making the gtkmmfication just a tiny bit easier.

David

On Sun, 2005-12-25 at 17:58 -0400, bulia byak wrote:

On 12/25/05, David Christian Berg <david@...407...> wrote:

...

bt

This is a crash is aspell. Look it up in closed bug reports. As far as I remember the likely reason is that your aspell library is compiled by a different compiler version.

Thanx!

So what advantage will librsvg rendering give us? I only see disadvantages (likely slower, not so easy to edit icons, may be surprises with non-compliant rendering), not to mention the "don't fix what is not broken" principle.

I have argued about this extensively in the past, and I had hoped this issue is put to rest. Are there any new reasons to reopen this?

I can't find the discussion right now, but I do remember, that you were strongly arguing against this. I do also agree with your point of view. The interesting part is not about librsvg or whatever, it's about giving away the parts of a program which should be done by a global layer.

You can use stock icons just as easily now, and some commands use them. The single icons.svg is not an obstacle to that.

Well, actually I meant something else. If you have the icon files as separate files already, you can easily copy them into your icon theme and have them used on a system-wide level. With Gtkmmfication Inkscape should move towards using flipping and rotating icons and whatever else exists from the icon theme.

That is fine, but if you want to do that, you can easily export the icons you need manually once. It's no reason to break the internal rendering of icons in Inkscape.

Actually the script is not about breaking it in the first place. Very obviously the new GUI uses single icon files... since all the icons don't exist yet, and doing them manually is not quite handy, I asked my brother to create a small script doing that manual work. It's not really nice a script, but it gives you quite the ease of use, because it takes the IDs and creates separate images of the groups with those IDs.

Take care!

David

On Dec 25, 2005, at 2:35 PM, David Christian Berg wrote:

On Sun, 2005-12-25 at 17:58 -0400, bulia byak wrote:

...

You can use stock icons just as easily now, and some commands use them. The single icons.svg is not an obstacle to that.

Well, actually I meant something else. If you have the icon files as separate files already, you can easily copy them into your icon theme and have them used on a system-wide level. With Gtkmmfication Inkscape should move towards using flipping and rotating icons and whatever else exists from the icon theme.

Or...

One can just hook things in to the standard API for rendering icons. That is, have Inkscape act as an icon source. Then we keep control of the icon rendering but still get all the 'standard' API's features. Then standard Gtkmm work can follow.