I just finished reviewing Rails 2.3 Nested Object Forms. While a very nice and “magical” feature, I’ve got to admit that I’m really not that crazy about how it works.

Rails’ script/console makes it easy to fetch, view and edit your database records. But can you edit those records as quickly as you edit code in your text editor? Riiight, like editing our database records in an editor is gonna happen? It already has.

Hirb provides a mini view framework for console applications, designed with irb in mind.

HTML sanitizer by the wonko.com guy.

I believe that the current specification of the element is vague because it avoids the question whether the element is safe for historians. Right now it hurts historical research more than it helps

So, as a result, people using RESTful ideas to talk to browsers have to put the smarts back on the server. They invent new URLs which (for example) return a resource, but return it all wrapped up in the HTML needed to display it as a form for browser-based editing.

This is a project to make a complete replacement for the default HTML generator for Rdoc, the API documentation-extraction system for Ruby.

Hanna is an RDoc template that scales. It's implemented in Haml, making the sources clean and readable. It's built with simplicity, beauty and ease of browsing in mind.

Porter is essentially the inverse of X-SendFile. It parses the multipart post in C inside your apache process and writes the files to disk. Once that work is done it changes the request to look like a regular form POST which contains pointers to the temp files on disk.

SlickMap CSS is a simple stylesheet for displaying finished sitemaps directly from HTML unordered list navigation.

Highslide JS is an open source image, media and gallery viewer written in JavaScript.

In a nutshell, Bowline lets you build cross platform desktop applications with Ruby, HTML and JavaScript. The idea is to make building desktop apps as simple (and fun) as building Rails websites.

View testing that doesn't suck.

It's important, however, that his wonderful code live on, and we need your help to do so. We've mirrored what repos we could find and contacted github tech support, who have promised assistance. Whymirror will do what it can to ease the transition but CANNOT be a long-term solution

The same problem happened with address, which was specified to mean only the contact information for the author of a page. It was quite explicitly specified to not accept mailing addresses. Of course, tons of people did just that, because they had an address and there was an address element, so of course they went together!

Amidst my 400 unread Boing Boing links are probably ten or fifteen that are probably real gems. But I’ll never know and Boing Boing sure as hell isn’t going to help me out.

validate( "email".is("required").andIsAn("email") );

Even though the gradual engagement meme has been around for a while, and everyone just hates signup forms, they just seem to keep popping up like a bad habit.

cxpartners has an interesting eye tracking study on form design. They distill the results into a few simple guidelines which are definitely worth keeping in mind when designing forms.

MailStyle allows you to write the css for your html emails as you normally would, then writes the styles inline when you send your emails. It also makes sure that your image paths are absolute rather than relative.

In order to lower friction and the hurdles to pass, users need to be provided with a reason to trust you with the information they supply. The time and effort required to complete a form should be appropriate for the task at hand. A constant battle between the reward for completing an action and the effort it takes to complete it, is at play at all times.

We simply convert your design (PSD, PNG, AI, etc.) into a hand coded, pixel perfect and Standards compliant XHTML/CSS. Since our service is targeted to agencies and freelancers the job done by us is 100% confidential. In addition we are offering payment after satisfaction.