Monday, 24 December 2007

After my one-week rss detox, I was not surprised to find a 1000+ counter on my google reader. However, I couldn't digest it all an once due to (well, due to the enourmous amount of posts, but also due to) safari's memory usage growing from 17 to 250 Mb by the simple act of scrolling. As it turns out, they know about the bug already, and, well, tried to fix it. But if I understood well, they didn't succeed :/

Wednesday, 12 December 2007

Here's the story. Rake is a ruby-based DSL for building tasks. It's heavily used by Ruby on Rails, especially for database maintenance and testing. One of its use for testing is a use for testing _plugins_. The way rails does it is, well... let's say brings a few surprises.To run the tests of all plugins you enter command rake test:plugins, to run the test of a single plugin you provide an environment viariable using this syntax rake test:plugins PLUGIN=plugin_name. Now, to write a rake task that runs a subset of tests, and does some additional job, you'd set the variable from within your code and programatically invoke the test task.And this is what's not working. The problem is - all test tasks are evaluated before reading your file, and stored as a data. The particular task for running plugins simply generates all paths and stores it all in a huge hash (dictionary). After finding this out, all I was left to do was to copy rails' inner solution into my code. I don't like it much, though...

Friday, 7 December 2007

I decided to try out google new charting API. It's use is pretty straightforward - you simply a regular GET request and receive the chart in response. The nice part of it is sending actual values - you encode them as strings, so here's "helloWorld"With strings you say? Let's check it!