Choosing between an FBML or IFrame Application(1)

Choosing between an FBML or IFrame Application


Traditional IFrame Canvas Page


FBML Canvas Page



XFBML as part of Facebook Connect as a way to quickly get social content onto any Web page, and since IFrames are just Web pages, XFBML can speed those up as well.

Before XFBML, IFrame applications always had to make API calls to render social content like user names and profile pictures, and those API calls required another round trip communication between your server and Facebook before sending back content to the user's browser

with XFBML, you can embed various FBML tags like fb:name and fb:profile-pic directly into the HTML that your application sends to the user's browser. Then you simply include some Facebook-specific JavaScript, and that code gets executed and scans the DOM for those tags. The JavaScript then determines all the data needed to render that content and batches it up into one API call from the user's browser to Facebook

The rest of the page that isn't social content can render to the user before the API call completes. And in XFBML, we cache data on the browser so that in many cases, it isn't even necessary to make any API call to Facebook at all.

IFrame Canvas Page Using XFBML - First Page Load by a User


IFrame Canvas Page Using XFBML - Subsequent Page Loads by a User

找該加index 的地方

rails_indexes

<br />script/plugin install git://github.com/eladmeidar/rails_indexes.git<br /><br />#用association 來找 缺少的 index<br />rake db:show_me_a_migration<br /><br />#用 AR::Base#find calls (including: find, find_by, find_all_by, find_by_x_and_y, find_all_by_x_and_y): 來找缺少的index<br />rake db:show_me_ar_find_indexes<br />

check index exist

add_index 之前檢查一下
<br />class AddMissingIndexes < ActiveRecord::Migration<br /> def self.up<br /> check_add_index :groups, :id<br /> check_add_index :about_states, :confirm_email_code<br /> check_add_index :messages, :id<br /> end<br /><br /> def self.down<br /> check_remove_index :groups, :id<br /> check_remove_index :about_states, :confirm_email_code<br /> check_remove_index :messages, :id<br /> end<br /><br /> def self.check_add_index(table, column)<br /> add_index table, column unless check_index_exist(table, column)<br /> end<br /><br /> def self.check_remove_index(table, column)<br /> remove_index table, column if check_index_exist(table, column)<br /> end<br /><br /> # indexes 可以找出talbe 的 indexes<br /> # index_name 可以產生該生成的 index name<br /> def self.check_index_exist(table, columns)<br /> ActiveRecord::Base.connection.indexes(table).map(&:name).include?(ActiveRecord::Base.connection.index_name(table, columns))<br /> end<br /><br />end<br />

mustache 把view logic 的部份再拆出來

就是要讓view 更乾淨把logic 的部份再拆出來
mustache

Ruby on Rails Code Quality Checklist

Ruby on Rails Code Quality Checklist

1. Each controller action only calls one model method other than an initial find or new.
(Make custom .new or .update methods in the model with all necessary). ...
就是盡量把邏輯擺到model 裡, 唯一的例外就是在決定要render view or redirect的時候


2. Only one or two instance variables are shared between each controller and view. ...
保持一兩個instance variable 在controller 和 view 就好
這樣可以讓所有相關連的只有在需要的時候在被call 到, 而且還可以做instance-variable cache in one place
例如不要在controller 裡用到 @post and @related_posts 兩個instance variable, 而是create a method 給 @post, 這樣你就可以在 view 裡面直接用 @post.related_posts


3. All model and variable names are both immediately obvious (to a new developer) and as short as possible without using abbreviations. ...
取個好名字


4. All custom "finds" accessed from more than one place in the code use named_scope instead of a custom method. ...
有關find 什麼東西的, 都用named_scope 來做


5. A .find or .find_by_ is never called in a view or view helper. ...
別直接在view , find or find_by anything, 至少用一下namde_scope or custom methods to do that


6. There is zero custom code that duplicates functionality of a built-in function in rails. ...
7. Code has been aggressively DRYed during development. ...
8. All functionality used in two or more models has been turned into a library/module. ...
9. All logic duplicated between two or more apps has been turned into a gemified plugin. ...

10. STI is not used anywhere ...
別用STI, 用module 來代替, 如果你用STI 你會需要至少bind 兩個model, 這樣你很難回頭
data migration 你會死
但是polymorphic association 是鼓勵的


11. Every design choice should yield the most simplistic design possible for the need of users at the current time.
No guesses for future functionality were designed into the application. ...
對於現在的情況做最簡單的設計, 不要猜測未來的情況, 你可能會猜錯


12. Close to full test coverage exists at the highest level of the application: on and between controller actions. Coverage is highest for code used by the most number of end users. ...

先從user 最常用的開始測起
13. All tests pass before code is merged into a shared repository. ...

merge 前要測過
14. Every fixed defect on a deployed product has tests added to prevent regression. ...
替解掉的defeat 加上測試

15. Every plugin installed has been code reviewed. ...
檢查一下你的plugin code

Install any HTML theme/template into your Rails app

Install any HTML theme/template into your Rails app
install_theme
open source web design

幫你用來快速套template 的
<br /># lowerright:text 的部份就是指定content的部份<br /># partial 就是指定哪邊會變partial, 最基本的就是menu<br /># 指定path 有不同的指定方式XPath or CSS path 都可以<br /># install_theme . path/to/theme/folder ".lowerright:text" --partial "menu:.nav:text"<br /><br /><br />$ gem install install_theme<br />$ rails my_app<br />$ cd my_app<br />$ install_theme . path/to/theme/folder ".lowerright:text" --partial "menu://div[@class='nav']/text()"<br /> create app/app/helpers/template_helper.rb<br /> create app/controllers/original_template_controller.rb<br /> create app/helpers/template_helper.rb<br /> create app/views/layouts/_menu.html.erb<br /> create app/views/layouts/application.html.erb<br /> create app/views/original_template/index.html.erb<br /> create public/images/footer.png<br /> ...<br /> create public/stylesheets/style.css<br /><br />Your theme has been installed into your app.<br />
<br />#可以用這樣來做menu 的選擇<br /><br />module TemplateHelper<br /> def render_or_default(partial, default = partial)<br /> render :partial => partial<br /> rescue ActionView::MissingTemplate<br /> begin<br /> render :partial => "layouts/#{default}"<br /> rescue ActionView::MissingTemplate<br /> nil<br /> end<br /> end<br />end<br />

[Scale] Scale Frontend 應該注意的五件事

[Scale] Scale Frontend 應該注意的五件事
Rails in the Wild: 5 Client-Side Performance Observations

1. It’s easy to forget to compress your JavaScript and CSS

要記得 :cache => true
要記得壓 js 和 css

2. Watch out for slow third party services

都是慢在第三方
google ads, analytics 也會托慢, 請用 postload_google_ads


3. Using multiple image hosts doesn’t always mean higher performance

拆那麼多台未必會比較快

4. S3 is NOT a Webserver!

S3 是 storage ，不是 web server。所以不要一股腦的把東西往上丟，要注意有沒有敏感資訊，而且 s3p 是沒有幫忙做 gzip 的。

5. Most performance variability is NOT attributable to page factors

速度慢通常是慢在後端..