Melody time Im using it daily

Melody time

Im using it daily and am fine-tuning the interaction, visuals, features, and performance. The app is now available as PeepOpen with a beautiful icon. Works with TextMate, Emacs, and MacVim. For o the r updates, follow peepcode on Twitter here. The initial prototype performs a fuzzy search on paths and lists file modification dates. You can contribute your own froth over the design and content of this article with the Neanderthals at Hacker News. The RubyAMP bundle for TextMate shows a simple list of open windows, but without fuzzy search. This article is heavily styled and is best viewed at PeepCode! DISCLAIMER: Reg Braithwaite delivered this quote in a completely different context1, but I think melody time applicable to the design of almost any software API. Illustration by Mike Rohde. The Rails router has been written and rewritten at least melody time times2, including a recent rewrite for the upcoming Rails The syntax is now more concise. But never mind making it shorter! Its time for a but I think its applicable to the design of almost any software API. Illustration by Mike Rohde. including a recent rewrite for the upcoming Rails The syntax is now more concise. But never mind making it shorter! Its time for a final rewrite : Lets get rid of it altoge the r! The ir meaning is blurred in the context of REST. The yre an unhelpful layer between programmer and protocol. Lets get rid of duplicate functionality already implemented in the controller. If you need to redirect, take action based on the user agent, or examine headers, that should be done in a controller! And lets start thinking in URLs, resources, and APIs instead of doing image caching in models or asset bundling in view helpers. Thats the controllers job. It scales better, too. Routes are unnecessary configuration. The seven standard controller actions are legacy. Become intimate with your URLs dont abstract the m away. Decrease the distance between thought and implementation. Let the controller do its job. A big part of the problem with a routing layer is that it abstracts the developer melody time from the URLs that define the application.