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!
SlickMap CSS is a simple stylesheet for displaying finished sitemaps directly from HTML unordered list navigation.
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.
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.
This is a project to make a complete replacement for the default HTML generator for Rdoc, the API documentation-extraction system for Ruby.
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.
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
Simplifies plugin testing by creating an isolated Rails environment that simulates its usage in a real application
Hirb provides a mini view framework for console applications, designed with irb in mind.
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.
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.
Pocket Informant for the iPhone doesn't just simply let you view your daily events but lets you really work with them. So many calendar or task applications are either too hard to use or too simple to be useful. Pocket Informant takes eight years of mobile experience and brings a fresh perspective to the iPhone user.
Until some future version of HTML gives us new native controls to use in a browser, at Google, we’ve been playing and experimenting with controls we call “custom buttons” in our apps (among other custom controls).