Knock Out Tour

[GoogleCodeExporter]

Any chance of bringing back the KO Tours?  I could write it if you don't 
want anything to do with it.

Original issue reported on code.google.com by funnyfin...@hotmail.com on 10 Sep 2009 at 9:22

[GoogleCodeExporter]

I trashed the old KO scheduler because I wanted it to do more than just the 
initial
scheduling of "level"/round 1. I wanted it to update the whole KO bracket once a
level was finished, thereby automatically creating subsequent matches itself.
Otherwise you end up with having to convert the tournament to a FFA and 
manually add
matches after the first "level"/round has been played - you might as well use a 
FFA
to begin with, then. 
This is complicated task, as you'll not be writing a tournament scheduler, but a
tournament handler, literally. 
I had already done this successfully but the maintainability was a headache, 
there
kept popping problems up, It slowed down page loading dramatically and was 
generally
a constant thorn in the eye.

I really discourage you to embark on this, trust my experience.
Also, I would very much like to see you finish the other tasks first!

Original comment by Nimda...@gmail.com on 11 Sep 2009 at 9:06

[GoogleCodeExporter]

I thin the automatic scheduling would work well during the leegmgr match 
reporting 
routine.

The initial thing it would do is create the first round.  During the reporting 
phase 
it checks to see if the scheduled match is also a KO match, checks rounds, 
winner, 
etc and then creates the next round if the opponent is already known.  Or 
creates 
half the match putting a dummy team as the opponent, until the next team is 
known 
replacing that dummy team.

Original comment by funnyfin...@hotmail.com on 11 Sep 2009 at 11:28

[GoogleCodeExporter]

Do you think a match needs to include what seed it is in order for the 
automation to 
work?

Original comment by funnyfin...@hotmail.com on 11 Sep 2009 at 11:45

[GoogleCodeExporter]

You are welcome to strap whatever chunks of code you can use out of
lib/class_knockout.php. As long as you keep it in your module (or making a 
new), I
won't be banging my head against the wall trying to reimplement it :-).

Yes, I know what it's supposed to do, as I said I already did it. See the old
revisions of class_tournament.php if you need inspiration.

The seeding is up to you, can't remember how I did it, I managed without extra 
fields.
But please William, do me a BIG favour and leave this one alone for now. It's 
in no
way a priority, and I would really appreciate you finishing the other open 
issues you
have instead!

Original comment by Nimda...@gmail.com on 11 Sep 2009 at 12:26

[GoogleCodeExporter]

I don't have to start it soon, just gathering ideas.  It is needed.  It is a 
pain to 
do big KO tours.

Now you said you didn't need a seed, but you didn't do the auto scheduling 
after 
round 1 right?

Original comment by funnyfin...@hotmail.com on 11 Sep 2009 at 1:12

[GoogleCodeExporter]

No, I did, without hashes or seeds.

Original comment by Nimda...@gmail.com on 11 Sep 2009 at 1:23

[GoogleCodeExporter]

Original comment by funnyfin...@hotmail.com on 16 Sep 2009 at 8:42

• Added labels: Milestone-Unknown

[GoogleCodeExporter]

Original comment by funnyfin...@hotmail.com on 16 Sep 2009 at 8:43

• Changed state: Postponed

[GoogleCodeExporter]

Any chance KO Tour could be added as a tour type now?  It is a pain to have to 
lock 
a KO tour because it will be shown when calling FFA Tours.  Then to schedule a 
new 
round for the KO you must unlock the tour and then you must go back and lock 
the 
tour.

Original comment by funnyfin...@hotmail.com on 30 Sep 2009 at 4:41

[GoogleCodeExporter]

Sorry, but that's still the way it's going to be. It'll be resolved once the
coach->league scheduling is implemented, if I understand you correctly.

Original comment by Nimda...@gmail.com on 1 Oct 2009 at 8:35

[GoogleCodeExporter]

We'd still need a KO Tour Type and even before anything automated is done KO 
type 
would still be a usefule choice even if it must all be scheduled by hand.

Original comment by funnyfin...@hotmail.com on 1 Oct 2009 at 8:39

[GoogleCodeExporter]

Sorry for being such a pain, but please explain to me again why having a 
separate
type would help, even if the bracket scheduling it is not automated?

Original comment by Nimda...@gmail.com on 2 Oct 2009 at 4:59

[GoogleCodeExporter]

A KO type that does the same thing as FFA would allow modules to know whether 
or not 
they are dealing with a true FFA tour or a KO tour.  In my specific case, I do 
not 
want to have to lock a KO tour in order to keep it from showing up on the FFA 
list.

Original comment by funnyfin...@hotmail.com on 2 Oct 2009 at 6:15

[GoogleCodeExporter]

But the way I see it the implementation is totally impractical.
Where would you place the list of KO-tours? Also, people would still be allowed 
to
add matches to the tours in that KO-tour list unless they are locked - which 
then
again is the same as a FFA system? I assume you have abandoned writing the 
entire
scheduler?

Original comment by Nimda...@gmail.com on 3 Oct 2009 at 9:30

[GoogleCodeExporter]

I haven't abandoned the KO scheduler.  I actually need this KO type before I do 
that 
anyway.  And I really need to to be able to change the uploading to an 
automated 
uploader.  I will be making it so if a match is uploaded, it will automatically 
choose to send it to the first available FFA tour for that league.  This is 
where it 
would be nice to not have a KO tour listed as an FFA tour.

Original comment by funnyfin...@hotmail.com on 3 Oct 2009 at 10:38

[GoogleCodeExporter]

OK. 
I *strongly* suggest another solution then:

Have your module use/make a new table which sets your own options/attributes on
tournaments. When uploading you consult this table to see what is 
allowed/possible
and so on. This gives you much more power including making your own admin page 
for
settings these settings...

Do you follow?

Original comment by Nimda...@gmail.com on 9 Oct 2009 at 8:31

[GoogleCodeExporter]

I'd rather just build the logic into the script than create another table...

Original comment by funnyfin...@hotmail.com on 10 Oct 2009 at 2:57

[GoogleCodeExporter]

What script? 
If you can do it in your module, fine, else it'll have to be that way (with a 
table)
for now.

Original comment by Nimda...@gmail.com on 10 Oct 2009 at 3:20

[GoogleCodeExporter]

I think you are missing my main point here.  We'll just need to chat on it:)

Original comment by funnyfin...@hotmail.com on 11 Oct 2009 at 2:38

[GoogleCodeExporter]

Shall we close this if you are not going to take any action on it any time 
soon? You can re-open if necessary...

Just for the sake of cleaning a little up.

Original comment by Nimda...@gmail.com on 20 Oct 2010 at 9:37

[GoogleCodeExporter]

Re-open when necessary/you resume your work. Closing for now.

Original comment by Nimda...@gmail.com on 20 Oct 2010 at 3:18

• Changed state: WontFix