Heipei

I thought i’d report back here to tell you how much progress i made (with RoR). Well, to be honest, not that much. But as always I learned some other useful things in the progress. Anywho, as you can see in the photo i created a little rails application which takes a search string and returns the image results from flickr and yahoo image search. Flo inspired me to do this, and i was planning on adding other search engines as well (Google Images, MSN Image Search). The good thing about flickr is that there is a ruby gem called ‘flickr’ which does everything one could need, albeit reaaally slow (takes 3-5 sec. per image, somethings wrong there). The same guy also created a yahoo-search library, but for some reason didnt include the url for the thumbnails cached at yahoo, which is why i had to implement it (easy though). Having looked at the flickr, the yahoo and the google api for search request i can say that i cant stop padding the shoulder of the flickr-guys. Not only is their whole service really great but the api is as well.

Now, i cant say that developing it has been much fun so far. Sure, rails is cool when you do what its supposed to do. Like create a form which sends something and using the magic that is ajax re-renders a part of your webpage. Cool thing, and compared to writing it yourself (like in the current german it magazine c’t) it saves you a lot of time. But then you reach a point where you ask ‘how can one form call multiple methods which update multiple regions in turn’ or ‘i dont get this whole render :foo principle, why can there only be one render command?’ and finally ‘why do the flickr results take so f***ing long to render?’

[tags]ruby, rails, flickr, yahoo, search, engine, web, development[/tags]