elf
/
yahoobingo
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
A client for the Yahoo! bingo contest. #complete
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
8 Commits
1 Branch
0 Tags
128 KiB
 
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Elf M. Sternberg 72dcd58784
Improve readability; fix end-state handler. 		10 years ago
.gitignore Bingo client. 10 years ago
LICENSE Updated with Github info and Coffeescript dependency. 10 years ago
README.md Changed initial state to 'playing', so that we don't assume a broken connection is automatically a lost game. 10 years ago
bingo.coffee Improve readability; fix end-state handler. 10 years ago
package.json Removing underscore as a dependency. No longer hacking objects, just indexes. 10 years ago
package.yml Removing underscore as a dependency. No longer hacking objects, just indexes. 10 years ago

README.md

Yahoo's running this contest. Read about it here: http://yahoobingo.herokuapp.com/

This took me about 40 minutes, total. I was thinking about re-writing this in Bacon, but my Bacon is pretty raw. At best, I could propertize the cards to create a new card (i.e. a new state) every time a ball came in, but that seemed a little overwrought.

It was nice to have an opportunity to hack Coffee and Node again.

I don't know that I trust Yahoo's server. At least once I got back a "you lost" signal from the server. Since this client includes full playback of every game, I could see that I had clearly won. Unfortunately, my initial code assumed "lost" as the default state, so I couldn't see if maybe the 'won' signal was lost before receiving the disconnect. I've changed that to 'playing,' so we can see that condition now.