This is more like it:Railscasts – Formtastic Part 1 and Part 2.

The Ruby Soap4R API docs at http://dev.ctor.org/doc/soap4r/ are way out of date compared to the most recent gem. Don’t use them. Use gem server to view the rdocs locally.

Some jQuery tips I came across: In the Woods: 7 Things I Wish I Had Known About jQuery

On Your Best Behavior: Prototype, LowPro, and Responsible Scripting | The Thoughts of Robots

Configuring origin master in git: git pull origin master config

Today I was having trouble installing the Curb gem on a Rails Machine 64-bit Cent OS server. Then I found this:

yum -y install krb5-devel e2fsprogs-devel libidn-devel openssl-devel
zlib-devel

Found it here:
http://groups.google.com/group/curb—ruby-libcurl-bindings/browse_thread/thread/cb50d150424b4fe5

Wondering why I couldn’t find SOAP::Mapping::LiteralRegistry and SOAP::Mapping::EncodedRegistry in the online Soap4R docs, I finally fired up the gem rdoc server. Sure enough, there they are. So, if you need to look at Soap4R’s rdocs, don’t view them online.

Because CouchDB provides an easy way to do offline replication, people can mirror your hosted application for personal use, and sync back later when they’ve made changes. –books.couchdb.org/relax/hosted-applications

This has wonderful work-flow implications compared to apps using relational databases for storage.

The more I use Cucumber on the Blacklight project, the more I like it. Sometimes, when I’m feeling lazy, it seems that it’s just taking up my time. But every time I use it I’m glad I did. Cucumber holds my hand as I write my features and scenarios. Write scenarios, watch them fail, copy-paste the output to a step, write the application code, pass, move on. When I’m done, I’ve got running code that specifies a feature and its scenarios. This really paid off the other day when I was refactoring the code behind Blacklight’s search history feature.

I’ve been using this as my introduction to Lisp: Successful Lisp. So far I’m finding it to be a wonderful resource.