On Tue, May 26, 2009 at 07:49:38 -0400, "Eric S. Raymond" <[email protected]> wrote: > > If we're displaying only threads, it's clear what to do; only D and E2 > get listed. But if we're displaying all saves associated with a thread, > how do we represent the branch point? The straight tree-view model suggests > a > visual branch per thread, with A and B listed twice.
You're looking at the tree from the wrong side. The save games have to form a tree (assuming you're not missing entries) because there is no way to have branches merge later. The issue is that normally you don't want to see the root of the tree, but rather leaves. Maybe it would work to instead of showing the save game from the branch point, the latest dated save file. If you expand the branch point, then you would see the latest leaf in each branch and the branch point would switch to showing the save game they branched from. That might be a bit confusing as a UI, be shouldn't be too hard to implement relative to what you were initially discussing. _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
