[Top][All Lists]

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

Re: [Bug-gnubg] Three things that are broken

From: Massimiliano Maini
Subject: Re: [Bug-gnubg] Three things that are broken
Date: Mon, 16 Apr 2007 13:51:48 +0200

> Vehemently opposed to removing python support. This is a major
> mistake. If it's broken on some systems, lets get it fixed. One of my
> projects which I'm finding difficulty to find free time for but really
> would like to finish is to add the option to put errors into the
> database and allow players to select a previous error at random and
> replay it. I think this would make a very effective training
> tool.

Totally agree.

> Doing this in C code would be possible, but very
> difficult. Doing this using Python requires adding a small number of
> additional Python functions into gnubg.

Well, I tried to do this in Python (actually I just tried to export to
text format all the bad/very bad decisions of an anlyzed match/session)
and I gave up : no documentation, strage behaviors, bugs, Windows
specificities ... I just do it manually : run through the match, export

I don't think coding the feature in C would be a big pain ... I would
even say that the right thing to do is to create an (optional) error
rdb (every time a match is added to the players rdb, the errors are
optionally added to the error db). Then, a simple command would
allow the user to fetch one error according to various criteria (random,
chequer or cube, etc).

reply via email to

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