One of the items on my TODO list for 0.9 was to switch to a gtk.ListStore() as the data back-end for the changelog tool. This has been recommended by just about every GTK+ person who has looked at our changelog code.
I got this working today, but I'm not terribly impressed at the results. Using a gtk.ListStore() forces you to load all the data for each revision up front, so the initial load of the revisions is slower. Once in memory, it does scroll more smoothly than the existing code, but I think this is a poor trade-off. And while I expected the ListStore to be more memory efficient, it turned out that the old method was ~10% more efficient memory wise. Long story short, I'm going to leave the old back-end in place, but I'll refactor it to make it more maintainable, and optimize a bit for speed and memory usage. I think I'll checkin this ListStore change and immediately back it out, just so there's a record of this experiment in the repository. -- Steve Borho ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
