Posted by Fred Wu
Here’s a few things you might be interested in from the past few weeks. :-)
I have just pushed a commit that added Rails 2.x compatibility to Inherited Resources Views. Please give it a spin! :-)
It isn’t the first time realtime website traffic analysis has been introduced. Reinvigorate is one of the services that provides realtime traffic tracking and analysis.
I have just added a Github ribbon to my blog (look at the top left corner!). Please feel free to poke me! :D
Using Inherited Resources is an excellent way to reduce the amount of repetition in your controllers. But what about views? A lot of times resources share the same views, so why not DRY ‘em up using Inherited Resources Views!
In a web app, it is very common to have actions that destroy (delete/remove) data. These actions, if you don’t already know, should always map to POST methods. On top of that, because these actions are destructive, the UI should always ask the user for confirmation…
I am extremely happy that my patch was accepted, so I am now one of the 1600 odd people who have contributed to the Rails project! :D
Similarly to Action Throttler for Rails, KThrottler is an easy to use Kohana module to quickly throttle application actions based on configurable duration and limit.
Dating girls is like calling a callback function without knowing the accepted arguments. Random exceptions would throw right in your face.
Dating girls is like running prerelease ruby gems. Things might not be compatible, there might be memory leaks and other weirdnesses…
ActiveRecord is without doubt the de facto ORM library for Rails and many Ruby web frameworks. Many developers however, do not like database migrations and prefer to use DSL for data mapping. Datamappify is created with the sole purpose of getting rid of the DB migration headaches…