RubyFlow The Ruby and Rails community linklog

×

The Ruby and Rails community linklog

Made a library? Written a blog post? Found a useful tutorial? Share it with the Ruby community here or just enjoy what everyone else has found!

Submit a post

You can use basic HTML markup (e.g. <a>) or Markdown.
Note that your post may be edited to suit the format of the site.

As you are not logged in, you will be
directed via GitHub to signup or sign in

Post Preview

Note: Only the first pargraph is shown on the front page and overly long paragraphs may be broken up.

wrapr allows you to inject behavior into any existing class

Wrapr allows you to modify the behavior of any instance method (even #initialize) with before, around and after filters. The gem allows you to modify arguments before they reach instance methods and allows you intercept/modify returns. As it was originally developed to wrap Exception to trap/debug specific exceptions deep in business logic, Wrapping a base class wraps all descendant classes.

Turn to Tap Out

The wheels on the Turn bus aren’t going quite so round and round. So I decided to score my own ride. Checkout TapOut, a TAP-Y/J consumer reporting tool, and MiniTap, a TAP-Y/J reporter for MiniTest. It’s like one of those uber-cool kit cars your neighbor’s son uses to pick up the chickies. Of course, like all good mechanics, we’re still tweaking the engine a bit –mainly the current set of report formats are riding a tad thin and rough, but they’ll be polished up as time permits (feel free to grab a wrench). Peace out.

Please delete the spam.

Rails Misapprehensions: Helpers are shit.

The current helper implementation in Rails is not good. This post explains why and how to get out of this misery using draper, cells and some different approach.

apotonick, when will you stop advertising your cells plugin in every of your bl…
I second that! Rather tell us in a foul manner how bad helpers are why don’t y…

RDocodile is Dead

As of this morning, RDocodile is no more. The Ruby community showed the barest of interest in the work. Less than seven individuals took watch of the projects on GitHub. I suspect the lack of interest stems primarily from the rise of RDoc’s main competitor, YARD. I had hoped RDocodile would give some invigoration to RDoc, but the maintainer of RDoc itself gave cold reception to the whole endeavor. So I have decided to end development completely. It might seem rather unfortunate, such a large amount of good work going up in smoke, but I’m not bothered by it. Failures compose the soils of success. Instead of looking back, I look forward. And I see even better documentation pastures on the horizon.

I think you guys are having a conversation with yourselves, b/c you sure aren’t…
@zenspider what resume? I never published one. so you’re talking out your ass. …
Thomas Sawyer’s LinkedIn Résumé, which I’ve saved off as a PDF since someone li…
I remember your initial post about RDocdile. I’m sorry you ceased efforts and f…

OOP, DCI And Ruby - What Your System Is Vs. What Your System Does

Read more about why you might care about DCI (Data, Context, and Interaction — a new approach to object oriented code) in my latest post on the subject. OOP, DCI And Ruby - What Your System Is Vs. What Your System Does discusses separation of objects from the actions they perform.

Sounds like someone is changing all the happy’s to glad’s so he can be called a…
DCI is a concept created by Trygve Reenskaug, the creator of MVC. If anyone is …

Do you know Ruby Doctest?

Victor Goff’s guest blog post on RubyLearning - Do you know Ruby Doctest? explains how to document our programs using IRB sessions, resulting in a way to provide usage examples as well as knowing when an expected use fails because of some update or changes to our program or environment.

Brother if you want to write crap like this use python. With so many expressiv…
Loading older posts