Welcome to this week's Ruby Weekly , the e-mail newsletter.syndication of
Highlights include: MagicRuby 2012, a code structure/patterns 'drama', Mark Bates' new a ) conference!book, minitest 3.2.0, and the chatting with Jim Weirich (who I met for the first time this week, ironically at
Before I start this article, let me apologize for the lack of writing over the last six months. My only excuse is that I've been working on a new book and that is where all my writing energy has gone. So with apologies out of the way, let's talk pagination.
Dealing with pagination in any application is never easy. There are a lot of great libraries out there that help you better handle this awkward, but unavoidable part of application programming. Things get even more complicated when you are trying to define an API.
I've started working this week on an example application for the next book I'm about to write and I wanted a simple way for my readers to easily run the app (it's going to be a single Rack . If you are unfamiliar with , please check it out. It provides a simple interface for writing web applications. By writing a simple Ruby file …file with a ton of cool going on in it). My first choice for running this app was to use the popular library,
Mark Bates shows how to usein your views.
The of the Library
posts on the blog about what makes a good library.
TDD in with MacRuby
Joshua Ballanco walks through creating a pig latin translator in objective c usingto .
exposes all of 's most powerful search features using an of elegant DSLs. That means robust, flexible fulltext search with no …
Mark Bates, over on the Meta Bates blog, introduceswhich he describes as "what wish they could be, and more!" A Warp Drive is a standard, full featured, Rails application that you can easily bundle up into a , and include into another Rails .
Nathan Esquenazi has posted some common cap recipes on hisaccount. There are recipes for Ruby, Passenger, , and more.
Last night I had the pleasure of presenting to the Boston on 's Group . My talk was geared to helping understand, and hopefully love, CoffeeScript. Along the way I tried to debunk a few myths and preconceptions as to what CoffeeScript is and isn't. The reaction was really positive, so hopefully I did my job. Anyway, here are the slides:
I have to ask a question to my fellow Rubyists out there? Why are you still using YAML? I know why you think you like YAML. You think it's a great way to write configuration files, but it's really not. You know what's a great way of writing configuration files for Ruby apps? RUBY!
I know it's crazy, isn't it? But why not? Why would you not want to use Ruby for configuring your applications instead of YAML?
I'm the maintainer of a pretty popular configuration …
Twitter is an incredibly rich source of information. I find out about new libraries, applications, plugins, screen casts, etc... But, there's a problem with is overwhelming amount of information... keeping track of it all. A lot of time I read Twitter when I'm on my phone. I'll see a link to an article or website, etc... but I don't have time to read it then, what do I do? How do I find that tweet later? Or what about that announcement or news link for a new service or application …
About six weeks ago I announced FluxTracker.com a unified issue, document, and error management service. The response has been amazing. People love that you can now manage all of those things in one place, without any configuration. Well, today I'm happy to announce that FluxTracker has taken the next step forward to make managing all aspects of your project easier. Introducing FluxTracker Feedback .
FluxTracker Feedback allows you to put a little feedback widget …
Because I maintain several open source projects on Github I'm constantly getting emailed questions or issues, or people are always opening up tickets with bugs, issues, complaints, etc... And I really appreciate the feedback on these projects, I really do. What I would appreciate more is if instead of just opening a ticket, or sending an email, why not fork the project, fix it, and then contact me?
Now, I know that sounds like a lot of work, but honestly it's really not.…