to install bcrypt:
npm install bcrypt --openssl-root="C:\Users\Mack Yi\openssl"
** fixed now by moving openssl to C:\OpenSSL-Win64
1/24/13 added 'play' route and play.jade figured out how to display games using looping logic in jade and querying database problems: games shouldn't really be permanent, they multiplied pretty quickly have to save games all the time in order for this to work solutions: have "global"-ish variable that stores games, among other things, temporarily should this be saved into the database regularly, maybe using setinterval? not sure, don't see why for now next time: 1. implement global-ish variable 2. make play.jade useable, but not pretty 3. figure out socket.io configuration to go to specific games using game:gameid where the id can be extracted - but only from the database? solution: store every game in the database upon creation with its name, so that, if nothing else, it can at least be queried around. this seems sketchy how about using an id on the global-ish variable? this seems sketch but cool. not sure how it would be implemented. not sure if it should be the same as the one used in the database
1/25 addressed (1) fiddled around with global games variable... errors with restarting server and people still being on the page...not sure how to prevent this...why isn't authorization stopping them? looked into node-inspector, should use that because console.log() is pretty unreliable
next: same as last time.
also: figure out a way to keep usernames, users, usercolors, etc. in some reasonable way. updating a bunch of stuff every time seems like a pain in the ass.
1/26 games is mostly working adapted chat for multiple rooms and logged in users...mostly. colors is still not moved over, among other things. play has now replaced games on navbar and able to pass game_id to html. not sure how to proceed next: put links on play.jade, and probably make it presentable too use locals.message to make redirects make more sense than they are now make a game in sockets, man.