Introduction to RoR

1. Ruby On Rails
Building Web Applications Is Fun!

2. What is Ruby on Rails?
Rails is a full-stack framework for developing
database-backed web applications according
to the Model-View-Control pattern.
– www.rubyonrails.org - Ruby on Rails official site

3. RoR Trivia
• Written in Ruby
• Creator of Ruby on Rails
– David Heinemeier Hansson
• Birth: July 2004
• Latest: 2.1.1: 4 September 2008
• Based on SmallTalk, Perl, Lisp
• Not strongly typed

4. What is Ruby?
Dynamic, high level, interpreted, pure object-
orientated language.
“Ruby is designed to make programmers happy”
Yukihiro Matsumoto aka Matz

5. Ruby Trivia
• Creator of Ruby
– Yukihiro Matsumoto aka Matz
• Birthday: 24 February 1993
• Originated in Japan and Rapidly
Gaining Mindshare in US and Europe.

7. Design Principles

8. Design Principles
Model - View - Controller
• Separate data (model) from user interface (view)
• Model
– data access and business logic
– independent of the view and controller
• View
– data presentation and user interaction
– read-only access to the model
• Controller
– handling events
– operating on model and view

9. Design Principles
Database Persistence
• OR mapping
– Active Record design pattern
• migrations
– incremental schema management
• multiple db adapters
– MySQL, PostgreSQL, SQLite, SQL Server, IBM DB2,
Informix, Oracle

10. Design Principles
Full Stack Framework
• MVC suite
• built-in webserver
• default db adapter
• AJAX, web services, email
• test framework
• plugins

11. Design Principles
Convention over Configuration
• fixed directory structure
– everything has its place – source files, libs, plugins,
database files, documentation etc
• file naming conventions
– e.g. camel case class name, underscore file name
• database naming conventions
– table names, primary and foreign keys
• standard configuration files
– e.g. database connections, environment setting definitions
(development, production, test)

12. Design Principles
DRY - Don’t Repeat Yourself
• reusing code
– e.g. view elements
• reusing data
– e.g. no need to declare table field names – can be read
from the database
• making each line of code work harder
– e.g. mini languages for specific domains
• object-relational mapping
• metaprogramming
– dynamically created methods

13. MVC Architecture

14. MVC Architecture
MVC Architecture

15. MVC Architecture
Model - ActiveRecord
• Object Relational Mapping
– “ActiveRecord”
• Less Database “glue” Code
• Logging for Performance Checking

16. MVC Architecture
Model : Rules
• Table Names
– Plurals
• Attribute Names
– id for primary key in table
– table_id for foreign key in other table

17. MVC Architecture
View - ActionView
• multiple template types
– oldest and basic: erb (embedded ruby), similar to e.g. jsp
– remote javascript templates
– xml templates
• easy reuse of view elements
– file inclusion – layouts, templates, partials
– multiple standard "helpers" – common html element
generators (e.g. form elements, paginators)
• easy AJAX integration

18. MVC Architecture
Controller : ActionController
• Method name matches view folder
– users_controller.rb works for
/views/users/***.rhtml
– called “actions”
– all view’s methods will sit there
• Ability to
– CRUD
– Flash
– Redirect

19. Some Comparisons

20. RoR vs. Java
Comparison of Rails and J2EE stacks

21. Usage & Support

22. Usage & Support
Web Servers
• Lighttpd
• Mongrel
• WEBrick
• Apache

23. Usage & Support
RoR Databases
• Mysql
• Oracle
• Postgre Sql
• SqlLite

24. Usage & Support
Websites on Rails

25. Usage & Support
Companies Using Rails

26. References
• www.slideshare.net
• www.youtube.com
• www.google.com
• http://www.netbeans.org/kb/docs/ruby/rapid-rub
• http://guides.rails.info/getting_started.html
• www.rubyonrails.org
• http://www.tutorialspoint.com/ruby-on-rails-2.1

27. Thank You.!!