node.js ko
Patrick Meenan
Patrick is the founder of webpagetest.org and is part of the team at Google responsible for making the web faster.
Votes (10)
dtudury
contestanthey, thanks for looking at it. I've heard that a few times. I got pretty lucky with the judges not running into it (until now) :) I'd say "please try firefox and safari" in the hopes of getting lucky, but it seems like people that get it, get it in everything... sorry you weren't able to check it out.
The concept is great but it wasn't behaving as expected when I was playing. The movements appeared random rather than following the color tiles (using Chrome 23). The concept and design are great though, would like to see it when the kinks are worked out.
After hitting 's' for the first time, all subsequent keypresses acted as if they were also 's' so movement became impossible.
The facial detection is pretty cool but this doesn't seem like a particularly interesting application of WebRTC or Node.
- Audio doesn't work on Chrome 23 on Windows.
- There should be some form of highlighting to show you which element you locked in and which one the opponent locked it (and the connecting line should also be highlighted).
Was a lot of fun. Couple of suggestions for possible improvement:
- Make the note rage wider so they are a little more distinct.
- Provide a counter or some feedback to indicate when I can make a move.
levito
contestantThanks for your input! We also have a lot of ideas for improvement. You should know we came up with the actual game idea on saturday :)
Regarding your suggestions: There is a counter for whose turn it is - the tubes in the top right. If they are glowing, you can make your move. They are turning off as your time goes down. If they are all off, it's your opponent's turn.
With the note range you mean it's too hard to guess? Well... for a musical ear it can be too easy. We have chosen a pentatonic scale so our randomly generated patterns always sound as pleasing as possible, and only 6 different notes to make it not too hard to play.
Great starting point for kicking off deployments. Can see a bunch of ways this can be extended:
- API for automation
- Ability to update existing deploys
- Scale up/down deployments
niallo
contestantThanks. Yes, there is a lot more to be done and I hope to continue this as an open source project :)
This would not work very well for 3rd-party API calls that rely on cookies for user identification since the requests will be on the wrong domain (Facebook, Twitter, Google+, etc). It can work reasonably well for API's that you control or anonymous API's.
It also introduces a cross-API dependency in that none of them populate until all are complete. It might be more interesting to just provide the caching/proxy functionality and keep them separate.
Finally, it would have been nice to see the sample scripts be loaded asynchronously instead of as blocking script at the end of the page.
dtex
contestantThanks for the detailed comments. It's not intended to make requests for your sites visitor's account or based on parameters defined by the user. It doesn't make sense to cache those 1-off requests so you should just go direct. Many of our clients embed their own YouTube, Twitter or Flickr feeds on their pages. Same request every time so it makes sense to cache it.
SPAS can make requests on behalf of a specific user using OAuth (if authentication is required).
As for not all of them populating until they are all complete,
A feature I did not have time to add, was a timeout on the request to the API. If the API is taking too long or bombs out then the stale data should be returned. The data would be updated once the API returns a response so the next request to SPAS would be current.
I also confess there is a bug. I am not tracking my asynchronous requests properly and it is prematurely returning a response leaving some of the API panes empty.
Yep, I should have made those calls asynchronous. Wasn't really thinking too much about those sample pages.
Having issues? When I complete the OAuth flow I get an "Internal Server Error:
Is it currently having issues? The map looks like it is working but the OID display for individual devices is blank
mainiak
contestantHi. Yes. It has more bugs than we would like to have. This one is forgotten hardcoded localhost url in client part, which we found five minutes after code close time. But this is only beggining we promise :)
Having issues? Tried both Chrome Stable (23) and Canary and the UI doesn't react or allow for any actions (even after populating the password field). The Facebook login bar doesn't show up either.