<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/" xmlns:georss="http://www.georss.org/georss"><id>tag:blogger.com,1999:blog-8941983</id><updated>2009-09-09T03:59:03.676+04:00</updated><title type="text">Kir's blog</title><subtitle type="html" /><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://feeds2.feedburner.com/idetalk/xSAl" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/" /><link rel="hub" href="http://pubsubhubbub.appspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default?start-index=26&amp;max-results=25" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>46</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><link rel="self" href="http://feeds.feedburner.com/idetalk/xSAl" type="application/atom+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry><id>tag:blogger.com,1999:blog-8941983.post-5518480460943814358</id><published>2009-08-22T10:56:00.004+04:00</published><updated>2009-08-22T11:07:44.226+04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="RubyOnRails" /><category scheme="http://www.blogger.com/atom/ns#" term="Checkvist" /><category scheme="http://www.blogger.com/atom/ns#" term="Rails" /><title type="text">Checkvist Pro plan</title><summary type="text">After a long silence, we've finally released Checkvist Pro plan. The detailed post about this is available.With this release, I've also upgraded Rails to the version 2.3.3 and migrated Mysql database from MyISAM to InnoDB engine (because we've had problems with data consistency when transactions were interrupted).So far so good, performance haven't become worse. And I'm pretty satisfied with </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/5518480460943814358/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=5518480460943814358&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/5518480460943814358" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/5518480460943814358" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2009/08/checkvist-pro-plan.html" title="Checkvist Pro plan" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-7522830323397209149</id><published>2009-04-12T21:45:00.004+04:00</published><updated>2009-04-12T22:01:01.701+04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="RubyOnRails" /><category scheme="http://www.blogger.com/atom/ns#" term="Checkvist" /><category scheme="http://www.blogger.com/atom/ns#" term="Rails" /><title type="text">Migration of Checkvist to Rails 2.3</title><summary type="text">I decided to migrate Checkvist to new and fresh Rails 2.3 (or 2.3.2, to be more specific).I cannot say I really need features from 2.3, but I think it worth using the latest release (especially given that I already had to patch my Rails 2.2.2 installation to remove some bugs from it). As usual, the migration turns to be an adventure: Change all tests which extend Test::Unit::TestCase and use </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/7522830323397209149/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=7522830323397209149&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/7522830323397209149" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/7522830323397209149" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2009/04/migration-of-checkvist-to-rails-23.html" title="Migration of Checkvist to Rails 2.3" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-6824248179192972400</id><published>2009-03-18T12:29:00.003+03:00</published><updated>2009-03-18T12:47:58.641+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Checkvist" /><category scheme="http://www.blogger.com/atom/ns#" term="monit monitoring" /><title type="text">Monit start/stop problem from the command line</title><summary type="text">Monit is a great tool to monitor various UNIX-like services and to take appropriate actions when they fail. And I've been using it with a great success to monitor Checkvist server. But, as with any tool, there are some issues. I've spent some noticeable time trying to figure out why monit's command line actions do not work. All of the start, stop, restart actions did nothing. Monit's log didn't </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/6824248179192972400/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=6824248179192972400&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/6824248179192972400" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/6824248179192972400" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2009/03/monit-startstop-problem-from-command.html" title="Monit start/stop problem from the command line" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-5694116816219841028</id><published>2009-03-13T20:50:00.004+03:00</published><updated>2009-03-18T14:24:14.686+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="IntelliJ IDEA" /><category scheme="http://www.blogger.com/atom/ns#" term="TeamCity" /><title type="text">JetBrains gone twitting</title><summary type="text">Recently I've created a twitter account with basic purpose to provide some support for JetBrains TeamCity and Checkvist.Many JetBrainers actively twit and provide product support as well.Today, you may find twitter account for most  JetBrains products: IntelliJ IDEA Resharper RubyMine TeamCity dotTraceThese accounts a pretty new, but in the long run you'll find a lot of interesting stuff in these</summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/5694116816219841028/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=5694116816219841028&amp;isPopup=true" title="5 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/5694116816219841028" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/5694116816219841028" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2009/03/jetbrains-gone-twitting.html" title="JetBrains gone twitting" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-6953870275330825207</id><published>2009-01-09T23:15:00.003+03:00</published><updated>2009-01-10T00:17:43.794+03:00</updated><title type="text">Standalone Windows Mobile emulator setup</title><summary type="text">I've spent several hours trying to setup and run windows mobile emulator (we're working on mobile UI for Checkvist), and here is the essence of my experience:Don't try to run this emulator under Parallels / Mac OS if you need to get a working network under the emulator. This is due to the fact that emulator uses Virtual PC functionality for setting up network, and it is not compatible with </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/6953870275330825207/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=6953870275330825207&amp;isPopup=true" title="3 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/6953870275330825207" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/6953870275330825207" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2009/01/standalone-windows-mobile-emulator.html" title="Standalone Windows Mobile emulator setup" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-824604874450988241</id><published>2009-01-09T22:43:00.004+03:00</published><updated>2009-01-09T23:14:56.727+03:00</updated><title type="text">nginx, Analog stats, LOGFORMAT</title><summary type="text">Currently, I'm using nginx web server for the Checkvist project. And have the following definition for the access log format (from The Rails Way book):    log_format  main  '$remote_addr - $remote_user [$time_local] $request '                  '"$status" $body_bytes_sent "$http_referer" '                  '"$http_user_agent" "$http_x_forwarded_for"';Today I decided to create a quick and dirty </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/824604874450988241/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=824604874450988241&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/824604874450988241" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/824604874450988241" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2009/01/nginx-analog-stats-logformat.html" title="nginx, Analog stats, LOGFORMAT" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-321353502101219315</id><published>2008-11-30T22:58:00.007+03:00</published><updated>2008-12-03T21:10:19.967+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Ruby" /><category scheme="http://www.blogger.com/atom/ns#" term="demo" /><category scheme="http://www.blogger.com/atom/ns#" term="RubyOnRails" /><category scheme="http://www.blogger.com/atom/ns#" term="TeamCity" /><category scheme="http://www.blogger.com/atom/ns#" term="Checkvist" /><category scheme="http://www.blogger.com/atom/ns#" term="Rails" /><category scheme="http://www.blogger.com/atom/ns#" term="Continuous Integration" /><title type="text">TeamCity 4.0 runs Checkvist's tests</title><summary type="text">I'm working on two projects: TeamCity - a rather popular continuous integration and build management server, and Checkvist - a simple and fast online outliner with task sharing and keyboard navigation.I use Checkvist to plan my work on TeamCity, and recently I got a chance to use TeamCity to assist Checkvist development.TeamCity recently reached its next milestone - 4.0 release. One of the </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/321353502101219315/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=321353502101219315&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/321353502101219315" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/321353502101219315" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2008/11/teamcity-40-runs-checkvists-tests.html" title="TeamCity 4.0 runs Checkvist's tests" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-3740074930526775556</id><published>2008-08-03T21:33:00.005+04:00</published><updated>2008-08-05T22:07:51.518+04:00</updated><title type="text">We named it Checkvist</title><summary type="text">We've finally decided to open public registration for our pet project. This is an online task management service, similar to those already available on the Web (like RTM or todoist).  What's the difference? We're trying to make a tool which allows Work fast. From the very beginning, we strive to provide usable keyboard navigation around checklists.  Work together. You can share a checklist, add </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/3740074930526775556/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=3740074930526775556&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/3740074930526775556" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/3740074930526775556" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2008/08/we-named-it-checkvist.html" title="We named it Checkvist" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-2593236397891685621</id><published>2008-04-28T13:42:00.000+04:00</published><updated>2008-04-28T14:48:01.018+04:00</updated><title type="text">TeamCity developer blog</title><summary type="text">TeamCity team has decided that it might be a good idea to have an own "unofficial" developer blog. It's a kind of experiment, because most developer's  time is spent on, well, developing. But sometimes it is enticing to share some ideas, findings, tell about a feature which will be available in the next EAP build. And this stuff may be too "unofficial"  and personal to go to the main product </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/2593236397891685621/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=2593236397891685621&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/2593236397891685621" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/2593236397891685621" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2008/04/teamcity-developer-blog.html" title="TeamCity developer blog" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-7546263433586248142</id><published>2008-04-22T23:29:00.003+04:00</published><updated>2008-04-23T11:58:54.478+04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Javascript" /><title type="text">href value for javascript link anchor</title><summary type="text">If you create a link with javascript handler, and href attribute doesn't matter for you, do not use # as the value of the attribute. This results in page scrolling to the top of the page in MSIE. Instead, use value like javascript:// - this is safe and most browsers will ignore it. And this is what you want when you have an onclick handler, isn't it?Update: I was pointed out, that if javascript </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/7546263433586248142/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=7546263433586248142&amp;isPopup=true" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/7546263433586248142" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/7546263433586248142" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2008/04/href-value-for-javascript-link-anchor.html" title="href value for javascript link anchor" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-8764455193873679664</id><published>2008-02-24T14:47:00.011+03:00</published><updated>2008-02-24T22:11:56.395+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="performance" /><category scheme="http://www.blogger.com/atom/ns#" term="Javascript" /><category scheme="http://www.blogger.com/atom/ns#" term="CSS" /><title type="text">Internet Explorer rendering problems or how to repaint Web-page</title><summary type="text">A short prelude.I'm developing a small checklist application, to study ruby/rails and to play with various Web 2.0 UI patterns. And to get a tool which will help me to organize all my todos.On the checklist screen I have, guess what - list of tasks, the checklist is comprised of. On some actions (like completing a task) the tasks are updated incrementally (with plain Javascript), on some actions </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/8764455193873679664/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=8764455193873679664&amp;isPopup=true" title="5 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/8764455193873679664" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/8764455193873679664" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2008/02/internet-explorer-rendering-problems-or.html" title="Internet Explorer rendering problems or how to repaint Web-page" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-4228996956034655792</id><published>2008-01-12T18:38:00.000+03:00</published><updated>2008-01-12T20:47:12.703+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="TeamCity" /><title type="text">TeamCity: immediate test failure notifications</title><summary type="text">This feature is particularly useful, if you have lengthy builds.With most continuous integration tools, one have to wait until build is finished to get notified about test failure. TeamCity can send notification right after test failure, before build completion.Scenario Developer commits a change Build is started A test failsNotification "Build is failing" is sent to the developer and to other </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/4228996956034655792/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=4228996956034655792&amp;isPopup=true" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/4228996956034655792" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/4228996956034655792" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2008/01/teamcity-immediate-test-failure.html" title="TeamCity: immediate test failure notifications" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-1984063177747083289</id><published>2007-12-06T13:11:00.000+03:00</published><updated>2007-12-07T02:36:20.767+03:00</updated><title type="text">What I like about TeamCity: Pre-tested commit</title><summary type="text">I am one of the TeamCity developers so you can surely consider my opinion to be biased. But I am speaking here of a typical problems that any of you can experience and will try not to brag about my product too much ;-)I'm a software developer. And though TeamCity is not an individual tool like IntelliJ IDEA, I'd like to present TeamCity features which ease my life as a software </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/1984063177747083289/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=1984063177747083289&amp;isPopup=true" title="5 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/1984063177747083289" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/1984063177747083289" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2007/12/what-i-like-about-teamcity-pre-tested.html" title="What I like about TeamCity: Pre-tested commit" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-4079983495428059312</id><published>2007-10-04T12:28:00.000+04:00</published><updated>2007-10-04T12:42:19.270+04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Javascript" /><category scheme="http://www.blogger.com/atom/ns#" term="CSS" /><title type="text">Problem with offsetTop and element position location in IE</title><summary type="text">This is just a small note for someone looking into a similar problem. I was implementing keyboard navigation with explicit scrolling using scrollTo method, and found out that in IE I cannot get correct values for element position on the page. I use Prototype and it's Position.cumulativeOffset method (which, in turn, uses offetTop/offsetParent properties of the element). Position calculation </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/4079983495428059312/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=4079983495428059312&amp;isPopup=true" title="8 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/4079983495428059312" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/4079983495428059312" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2007/10/problem-with-offsettop-and-element.html" title="Problem with offsetTop and element position location in IE" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">8</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-132709889813763922</id><published>2007-09-09T14:47:00.000+04:00</published><updated>2007-09-10T14:55:55.862+04:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="RubyOnRails" /><title type="text">How to run rake tasks for non-development rails environments</title><summary type="text">I’ve found that parameters passed to rake tasks in the form “name=value” are converted into the environment variables. This magic is done by rake itself when parsing command-line parameters. It has an interesting consequence – you can run some db-oriented rake tasks for any of your ruby on rails environments. For instance, to migrate your production database to the latest version you can run:rake</summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/132709889813763922/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=132709889813763922&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/132709889813763922" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/132709889813763922" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2007/09/how-to-run-rake-tasks-for-non.html" title="How to run rake tasks for non-development rails environments" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-1633774003382965086</id><published>2007-03-01T16:15:00.000+03:00</published><updated>2007-03-01T17:23:34.659+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="TeamCity" /><title type="text">How EAP works</title><summary type="text">I'm really excited how TeamCity EAP program works. Using our discussion forum, people report bug, problems, enhancements, features, ask for and got real help. We're trying hard to answer all questions and requests, and though it takes noticeable time, it's worth doing it.One small example.Some time ago we got a message from Jacques Morel regarding support for third-party reporting tools in </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/1633774003382965086/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=1633774003382965086&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/1633774003382965086" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/1633774003382965086" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2007/03/how-eap-works.html" title="How EAP works" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-890770059312711160</id><published>2007-01-31T18:09:00.000+03:00</published><updated>2007-02-07T19:40:08.690+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="TeamCity" /><title type="text">Agra: popups everywhere</title><summary type="text">Just a couple of screenshots from the latest EAP of TeamCity.Quick access to artifacts:Quick access to the list of failed tests:TeamCity continuous integration Ajax Web 2.0</summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/890770059312711160/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=890770059312711160&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/890770059312711160" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/890770059312711160" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2007/01/agra-popups-everywhere.html" title="Agra: popups everywhere" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-254830275060701841</id><published>2007-01-26T10:58:00.000+03:00</published><updated>2007-01-26T11:13:28.112+03:00</updated><title type="text">Humanized and Enzo</title><summary type="text">I've read about that tool at 37 Signals and watched the short demo. I should say it looks brilliant.  Quite obvious for Mac users but it is first time I see such a good implementation on Windows.In fact, they put to life "Command" button inspired by Jeff Raskin in his The Humane Interface book. The implementation is simple, and very impressive - they just use "Caps Lock" key as such "Command" </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/254830275060701841/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=254830275060701841&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/254830275060701841" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/254830275060701841" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2007/01/humanized-and-enzo.html" title="Humanized and Enzo" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-9098335206743842680</id><published>2006-11-21T00:17:00.000+03:00</published><updated>2006-11-21T00:27:07.656+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="TeamCity" /><title type="text">Release woes</title><summary type="text">Shit happens. You've prepared final release build, marked it as 1.1 and put on the site. Next day a couple of people from your company comes - they found an unnoticed critical bug. Because of strange consequence of events this bug wasn't noticed before.    Bug is fixed, new 1.1.1 build is uploaded to the main site, build number is corrected.  Next day you got an e-mail from support with message "</summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/9098335206743842680/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=9098335206743842680&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/9098335206743842680" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/9098335206743842680" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2006/11/release-woes.html" title="Release woes" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-116185115421816328</id><published>2006-10-26T12:25:00.000+04:00</published><updated>2006-11-11T20:30:49.013+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Books" /><title type="text">Getting Real, free</title><summary type="text">A highly recommended reading for everyone involved in software development. Now you may read it free in HTML: Getting Real (37signals)</summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/116185115421816328/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=116185115421816328&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/116185115421816328" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/116185115421816328" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2006/10/getting-real-free.html" title="Getting Real, free" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-116179119490269550</id><published>2006-10-25T19:39:00.000+04:00</published><updated>2006-11-11T20:30:48.767+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="IDEtalk" /><title type="text">IDEtalk goes open source</title><summary type="text">Just a small note - IDEtalk project goes open source.It's repository is located at http://svn.jetbrains.org/idea/Trunk/IDEtalk/,so you can view code, fix bugs and participate if you wish.I'll continue work on it, though I cannot spend much time becauseof another cool project I'm working on.Have no idea when I'll update main IDEtalk site.</summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/116179119490269550/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=116179119490269550&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/116179119490269550" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/116179119490269550" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2006/10/idetalk-goes-open-source.html" title="IDEtalk goes open source" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-115083339392378746</id><published>2006-06-20T23:43:00.000+04:00</published><updated>2006-11-11T20:30:48.553+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="TeamCity" /><title type="text">Safari JavaScript problems</title><summary type="text">Today I spent several hours fixing various bugs in Team Server for another EAP release, and two of them concerned Javascript issues in the Safari browser.The first issue:  In Safari you cannot specify the location of an absolutely positioned element if this element has display:none. I had a code which set style.left and style.top of a hidden div and then showed it on the screen. It worked fine in</summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/115083339392378746/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=115083339392378746&amp;isPopup=true" title="4 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/115083339392378746" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/115083339392378746" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2006/06/safari-javascript-problems.html" title="Safari JavaScript problems" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-114513549597203167</id><published>2006-04-16T00:51:00.000+04:00</published><updated>2006-11-11T20:30:48.343+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="TeamCity" /><title type="text">Team Server: Remote Run functionality</title><summary type="text">To be honest, I didn't believe that this feature will be implemented in the first version of the Team Server.But now it is real - with the latest EAP of Demetra and Team Server a developer can integrate and run build with own changes without commiting them to version control system!The implementation is not perfect - but it works and surely will be improved. On the forum you can read how to setup</summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/114513549597203167/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=114513549597203167&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/114513549597203167" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/114513549597203167" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2006/04/team-server-remote-run-functionality.html" title="Team Server: Remote Run functionality" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-113908927860874145</id><published>2006-02-04T23:59:00.000+03:00</published><updated>2006-11-11T20:30:47.884+03:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="IntelliJ IDEA" /><title type="text">Unit test for IntelliJ IDEA plugin: load complex project</title><summary type="text">Recently Hugo Palma had a problem with writing a unit test for his IDEA plugin. What he needed was a custom project configuration with a web module.Actually, IDEA's OpenAPI does not allow to load project from disk (so far). But there is a way to do it using closed API. I've wrote a small example which shows how to write such a test, but remember, there is no guarantee that this code will work </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/113908927860874145/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=113908927860874145&amp;isPopup=true" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/113908927860874145" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/113908927860874145" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2006/02/unit-test-for-intellij-idea-plugin.html" title="Unit test for IntelliJ IDEA plugin: load complex project" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8941983.post-113761010458794276</id><published>2006-01-18T21:42:00.002+03:00</published><updated>2008-06-01T19:56:18.275+04:00</updated><title type="text">Export b2evolution  to Movable Type</title><summary type="text">Just a small note. Recently I've migrated Sashblog from b2evolution to Movable Type. To accomplish this, I wrote an export script for b2evolution database, which prepares data in format Movable Type can understand. The script exports published entries and comments to them.What's wrong with b2? The primary reason - bad spam protection and publicly available statistics, which opens a hole for </summary><link rel="replies" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/113761010458794276/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="https://www.blogger.com/comment.g?blogID=8941983&amp;postID=113761010458794276&amp;isPopup=true" title="6 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/113761010458794276" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/8941983/posts/default/113761010458794276" /><link rel="alternate" type="text/html" href="http://kirblog.idetalk.com/2006/01/export-b2evolution-to-movable-type.html" title="Export b2evolution  to Movable Type" /><author><name>Kir Maximov</name><uri>http://www.blogger.com/profile/11739397709323043771</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd="http://schemas.google.com/g/2005" name="OpenSocialUserId" value="02758259113327663730" /></author><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">6</thr:total></entry></feed>
