Comment 14 for bug 733966

I figured you did since it was so obvious this was SVG or a vector rendered
image being rendered through the same slow 2D code. Prerendered images are
the only way to go and not sure why it was even an option to use SVG. A bit
unheard of for most apps to use anything but prerendered in the About since
the about is of little value and is a pop-up and as such must render
quickly. Dates back to the first incarnations of "About" boxes well over
12yrs ago

On Mon, Mar 14, 2011 at 4:38 PM, John Cliff <<email address hidden>
> wrote:

> Thats because we render the about box from SVG, not a rendered image. Its
> one of the ways we eat dogfood.
> We also encourage the about images to have examples of some of the latest
> features, which generally results in fairly taxing files to render. The
> debate on prerendered vs SVG has been had a couple of times, perhaps the
> trunk should have svg and the release static renders, I dont know.
> incidentally if the first time speed issue was down to startup, thats the
> fonts being cached.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/733966
>
> Title:
> Inkscape way to SLOW - Refactor
>
> Status in Inkscape: A Vector Drawing Tool:
> Opinion
>
> Bug description:
> Guys truly it is time to stop adding features to Inkscape and go back
> and refactor the code to fix bus and the terrible performance issues.
> There is little excuse for it to be at ver .48 and performance to be
> slow sluggish. Even the about box repaints the logo/image very slowly.
> That alone would have told me I have performance issues. At what point
> do you stop trying to add features and go back and address
> performance? My recommendation is to get a better handle and control
> over the development effort and split your team and branch to allow
> some to work on new features and others the refactoring of the code
> and eventual merge. When I launched it for the first time a while back
> I nearly laughed at the performance. Then expecting someone to address
> it in .48 would have been an expectation.
>
> Do everyone a favor and place in your roadmap a REAL item to address
> performance and refactoring the code. This sluggish performance is
> across ALL platforms. For any developer on the team to be tolerant of
> such or even think of asking what hardware is foolish. Any junior
> level developer can easily determine the performance issues are within
> the code.
>
> As of now I am going to kick off my own branch of this code and move
> it to QT4 for the UI and begin refactoring for performance. I will
> make that split in the branch available for those who want a highly
> performance version of InkScape.
>
> I would invite you to address performance.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/inkscape/+bug/733966/+subscribe
>