4 ms·
yeah, the design and CSS tweaking took a lot of the time. I hadn't done any Twitter / search.twitter API stuff in Rails before either so it took some time to fi
by elliottkember 18y ago
yeah, the design and CSS tweaking took a lot of the time. I hadn't done any Twitter / search.twitter API stuff in Rails before either so it took some time to find the best way of doing things. Plus, I was watching a couple of movies - that didn't help.
- Steve-UK 18y agoReally need to get in on coding in Rails, not tried it as of yet. How does working with Twitter API differ much from other languages in Rails though? Still based all around parsing the atom feed from Twitter surely. http://search.twitter.com/search.atom?q=oops http://search.twitter.com/search.atom?q=oops
- cschneid 18y agoDidn't look close, but this gem might do it: http://twitter.rubyforge.org/ http://twitter.rubyforge.org/ In addition, there are more generic atom parsing gems that make coding quick. The great thing about ruby is the ease of making mini-dsls that make things like this trivial.
- elliottkember 18y agoYeah, that's one - there's actually two APIs going on here. One's the search.twitter.com API, and one's the official Twitter API. The search API is used for finding them, and the Twitter API is used to fetch profile images and follower counts.