--- On Mon, 11/5/09, Massimiliano Maini <[email protected]> wrote:

From: Massimiliano Maini <[email protected]>
Subject: Re: [Bug-gnubg] list of issues
To: [email protected]
Cc: "gnubg-list" <[email protected]>, 
[email protected], "Christian Anthon" 
<[email protected]>
Date: Monday, 11 May, 2009, 9:15 AM



[email protected] wrote on 10/05/2009 
12:45:28:


My 2c on Mike's post(s): 

- most of your problems comes from the graphics drivers issue. I wouldn't 
develop workarounds for that but rather solve it (Jon is on it). 

- 2 buttons for resign and reject is totally fine according to GUI standards: 
they are 2 distinct actions. If we make only one, how do we label it ? 
"Resing/Reject" ? Or have a label that dynamically changes between reject and 
resign ? Both bad imho. 2 buttons is fine (one grayed outwhen appropriate is 
perfect). 
 
MJR: Both actions mean that you're quiting the game - one is done during play 
and the other is only done after being doubled. The result though is identical 
- you quit, Sadly the program responds to resigning (after being doubled) in a 
different fashion ie it asks if you wish to resign a double game - this doesn't 
make sense in this situation. Perhaps you guys as developers can understand a 
reason for having two buttons but to an everyday user (ie me) it's confusing. 

- what's 'the score' you would like to see along the match ? Your FIBS rating ? 
Your Error rate ? Both would be almost pointless, even more if they take into 
account all your past matches (they would barely move during one match after 
you have played, say, 100 matches). 

 
MJR: The score is the fibs rating and it should be average out over a number of 
games to give a real indication of progress or even show any progress or lack 
thereof (ie -4 in red). Not too many games otherwise no change will be seen and 
not too few so that the score wildly fluctuates.

- the wild swings in FIBS rating are unavoidable: estimating your (FIBS) rating 
with a single match (most often a short/mid one) is essentially impossible. 
You will have to look at long term averages. 

- forum/mailing list: I know I will be labelled as "old school" but I wouldn't 
trade the currnt mailing list for a fancier forum. The mailing list is a 
developper 
maliling list. No real need for structure (topic, subtopic, subsubtopic) and/or 
fancy emoticons, singatures etc. Plain text is also enforced (I believe). 
However, if anybody wants to create a forum for gnubg users around the world, 
this could be a good idea. 

 
MJR: I'm sure the current system is fine for you guys but if you want feedback 
from average users then you need a system that is usable by average users. The 
current system is not - I can't even find this thread using it! If you base all 
your development decisions on the feedback through a utility like this then 
your decisions will be skewed entirely towards what a developer thinks a user 
wants and totally ignore real users as they are excluded.

MaX. 



      
_______________________________________________
Bug-gnubg mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnubg

Reply via email to