[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] Match statistics graph

From: Joern Thyssen
Subject: Re: [Bug-gnubg] Match statistics graph
Date: Fri, 29 Aug 2003 17:59:13 +0000
User-agent: Mutt/1.4.1i

On Fri, Aug 29, 2003 at 07:28:30PM +0200, Jim Segrave wrote
> On Fri 29 Aug 2003 (16:33 +0000), Joern Thyssen wrote:
> > 
> > As you can guess I'm not entirely conviced that we should stick with a
> > CSV file :-)
> I suppose my basic take is that we shouldn't be trying to do anything
> with the data within gnubg, only exporting it. In essence, remove the
> view player records item and the supporting code. 

OK, I see.

> Or freeze it at
> about the functionality it now has (I suppose we could save a bit more
> of the stats and display them), 

This introduces even more redundancy, and we surely end up with a CSV
file which has different data than the file with the accumulated data.

If we should show anything, I'd rather do the consolidation of the data
inside gnubg by reading the file when the user ask for the players'

> but really we should simply not make any effort to duplicate other and
> better tools in what is really a backgammon program. The issue of how
> to export the data is a second one - do we want to assume there's an
> RDBM server running? 

Yes, when they want to add stuff to the players' records.

> Which one?  

Anyone supported by Python DB2 API v2.0.

> What about people who want to import data into Excel or
> some other spreadsheet rather than a database? 

They can dump the data from the database.

> We could choose some simple low overhead  database and code that into
> gnubg, then provide simple tools outside of gnubg itself to extract
> the data for people who want to process it more thouroughly, but then
> you will be bombarded continuously by people who want database and
> data analysis code incorporated into gnubg itself.



Attachment: pgpUtZo4V7WcV.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]