Where can I find source/commit log history for Inkscape before Jan 16 2006 (where the current launchpad logs start)?

And is there some overview of the changes and how they were made? The reason is because newer versions of Inkscape are slower but I want some of the features (like the multiple paths editing path tool) so I want to add some parts but not others to older versions and use those older versions.

I also wanted to try Cairo rendering in older versions (but I can't add it without a description because a bunch of things were renamed).

The other way I was thinking going about this is to look for commits where there's a significant slowdown and try to fix them.

One example is the commit on Jun 6 01:43:35 2008 +0000 "merge gsoc2008_johan_path2geom into trunk" where the start up time jumps up from 7s to 10s for me. But for many version before and many versions after, the start up time stays the same.

Of course, its taking a ton of time since building inkscape from scratch for each commit examined takes a lot of time (I'm basically doing git bisect after a git bzr clone).

Any and all answers, guesses, suggestions welcome. Thanks!

Hi.

At the bottom of this page there are links to previous release notes, going back to 0.35 -around 10/08/03.

Other pages that might help:
http://wiki.inkscape.org/wiki/index.php/OldRoadmap
http://wiki.inkscape.org/wiki/index.php/Roadmap
http://wiki.inkscape.org/wiki/index.php/DevelopmentRoadmap
or in general
http://wiki.inkscape.org/wiki/index.php?title=Special:AllPages&from=0.91-tutorial-review&to=InkboardWikiPages
or go to the live chatboard.

In the about to be released 0.91, code rewriting was announced so it may already work faster.

Hello!

Lazur URH wrote:Hi.

At the bottom of this page there are links to previous release notes, going back to 0.35 -around 10/08/03.

This is very nice, thanks! Its great to see so much of the history kept and readily available.

Unfortunately, this would be more useful in addition to changes in the code since this only talks about what has changed (as it should) but not how it changed (which is useful for both routes I'm trying). And it can't really "answer" questions that were not asked at the time.

Getting to 2003 should be enough since I think Inkscape-lite (based on Inkscape 0.36, I think) was quite fast and I don't really want to look at potential speed changes beyond that point.

This also goes to show just how much stuff happens each version (of course this was quite apparent from the commit logs but it wasn't so obvious how many features it corresponds to). Though oddly (or fortunately?) enough, xml/node and xml/simple-node have stayed mostly unchanged since 2006, or perhaps even earlier.

Lazur URH wrote:Other pages that might help:
http://wiki.inkscape.org/wiki/index.php/OldRoadmap
http://wiki.inkscape.org/wiki/index.php/Roadmap
http://wiki.inkscape.org/wiki/index.php/DevelopmentRoadmap
or in general
http://wiki.inkscape.org/wiki/index.php?title=Special:AllPages&from=0.91-tutorial-review&to=InkboardWikiPages

Thanks for the extensive answer. Although again, a number of these have the advantage and disadvantage mentioned earlier. Even the parts that talk about internals don't always say how it was done.

Lazur URH wrote:In the about to be released 0.91, code rewriting was announced so it may already work faster.

Rewritten code certainly helps with this understanding what the code changes are about but only after they are made (so everything from then on is easier to work with and understand). But integrating them with old code is still hard since I can't always tell what the thing they replaced was supposed to do (and if a speed change I'm tracking happens right there, well, I don't really dare touch it).

But I don't know if a rewrite on its own would make things go faster (note to self: to test). Right now, I'm mostly trying to figure out where the speed changes happen in the history of things (and see if it can be partly changed to avoid this).

Lazur URH wrote:or go to the live chatboard.

I might try to pop by at some point (although I didn't know how long an answer would take in the forums so I threw this out much earlier than I was able to handle the answer). This was quite a nice surprise.

Developers hardly respond this forum -not much coding posts appear for that matter-, they are mostly at the bugtracker or at the dev mailing list.
There are about a hundred people around the iirc channel constantly, that is the fastest way of connecting to the developers as I see it.
As far as I know the code rewriting is changing from python to C++ or similar, so it is [i]supposedly[i] processed faster.
Can't tell anything more, I never got deep into coding (haven't even compiled inkscape).