[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] replacement for game list
From: |
Nardy Pillards |
Subject: |
Re: [Bug-gnubg] replacement for game list |
Date: |
Mon, 05 Jan 2004 11:37:20 +0100 |
On 5 Jan 2004 at 10:16, Joern Thyssen wrote:
> I'm not 100% familiar with GtkTree, but one problem is that GtkTree
> operates in "row" mode, i.e., you select a given row. We want to
> select a given cell, which makes a spread-sheet-like approach better.
>
> The alternative is to change the game list to be more snowie-like,
> i.e., instead of
>
> 1 65: 24/13 31: 8/5 6/5
> 2 65: 24/13 66: 24/18(2) 13/7(2)
>
> we use
>
> 1 65: 24/13
> 31: 8/5 6/5
> 2 65: 24/13
> 66: 24/18(2) 13/7(2)
>
> The advantage of the snowie-like game list is that it's much much much
> easier to implement (I can even add whoppers and colors to such a
> list). The disadvantage is that it takes up more vertical space.
>
> Jørn
If there are opponents (as in backgammon), the human eye (and brain)
tends to the gnugb approach. Left side - riht side.
(and it's what i personally prefer).
Yet I don't think this should be considered as 'No, I don't like a
change'.
Some out there are using Snowie, and I'm pretty sure they don't even
know what I'm talking about.
So: if working in rows instead of cells eases the job, go for it.
The disadvantage (less information visible) won't outweight the
advantage of visibility.
A user concentrating on the moves list, is a user analysing the game.
And thus the 'natural view' isn't that important: he/she is already
focusing on data. And opposed to chess and alike, a backgammon player
does not need to see the next 10 moves, since the dice influence
strategy.
My 2.2 cents :-)
Nardy
PS
I will be away for a week. No Win32 builds before Jan 13th :-(
Nardy