Five Minutes Introduction For Rails

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    1 Group

    Five Minutes Introduction For Rails - Presentation Transcript

    1. Presents
    2. JIN SHINTARO NISHIKAWA KAKUTANI Special Thanks
    3. AND ESM EIJI LLWG IENAGA Special Thanks
    4. 人はあらゆるプロセスよりも重要である。 優れた人々に優れたプロセスを与えれ ば、プロセスを持たない優れた人々より も常に効率が上がる。 ー Grady Booch
    5. On December 13, 2005 the David Heinemeier Hanson major released on excellent framework for the all of its programmers. Its purpose was to get back the lost Quality of Engineering Life and to insure that the all of men who comprehensive were the nice programmers in the world. They succeeded. Today, the Programmer calls it Web Application Framework. The programmers call it: 2005年12月13日
    6. On December 13, 2005 the David Heinemeier Hanson major released on excellent framework for the all of its programmers. Its purpose was to get back the lost Quality of Engineering Life and to insure that the all of men who comprehensive were the nice programmers in the world. They succeeded. Today, the Programmer calls it Web Application Framework. The programmers call it: DHHはすべての プログラマーのために
    7. On December 13, 2005 the David Heinemeier Hanson major released on excellent framework for the all of its programmers. Its purpose was to get back the lost Quality of Engineering Life and to insure that the all of men who comprehensive were the nice programmers in the world. They succeeded. Today, the Programmer calls it Web Application Framework. The programmers call it: WebアプリケーションF/Wを メジャーリリースした
    8. On December 13, 2005 the David Heinemeier Hanson major released on excellent framework for the all of its programmers. Its purpose was to get back the lost Quality of Engineering Life and to insure that the all of men who comprehensive were the nice programmers in the world. They succeeded. Today, the Programmer calls it Web Application Framework. The programmers call it: 目的は失われつつある エンジニア人生の質
    9. On December 13, 2005 the David Heinemeier Hanson major released on excellent framework for the all of its programmers. Its purpose was to get back the lost Quality of Engineering Life and to insure that the all of men who comprehensive were the nice programmers in the world. They succeeded. Today, the Programmer calls it Web Application Framework. The programmers call it: 世界最高の WebアプリケーションF/Wの 呼び名は
    10. Get back the lost Quality of Engineering Life with 分間の 入門
    11. Part1: Rails の思想 Part2: Rails の構成 Part3: Rails とRuby
    12. の思想 1.DRY 2.CoC
    13. Don ’ t Repeat Yourself 繰り返しを避けること
    14. Convention over Configuration 設定よりも規約
    15. まとめ あ あとで書く と で あとで書く
    16. の構成 1.AR 2.AP 3.Rails
    17. ORMのパッケージ
    18. より データベースのテーブル やビューの列をラップし、 データベースアクセスをカ プセル化し、ドメインロジッ クを追加するオブジェクト http://capsctrl.que.jp/kdmsnr/wiki/PofEAA/?ActiveRecord PoEAAで紹介されている ORMパターンのひとつ
    19. app/models/person.rb class Person < ActiveRecord::Base end ActiveRecord::Baseを継承
    20. データベース管理 db/migrate/001_create_people.rb class CreatePeople < ActiveRecord::Migration def self.up create_table :people do |table| table.column :first_name, :string, :limit => 32 table.column :last_name, :string, :limit => 32 table.column :number_of_dependents, :integer end end def self.down drop_table :people end end MigrationによるDB管理が可能
    21. の威力 Ruby だけ知っていれば よいか? ドメイン特化言語としてのRuby
    22. SQLの知識は重要、超重要
    23. ActionControllerと ActionViewを含むパッケージ
    24. app/controllers/people_controller.rb class PeopleController < ActionController::Base def show @person = Person.find(params[:id]) end end ActionController::Baseを継承
    25. app/views/people/show.rhtml <% for column in Person.content_columns %> <p> <b><%= column.human_name %>:</b> <%=h @person.send(column.name) %> </p> <% end %> コントローラと インスタンス変数を共有する
    26. app/views/layouts/people.rhtml <html> <head> <title><%= controller.action_name %></title> </head> <body> <%= @content_for_layout %> </body> </html> レイアウトを使って共通する ビューをまとめる
    27. レイヤーをつなげる線路
    28. まとめ 道 Tool 具 重 Matters 要 職人は道具を選ぶ
    29. と 1.DSL 2.Agile 3.Fun
    30. なぜDSL が大事か?
    31. の効用 Human Readable コードは人間にとって 読み易くあるべき
    32. RubyがDSLに向く3つの理由 1.括弧を省略できる 2.シンボルがオブジェクト 3.ブロックがある (名前空間の重複を防げる) http://blog.nikkeibp.co.jp/itpro/java/archives/2006/02/rubydsl.html 宣言的な記述が可能
    33. Is Ruby Agile? http://www.objectclub.jp/event/2005christmas/schedule#2-2 オブジェクト倶楽部 2005年クリスマスイベントにて
    34. まつもとさんの答え http://www.rubyist.net/~matz/slides/oc2005/mgp00005.html Rubyはアジャイルである
    35. あとで書く あとで書く
    36. まとめ 誇りと希望を持った仕事が QoELにつながる
    37. 結論 コンパイル / ビルドの 終わりを 待っているほど 人生は長くはない アジャイルな人の道具には Rubyが馴染むと思うのです
    38. Enjoy Engineering Life

    + Koichi ITOKoichi ITO, 3 years ago

    custom

    1165 views, 0 favs, 0 embeds more stats

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 1165
      • 1165 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 18
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories

    Groups / Events