This problem actually relates to any site that uses queued effects, I just ran into it on Ruby on Rails. The problem is that if you queue up too many scriptaculous effects on a dom object, you will end up having nothing displayed, or flickering or highlights that never fade etc…

Read the rest of this entry

If you have a form with some required text fields (like, name, password) then waiting for your users to hit submit is too late to tell them those fields are required. The other option is disabling the submit button until they have filled in the data, here is how…

Read the rest of this entry

If you are programming a Ruby on Rails AJAX application, you will have to handle system exceptions at some point, because if you don’t, the user gets to sit watching a spinner.gif file merrily spinning away for the rest of his or her natural existence…

Read the rest of this entry

Javascript Field Monitor

February 25th, 2008

While working on a recent Ruby on Rails project, I needed to be able to check the changes in the forms that were appearing on the page and highlight those fields on change. I looked around and couldn’t really find anything I liked, so I made one.

Read the rest of this entry

If you are using Ruby on Rails with AJAX to update parts or whole pages of your site, you will hit the history problem soon enough, luckily, with Really Simple History and Rails’ RJS templates and helpers, it becomes quite trivial to handle.

Read the rest of this entry