2010 July | DevInterface Blog

6

COMMENTS

Design Patterns in Ruby: Chain of Responsibility

09:53 AM Stefano

Today’s post discusses the first of the behavioral pattern shown by the GoF, the chain of responsibility.

This pattern expects a series of commands to be executed and a set of objects capable to handle them.
Each of these “handler” objects can send the command to the next handler in the chain if it is not able [...]

Share on:

Add 'Design Patterns in Ruby: Chain of Responsibility' to Del.icio.us

Add 'Design Patterns in Ruby: Chain of Responsibility' to digg

Add 'Design Patterns in Ruby: Chain of Responsibility' to reddit

Add 'Design Patterns in Ruby: Chain of Responsibility' to Technorati

Add 'Design Patterns in Ruby: Chain of Responsibility' to Stumble Upon

Add 'Design Patterns in Ruby: Chain of Responsibility' to Google Bookmarks

Add 'Design Patterns in Ruby: Chain of Responsibility' to Rojo

Add 'Design Patterns in Ruby: Chain of Responsibility' to OKnotizie

Add 'Design Patterns in Ruby: Chain of Responsibility' to Diggita

Add 'Design Patterns in Ruby: Chain of Responsibility' to FaceBook

Add 'Design Patterns in Ruby: Chain of Responsibility' to Upnews

Add 'Design Patterns in Ruby: Chain of Responsibility' to Twitter

Add 'Design Patterns in Ruby: Chain of Responsibility' to Technotizie

Add 'Design Patterns in Ruby: Chain of Responsibility' to FriendFeed

Add 'Design Patterns in Ruby: Chain of Responsibility' to Google Buzz

Tags: design patterns, ruby, ruby on rails
Posted in Development, Metodologies, Ruby |

GO

14

COMMENTS

Rails Best Practices 3: Increase Controller’s readability

10:45 AM Claudio

[POST UPDATE ON 19/07/2010 - 15:45]
Continuing our analysis of the Rails Best Practices today we’ll see two other tricks to make more readable method of the controller.
1. Methods within model
Suppose we have the classic user registry defined in such a way that an admin user can enable or disable other users.
The deactivate method inside user [...]

Share on:

Add 'Rails Best Practices 3: Increase Controller’s readability' to Del.icio.us

Add 'Rails Best Practices 3: Increase Controller’s readability' to digg

Add 'Rails Best Practices 3: Increase Controller’s readability' to reddit

Add 'Rails Best Practices 3: Increase Controller’s readability' to Technorati

Add 'Rails Best Practices 3: Increase Controller’s readability' to Stumble Upon

Add 'Rails Best Practices 3: Increase Controller’s readability' to Google Bookmarks

Add 'Rails Best Practices 3: Increase Controller’s readability' to Rojo

Add 'Rails Best Practices 3: Increase Controller’s readability' to OKnotizie

Add 'Rails Best Practices 3: Increase Controller’s readability' to Diggita

Add 'Rails Best Practices 3: Increase Controller’s readability' to FaceBook

Add 'Rails Best Practices 3: Increase Controller’s readability' to Upnews

Add 'Rails Best Practices 3: Increase Controller’s readability' to Twitter

Add 'Rails Best Practices 3: Increase Controller’s readability' to Technotizie

Add 'Rails Best Practices 3: Increase Controller’s readability' to FriendFeed

Add 'Rails Best Practices 3: Increase Controller’s readability' to Google Buzz

Tags: Best Practices, controller, factory method, ruby on rails
Posted in Development, Metodologies, Ruby |

GO

5

COMMENTS

Design Patterns in Ruby: Adapter

12:13 PM Stefano

This second post of the series leaves for a moment the creational patterns and speaks about one of the most important structural pattern: the Adapter.

The purpose of an adapter is “to convert the interface of a class into another interface clients expect. Adapter lets classes work together that couldn’t otherwise because of incompatible interfaces.”

Suppose therefore [...]

Share on: