2 ms·
A recap of your pleasant original comment: "Don't get me wrong, it's a nifty little app. You probably learned a lot! That said, it's still just
by danneu 13y ago
A recap of your pleasant original comment:
"Don't get me wrong, it's a nifty little app.
You probably learned a lot! That said, it's still
just a toy campus app."
A morsel of value from the world squandered.
I'll bite your offer for you to mock it up in Ruby real quick. The problem with the "it's easy and I could do it" dismissal is that, even though you could, you didn't.
Maybe you can team up with this guy[1]. You can probably even reuse his repo[2].
[1]: https://news.ycombinator.com/item?id=678501 https://news.ycombinator.com/item?id=678501
[2]: http://code.google.com/p/hackerexchange/ http://code.google.com/p/hackerexchange/
- tempestn 13y agoHey, [1] was only 1584 days ago. [2]'s looking not too bad for only 225 weekends in.
- angersock 13y agohttps://gist.github.com/crertel/7244841 https://gist.github.com/crertel/7244841 There you go--left out the boring HTML scaffolding (original chat example modified from here: https://github.com/igrigorik/em-websocket https://github.com/igrigorik/em-websocket). EDIT: It's super MVP, but the concept is there. A very, very simple addition would have the server echo back to the clients the lat/long pairs in question to dynamically update, say, a Google Maps window. For real usage, I'd use a PostGIS query--something like this: http://unserializableone.blogspot.com/2007/02/using-postgis-to-find-points-of.html http://unserializableone.blogspot.com/2007/02/using-postgis-... . EDIT2: Looks like we're both Texans--if you're ever in Houston, I'd be glad to grab a beer with you.