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

[Jonathan Kinsey]

> From: Christian Anthon <address@hidden>
>
> - Python support
> a) It is buggy
> b) Nobody, even among the developers use it regularly.
> c) It will never be used by a very large fraction of the users.

I was against using Python in the player database when that was done, when 
you get past all the argument passing and things it does offer some nice 
features though.  I'm all for removing Python from the relational db, I 
think we should keep it as an external interface though (probably).

> - Time controls
> a) it doesn't work out of the box
> b) it crashes (at least for me)
> c) It will never be used by a very large fraction of the users.

I think underlying the problems with time controls is the bad shape of the 
code, so maybe taking it out for now is a good idea, it can be re-added when 
(!?) the game management code has been redone.

> - Player records
> a) the player records are under featured
> b) the relational database requires some setup and is overkill in its
> construction
> c) It is used by a large fraction of our users

It was always my understanding that the old player record code would be 
removed when the relational database was working.  It's an important feature 
so we should try and finish off the new player record database (with some 
nice reports and graphs and things...).

> So what do you think? My personal preference is that we terminate python
> support and time controls. And I prefer the relational database, but it
> needs some adjustments, especially if we get rid of python support.

I seem to agree.  All for redoing the menus/toolbars as well.

Jon

_________________________________________________________________
Get Hotmail, News, Sport and Entertainment from MSN on your mobile.  
http://www.msn.txt4content.com/