[Monotone-commits-diffs] Revision eac91ccc6b922920c77c6d3d8e0653ae2ac30519

[monotone]

-----------------------------------------------------------------
Revision: eac91ccc6b922920c77c6d3d8e0653ae2ac30519
Ancestor: f35ab4fe461be7e3214b709443ae97b26e110802
Author: address@hidden
Date: 2007-05-07T12:09:41
Branch: net.venge.monotone.guitone.filter_by_project

Added files:
        src/model/BranchesProxyModel.cpp
        src/model/BranchesProxyModel.h
Modified files:
        guitone.pro res/forms/changeset_browser.ui src/Guitone.cpp
        src/Guitone.h src/model/Branches.cpp src/model/Branches.h
        src/model/ChangesetModel.cpp
        src/monotone/MonotoneDelegate.cpp
        src/monotone/MonotoneDelegate.h src/util/TreeBuilder.cpp
        src/util/TreeBuilder.h src/view/dialogs/ChangesetBrowser.cpp
        src/view/dialogs/ChangesetBrowser.h

ChangeLog: 

Added the possibility to filter the branch list by project, which looks
for the root revs of every branch and shows only those which match the
selected root revision we got from automate roots.
Currently this is not very performant at all and buggy: We need to do
two monotone requests to filter a single branch entry (automate heads and
automate erase_ancestors). Obviously one could cache that somehow, I'm
a bit against caching data externally and rather wait for a automate
branches version which outputs the root ids as well. A major issue is
also the filtering itself in the tree view: While normal items / branches
can simply be filtered out, aggregated items (branch*) cannot since they
may or may not contain branches which will be filtered on any next step.
The only solution here is to provide some kind of lookahead in the 
BranchProxyModel which would make the whole process of filtering items
even slower.

txtcFk2FUBumM.txt
Description: Diff [f35ab4fe461be7e3214b709443ae97b26e110802] -> [eac91ccc6b922920c77c6d3d8e0653ae2ac30519]