clearance 的 generator

clearance
Class Rails::Generator::Commands::Create


<br />#這邊是需要的library <br />require File.expand_path(File.dirname(__FILE__) + "/lib/insert_commands.rb") <br />require File.expand_path(File.dirname(__FILE__) + "/lib/rake_commands.rb") <br />require 'factory_girl' <br /> <br />class ClearanceGenerator < Rails::Generator::Base <br /> <br /> def manifest <br /> record do |m| <br /> # 原來可以這樣insert GOOD <br /> m.insert_into "app/controllers/application_controller.rb", <br /> "include Clearance::Authentication" <br /> <br /> user_model = "app/models/user.rb" <br /> if File.exists?(user_model) <br /> m.insert_into user_model, "include Clearance::User" <br /> else <br /> #原來也可以生目錄 <br /> m.directory File.join("app", "models") <br /> m.file "user.rb", user_model <br /> end <br /> <br /> m.directory File.join("test", "factories") <br /> m.file "factories.rb", "test/factories/clearance.rb" <br /> <br /> #還可以選擇用哪個file migrate, 叫啥名字 <br /> m.migration_template "migrations/#{migration_name}.rb", <br /> 'db/migrate', <br /> :migration_file_name => "clearance_#{migration_name}" <br /> <br /> m.readme "README" <br /> end <br /> private <br /> <br /> def migration_name <br /> #可以check table 在不在 <br /> if ActiveRecord::Base.connection.table_exists?(:users) <br /> 'update_users' <br /> else <br /> 'create_users' <br /> end <br /> end <br /> <br />end <br /> <br />#-------------------------------------------------- <br />Rails::Generator::Commands::Create.class_eval do <br /> def insert_into(file, line) <br /> logger.insert "#{line} into #{file}" <br /> unless options[:pretend] || file_contains?(file, line) <br /> gsub_file file, /^(class|module) .+$/ do |match| <br /> "#{match}\n #{line}" <br /> end <br /> end <br /> end <br />end <br /><br />#/clearance/templates/migrations/create_users.rb <br />class ClearanceCreateUsers < ActiveRecord::Migration <br /> def self.up <br /> create_table(:users) do |t| <br /> t.string :email <br /> t.string :encrypted_password, :limit => 128 <br /> t.string :salt, :limit => 128 <br /> t.string :confirmation_token, :limit => 128 <br /> t.string :remember_token, :limit => 128 <br /> t.boolean :email_confirmed, :default => false, :null => false <br /> t.timestamps <br /> end <br /> <br /> add_index :users, [:id, :confirmation_token] <br /> add_index :users, :email <br /> add_index :users, :remember_token <br /> end <br /> <br /> def self.down <br /> drop_table :users <br /> end <br />end <br /> <br /> <br />#------------------------------------- <br />#/clearance/templates/migrations/update_users.rb <br />class ClearanceUpdateUsers < ActiveRecord::Migration <br /> def self.up <br /><% <br /> # ActiveRecord::Base.connection.columns(:users).collect { |each| each.name } = User.columns.map { |each| each.name } <br /> existing_columns = ActiveRecord::Base.connection.columns(:users).collect { |each| each.name } <br /> columns = [ <br /> [:email, 't.string :email'], <br /> [:encrypted_password, 't.string :encrypted_password, :limit => 128'], <br /> [:salt, 't.string :salt, :limit => 128'], <br /> [:confirmation_token, 't.string :confirmation_token, :limit => 128'], <br /> [:remember_token, 't.string :remember_token, :limit => 128'], <br /> [:email_confirmed, 't.boolean :email_confirmed, :default => false, :null => false'] <br /> ].delete_if {|c| existing_columns.include?(c.first.to_s)} <br />-%> <br /> change_table(:users) do |t| <br /><% columns.each do |c| -%> <br /> <%= c.last %> <br /><% end -%> <br /> end <br /> <br /><% <br /> #連有哪些index 也可以看 <br /> existing_indexes = ActiveRecord::Base.connection.indexes(:users) <br /> index_names = existing_indexes.collect { |each| each.name } <br /> new_indexes = [ <br /> [:index_users_on_id_and_confirmation_token, 'add_index :users, [:id, :confirmation_token]'], <br /> [:index_users_on_email, 'add_index :users, :email'], <br /> [:index_users_on_remember_token, 'add_index :users, :remember_token'] <br /> ].delete_if { |each| index_names.include?(each.first.to_s) } <br />-%> <br /><% new_indexes.each do |each| -%> <br /> <%= each.last %> <br /><% end -%> <br /> end <br /> <br /> def self.down <br /> change_table(:users) do |t| <br /><% unless columns.empty? -%> <br /> t.remove <%= columns.collect { |each| ":#{each.first}" }.join(',') %> <br /><% end -%> <br /> end <br /> end <br />end <br />

JavaScript 中的 document.createDocumentFragment

