| require 'rubycocoa' | |
| ##### begin from drb/invokemethod.rb | |
| module DRb | |
| class DRbServer | |
| module InvokeMethod18Mixin | |
| def block_yield(x) | |
| if x.size == 1 && x[0].class == Array | |
| x[0] = DRbArray.new(x[0]) | |
| end |
| # mysql-style output for an array of ActiveRecord objects | |
| # | |
| # Usage: | |
| # report(records) # displays report with all fields | |
| # report(records, :field1, :field2, ...) # displays report with given fields | |
| # | |
| # Example: | |
| # >> report(records, :id, :amount, :created_at) | |
| # +------+-----------+--------------------------------+ | |
| # | id | amount | created_at | |
| # Add your own tasks in files placed in lib/tasks ending in .rake, | |
| # for example lib/tasks/capistrano.rake, and they will automatically be available to Rake. | |
| require(File.join(File.dirname(__FILE__), 'config', 'boot')) | |
| require 'rake' | |
| require 'rake/testtask' | |
| require 'rake/rdoctask' | |
| require 'tasks/rails' |
| # autoload concerns | |
| module YourApp | |
| class Application < Rails::Application | |
| config.autoload_paths += %W( | |
| #{config.root}/app/controllers/concerns | |
| #{config.root}/app/models/concerns | |
| ) | |
| end | |
| end |
| # 0 is too far from ` ;) | |
| set -g base-index 1 | |
| # Automatically set window title | |
| set-window-option -g automatic-rename on | |
| set-option -g set-titles on | |
| #set -g default-terminal screen-256color | |
| set -g status-keys vi | |
| set -g history-limit 10000 |
It's pretty easy to do polymorphic associations in Rails: A Picture can belong to either a BlogPost or an Article. But what if you need the relationship the other way around? A Picture, a Text and a Video can belong to an Article, and that article can find all media by calling @article.media
This example shows how to create an ArticleElement join model that handles the polymorphic relationship. To add fields that are common to all polymorphic models, add fields to the join model.
| #!/usr/bin/env ruby | |
| # A script that will pretend to resize a number of images | |
| require 'optparse' | |
| # This hash will hold all of the options | |
| # parsed from the command-line by | |
| # OptionParser. | |
| options = {} | |
| optparse = OptionParser.new do|opts| |
On Tue, Mar 12, 2013 at 1:26 PM, Martin Fowler [email protected] wrote:
The term pops up in some different places, so it's hard to know what it means without some context. In PoEAA I use the pattern Service Layer to represent a domain-oriented layer of behaviors that provide an API for the domain layer. This may or may not sit on top of a Domain Model. In DDD Eric Evans uses the term Service Object to refer to objects that represent processes (as opposed to Entities and Values). DDD Service Objects are often useful to factor out behavior that would otherwise bloat Entities, it's also a useful step to patterns like Strategy and Command.
It sounds like the DDD sense is the sense I'm encountering most often. I really need to read that book.
The conceptual problem I run into in a lot of codebases is that rather than representing a process, the "service objects" represent "a thing that does the process". Which sounds like a nitpicky difference, but it seems to have a real impact on how people us
| class Contact < ActiveRecord::Base | |
| ... | |
| def after_create | |
| if Hook.hooks_exist?('new_contact', self) | |
| Resque.enqueue(Hook, self.class.name, self.id) | |
| # To trigger directly without Resque: Hook.trigger('new_contact', self) | |
| end | |
| end |
