On Sun, Mar 19, 2006 at 11:22:31AM +0100, Michael Gerz wrote: > Jean-Marc Lasgouttes wrote:
... > given the fact that some bigger changes have to go into 1.4.X sooner or > later (speedups & CT), I think we should keep 1.5.X and 1.4.X in sync as > long as possible. I tried to keep track of all potentially relevant changes > that haven't been applied to 1.4.X, yet. These together constitute the multi-par CT work: > r13339 - Fix bug 880, or the multi-paragraph change tracking patch > r13356 - fix painting of change bar with only paragraph break changed > r13385 - Change tracking -related bug fixes (reported by Juergen) > r13408 - fix stripLeadingSpaces mechanism with change tracking enabled > r13418 - expand redrawing of current row to endpos() AGAIN > r13422 - Fix changebar non-update (Juergen) And these together the speedup (row paint caching inside insets) work. > r13328 - Fix bug 2195: Slowness in rendering inside insets, especially > on the Mac > r13415 - Changes to the within-inset row rendering caching code > r13420 - constify; remove unneeded casts Thanks for this compilation! > IMHO we should apply at least a few of them. Otherwise, it will become > more and more complicated to extract patches from the trunk. Yes, I think so. But as blocks as above, because they belong together. As for the speedup patch, I would like to know what makes your document slow. At least *that* speedup patch (if we have it :-) should be considered next for 1.4.x. - Martin
pgpVNtetOM0tz.pgp
Description: PGP signature