JavaScript 中的 document.createDocumentFragment
<br />var fragment = document.createDocumentFragment();<br />for (var i in some_array) {<br /> var node = document.createElement('option');<br /> node.innerHTML = '....';<br /> fragment.appendChild(node);<br />}<br />targetNode.appendChild(fragment);<br />
在這段程式碼中，使用了 document.createDocumentFragment() 這個函式產生一個 document fragment，你可以把它想作是一個處理 DOM element 的 buffer，把欲生成的 DOM element 先加入到這個 fragment 中，最後再一次加到頁面的 DOM 結構中，這樣的作法比起在迴圈中一直 appendChild 來得快上許多，當然更重要的是，問題也被解決了 :)

ruby binary code

有時候想要return 一些binary code 東西要怎樣帶勒
<br />#注意外面要雙引號喔<br />return :text => "aaaa\r\nbbbb"<br />#或<br />return :text => "aaaa\x0a\x0dbbbb"<br />

console tips

Hirb - Irb On The Good Stuff
可以看到sql 結果的
<br /> gem install cldwalker-hirb —source http://gems.github.com<br /> # Load hirb and enable view framework<br /> irb>> require 'hirb'<br /> => true<br /> irb>> Hirb::View.enable<br /> => nil<br />

可以看到sql 指令的
<br /># ~/.irbrc file <br />script_console_running = ENV.include?('RAILS_ENV') && IRB.conf[:LOAD_MODULES] && IRB.conf[:LOAD_MODULES].include?('console_with_helpers')<br />rails_running = ENV.include?('RAILS_ENV') && !(IRB.conf[:LOAD_MODULES] && IRB.conf[:LOAD_MODULES].include?('console_with_helpers'))<br />irb_standalone_running = !script_console_running && !rails_running<br /><br />if script_console_running<br /> require 'logger'<br /> Object.const_set(:RAILS_DEFAULT_LOGGER, Logger.new(STDOUT))<br />end<br />

has_many , time now, assocation

Do you know when your code runs?
有時候你時候你會發現你在你下的conditions 有關於時間的, 跑起來有點怪怪的

在development 沒問題, 在production 卻不正常

仔細看會發現時間統統都是static 的了, 因為production 並不會每次都去reload class
<br />class Person < ActiveRecord::Base<br /> has_many :posts<br /> has_many :recent_posts, :class_name => 'Post', :conditions => ["created_at > ?", 1.week.ago]<br /> validates_inclusion_of :birth_date, :in => (20.years.ago..13.years.ago), <br /> :message => "You must be a teenager to signup", :on => :create<br />end<br /><br />class Post < ActiveRecord::Base<br /> named_scope :recent, :conditions => ["created_at > ?", 1.week.ago]<br />end<br />
這時候只要換個寫法<br />#make one with no arguments, just to ensure that the time condition is evaluated whenever the scope is accessed. <br />class Post<br /> named_scope :recent, lambda { {:conditions => 1.week.ago}}<br />end<br /><br />#Active Record will perform that interpolation again at the point where sql is generated<br />class Person < ActiveRecord::Base<br /> has_many :recent_posts, :class_name => 'Post', <br /> :conditions => "created_at > #{1.week.ago.to_s(:db)}"<br />end<br /><br />#Validations can't play any of the clever little games that the other 2 examples can. You'll just have to something like<br />class Person < ActiveRecord::Base<br /> validate_on_create :is_a_teenager<br /><br /> def is_a_teenager<br /> unless birth_date < 13.years.ago && birth_date > 20.years.ago<br /> ...<br /> end<br /> end<br />end<br />

跨browser 播音樂

http://www.htmlcodetutorial.com/embeddedobjects/_EMBED.html
<br /><[embed src="symphony.mid" autostart="false" width="0" height="0" id="music"]><br /><br />var music = $("#music")[0];<br />music.Stop();<br /><br />music.Play();<br />

Facebook app memo

Facebook development: choosing FBML or iframe as your application type
http://apps.new.facebook.com/facebooker_tutorial/

1. Set up New application
http://www.facebook.com/developers/

2. remember your api key and serect key

3. Canvas/畫布 setting

---

api key, serect key

they let our application verify that requests are coming from Facebook.

---

Facebook sends us the ID of the current user and their whole list of friends on
every request. That makes our life quite a bit easier. It also can cause
some security problems.

---

All requests come from Facebook. To make sure this is the case, we can
verify the signature that is sent by Facebook on every request. A digital
signature is a way to use cryptography to verify that something actually
came from the person who it appears to be from.4 Facebook sends a
number of parameters that start with fb_sig. All these parameters are
used in the signature validation.

When Facebook sends our applications a request, it builds a string
that includes all the fb_sig parameters in alphabetical order. It then
adds our secret key to the end of that string and calculates the MD5 sum.

When Facebooker receives a request, it goes through the
same steps to recalculate the signature. If the value that Facebooker
calculates matches the one in our request, it proves that the request
came from somebody who knows our secret key.

---

Rails included a feature to stop cross-site forgery
attacks. Unfortunately, this feature doesn’t play well with Facebook.
We’ll need to disable it by editing environment.rb and setting allow_forgery_
protection to false,

---

---

---

---