> That's good. Then one can use either a pyhton script, where all "next
> marked !?" will be rolled out, or we think about implementing
a "batch
> rollout" of certain marked moves. The latter would be easier
to use for
> not so experienced windows user.
I do think that gnubg is not using enough of the possibility
offered by Python. Why coding a batch rollout when a python script
can do the same ?
For the user, as soon as he has a button somewhere
in the GUI to start the bacth roullout, it should be the same. Probably
the Python code would be much more readable and other users could modify/improve
it.
As a side comment, I do think that a fist step in
promoting python would be to have a few (3-4) "programmable" buttons,
i.e. buttons that simply runs 3-4 predefined python scripts (e.g export errors,
rollout errors/close/ marked decisions, etc).