Simplifying tournament class (delete some of the tournament types)

[GoogleCodeExporter]

This is a vote. For or against?

The tournament class and its tournament types have always bothered me a lot
because of their unnecessary complicated nature. 
With the FFA scheduling leagues can just as easily create their own K.O.
and RR tours, and removing the old large code chunks (for handling the tour
types) would simplify obblm A LOT.
Therefore I'm thinking of doing so - maybe leaving the RR scheduling system
in place, allowing to schedule a classical RR as a FFA, thereby not having
to setup a RR tournament from scratch. Essentially this is the same as
creating a RR tour and converting it to a FFA. 

What do you think?

Original issue reported on code.google.com by Nimda...@gmail.com on 2 Jun 2009 at 9:28

[GoogleCodeExporter]

If it will simplify things for you in the code, I'm all for it. I know that my 
league will never use anything other than FFA, realistically speaking; we're 
too 
large to do RR or KO without micro-managing them -- which, as you said, we 
would do 
by manually setting them up as an FFA, anyway.

Original comment by lahat...@gmail.com on 2 Jun 2009 at 11:32

[GoogleCodeExporter]

I would like to always see:

round robin without final, final isn't needed as you can make a KO.
KO
FFA

Original comment by funnyfin...@hotmail.com on 2 Jun 2009 at 6:20

[GoogleCodeExporter]

To add on to that I would say you don't need round robin to be able to play 
same 
people multiple times.  That is just my thought off hand.

Original comment by funnyfin...@hotmail.com on 2 Jun 2009 at 6:34

[GoogleCodeExporter]

One thing I'd like to see if the ability to choose pairing for a Knock Out style
tournament.  Allow whoever sets up the KO tournament to enter in a seeding 
number or
another way to allow a Commissioner to determine who plays who.

Original comment by meini...@gmail.com on 10 Jun 2009 at 8:47

[GoogleCodeExporter]

FFA allows for "manual" creation of KO tournaments. The commish have to do 
pairings
though. More intelligence has been requested before, in KO tours, and has been
denied. The code for KO is complex as it is. And there is no chosing/seeding who
meets who in KO. (Dont remember if it was team_id or name of team that decided 
the
order/pairings.)

Original comment by blodae@gmail.com on 10 Jun 2009 at 9:35

[GoogleCodeExporter]

correct..

Original comment by Nimda...@gmail.com on 10 Jun 2009 at 10:11

[GoogleCodeExporter]

Thats what I was thinking, instead of using team_id add a column where the 
Admin 
enters in a number.  Looking at what I can figure out it would work, just isn't 
really worth the effort.

But the nice bracket the KO creates is nice and shiny.

Original comment by meini...@gmail.com on 11 Jun 2009 at 11:43

[GoogleCodeExporter]

Original comment by Nimda...@gmail.com on 7 Jul 2009 at 9:20

• Changed state: Fixed