Quote:
Originally Posted by Chris is me
The current system tells you a green, yellow, red indication of roughly how long the waitlist is, but not an exact number. So I guess it only needs to be that specific. I guess it wouldn't be that hard to code something like this, but I'm hesitant to rely on even more custom software and logic for this sort of thing, considering the track record from FIRST recently of their web interfaces and whatnot.
|
The nice thing is that it can be a standalone system.
Let me blue sky this for a second.
Lets use a simple scripting language like Lua. Lets assume that all the events have a 4 letter code. Users would create a Lua script and submit via text box.
Code:
If EVNA.available then EVNA.register; -- first choice
If EVNA.green then EVEA.register; -- short wait list, that works
If ABCD.available then ABCD.register; -- lets see about event #2
if EVEA.yellow then EVEA.register; -- didn't get it, check on event 1 list
if ABCD.yellow them ABCD.register; -- rats, how long is the wait for #2
if XYZY.available then XYZY.register; -- sigh, ok what about event 3
-- nothing available that I want, just register on the first event and hope
EVNA.register; -- fingers crossed
Website just does a parse check to see if the code compiles, save to text field in data base.
On registration day, just pull the scripts out one by one and run them. I'd save the "random number" order so that if something bad happened I could re-run the same order again. (or run with a specific seed to the random function)