/explore
|
You are here 
|
pbrisbin.com | ||
| | | | |
thomascountz.com
|
|
| | | | | Adding Functionality to Client Classes The first step in tackling this problem is to add functionality to a model class. If we have a class Book, we want to add a class method Book.find , and some instance methods book#title, book#author, and book#isbn, without needed to explicitly write them, like we did in the original spike. A Note on Mix-Ins & Inheritance When you want to create a model with ActiveRecord, you have to inherit from the Base module: class Book < ActiveRecord::Base; end There are endless debates about composition v. inheritance, and, from my perspective, they all mostly lean towards composition, but what about using mix-ins versus using string inheritance? In Ruby, inheriting and including a module both add a new entity in the method look-up... | |
| | | | |
www.railstips.org
|
|
| | | | | ||
| | | | |
thepugautomatic.com
|
|
| | | | | I recently discovered the Ruby Module Builder pattern. It lets you pass in arguments to dynamically generate a module at include time: class Greeter < Module def initialize(name)... | |
| | | | |
blog.martinig.ch
|
|
| | | Architecture is an important asset for good programming and the notion of "pattern" is here to help us apply already trusted code architecture solutions to common problems. Jason McDonald has done a wonderful job to group some of them in a document that should be useful to most software developers. Go to his blog to | ||
