|
From: | Joseph Heled |
Subject: | Re: [Bug-gnubg] Match statistics graph |
Date: | Sat, 30 Aug 2003 11:09:59 +1200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 |
Let me stress my previous post.Why not write a python script that goes over matches and writes down the required data in whatever format we want. We can do it easily today. Perhaps what we are missing is a nice way to activate those scripts from the GUI?
Advantages: - You don't need to change player records. - You don't worry about future extensions. - You avoid GNUbg bloat. - Can adapt to any format. - Lets the user select any plotting/database she wants. Disadvantages: - You have to keep the .sgf files around (but I guess you do that anyway)? -Joseph Jim Segrave wrote:
But the difference I see is this: If someone computer illiterate (and I don't mean this in a derogatory sense, I'm a good programmer and a crap auto repair/simple household work, gardener... person. I'm mechanical illiterate in that sense) wants help with extracting some arcane data from a match or a long series of matches, then the choices are: a computer programmer adds a function to gnubg - difficulty 100 a computer programmer writes a python script to get gnubg to find the data - difficulty 10 a computer/database programmer writes an SQL query to find the data - difficulty 1on a wild-assed guess normalised scale.
[Prev in Thread] | Current Thread | [Next in Thread] |