| <?php | |
| if ( is_singular('product') ) { | |
| global $post; | |
| // get categories | |
| $terms = wp_get_post_terms( $post->ID, 'product_cat' ); | |
| foreach ( $terms as $term ) $cats_array[] = $term->term_id; |
| # MOTIVATION: As rails apps are growing, people are noticing the drawbacks | |
| # of the ActiveRecord pattern. Several apps I have seen, and several | |
| # developers I have spoken to are looking towards other patterns for object | |
| # persistence. The major drawback with ActiveRecord is that the notion | |
| # of the domain object is conflated with what it means to store/retrieve | |
| # it in any given format (like sql, json, key/value, etc). | |
| # | |
| # This is an attempt to codify the Repository pattern in a way that would | |
| # feel comfortable to beginner and seasoned Ruby developers alike. | |
| # |
| # | |
| # Scopes for date attribute | |
| # https://gist.github.com/2235839 | |
| # | |
| module Common::DateScope | |
| extend ActiveSupport::Concern | |
| included do | |
| unless respond_to?(:year) |
| /* Exercise: Loops and Functions #43 */ | |
| package main | |
| import ( | |
| "fmt" | |
| "math" | |
| ) | |
| func Sqrt(x float64) float64 { | |
| z := float64(2.) |
| #!/usr/bin/env ruby | |
| require 'active_record' | |
| ActiveRecord::Base.establish_connection( | |
| :adapter => 'sqlite3', | |
| :database => ':memory:' | |
| ) | |
| ActiveRecord::Schema.define do |
| source :rubygems | |
| gem "sinatra", "~> 1.3.2" | |
| group :test do | |
| gem "minitest", "~> 2.10" | |
| gem "rack-test", "~> 0.6.1" | |
| gem "capybara", "~> 1.1" | |
| gem "capybara-webkit", "~> 0.11" | |
| gem "capybara_minitest_spec", "~> 0.2" |
Ok, I geeked out, and this is probably more information than you need. But it completely answers the question. Sorry. ☺
Locally, I'm at this commit:
$ git show
commit d6cd1e2bd19e03a81132a23b2025920577f84e37
Author: jnthn <[email protected]>
Date: Sun Apr 15 16:35:03 2012 +0200
When I added FIRST/NEXT/LAST, it was idiomatic but not quite so fast. This makes it faster. Another little bit of masak++'s program.
I have always struggled with getting all the various share buttons from Facebook, Twitter, Google Plus, Pinterest, etc to align correctly and to not look like a tacky explosion of buttons. Seeing a number of sites rolling their own share buttons with counts, for example The Next Web I decided to look into the various APIs on how to simply return the share count.
If you want to roll up all of these into a single jQuery plugin check out Sharrre
Many of these API calls and methods are undocumented, so anticipate that they will change in the future. Also, if you are planning on rolling these out across a site I would recommend creating a simple endpoint that periodically caches results from all of the APIs so that you are not overloading the services will requests.
| group :assets do | |
| gem 'sass-rails' | |
| gem 'coffee-rails' | |
| gem 'uglifier' | |
| gem 'yui-compressor' | |
| gem 'compass-rails' | |
| end |
| class Chromosome | |
| attr_accessor :bitstring | |
| def fitness | |
| @fitness = @bitstring ^ 0b0101 | |
| end | |
| def self.random_chromosomes(length, number) | |
| return Array.new(length) { Chromosome.new(length) } | |
| end |
