Richard Kettering III <[email protected]>:
> I think it's a excellent idea; in fact I think it's long overdue.
>
> The only minutiae suggestion I'd have would be to use disclosure
> triangles instead of +/- elements; or even to use the open-book vs.
> closed-book icons we have for the help files. If you're wondering
> what disclosure triangles are, here is an article. I'd prefer them
> over +/-, they're slightly less ambiguous, and slightly more intuitive:
> http://wiki.jrmediacenter.com/index.php/Disclosure_triangle
Ah, so *that's* what those are called! Agreed - preferable to +/-.
However - boucman has pointed out that the tree-view paradigm these
imply doesn't really fit the relations among saves. (I knew this up
front, actually, but thought we could evade handling the most general
case; he showed me otherwise.)
The problem is this: suppose I have a sequence of end-of-turn saves A,
B, C, D. D is the tip save. Now I go back to B and play it a
different way, containing a line of saves C2, D2, E2. Right now you
have to manually change the devault savename while working on the
second line of play, otherwise C2 will overwrite C, etc.; but this is
possible.
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.
boucman suggests that the best effect-to-effort ratio would be to continue
displaying saves in straight chronological sequence, with a toggle controlling
whether only tip saves are displayed or all are.
I think the ideal solution would be the way the Mercurial
version-control system handles lines of development, with a achematic
node-and-link tree drawn to the left of a chronological sequence of
save names. I can't find a good screensave illustrating this, but here's
an ASCII mockup
| + E2
| + D2
| + C2
+ | D
+ | C
|/
+ B
+ A
Of course, the code to render the node-and-link tree would be tricky.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev
