On Fri, 2005-08-12 at 14:06 -0400, mental@...3... wrote:
Careful, you never know what other lists the Inkscape developers are subscribed to. :)
Quoting Vladimir Savic <vladimir@...958...>:
You cann't imagine the amount... One of most obvious is strange development course. We say "as with left leg writen" code. Optimisation is ...awesome... more then 1000 nodes and my box is literally dieing.
This is largely attributable to the current renderer. Parts of it have something like O(n^2) performance with the number of segments.
Unfortunately none of the current developers have simultaneously the time and the expertise to replace it (numerical stability, the really hard part, is as critical as speed).
We do plan to replace it with Cairo when that's ready, but realistically that probably can't happen at least until Cairo's 1.0 release.
In the meantime, any volunteers to help with cleaning up the rendering code would be very, very welcome.
And here we are -- for comfortable using of fonts -- YOU NEED A WORKING TOOL!!!! Font dialog is broken since 1950 - and chrushes the inkscape every single time.
This bug is new bug to us. The font dialog is crappy, but it doesn't crash for most users. Could you please report it in the bug tracker?
My guess is it's a bug exposed by the particular combination of fonts, languages, and libraries on your system -- so all the information you can give us would be helpful.
I had a crash problem with the font dialog and did a backtrace and found it happened to be an out of date aspell library.
Maybe you all could provide a backtrace of the font dialog crash. Here are my versions:
app-text/aspell-0.50.5-r4 app-dicts/aspell-en-0.51.1
Jon