Contents 

Ruby on Rails:
Table of Contents
Preface
Zero to Sixty: Introducing Rails
1.1. Rails Strengths
1.2. Putting Rails into Action
1.3. Organization
1.4. The Web Server
1.5. Creating a Controller
1.6. Building a View
1.7. Tying the Controller to the View
1.8. Under the Hood
1.9. What's Next?
Active Record Basics
2.1. Active Record Basics
2.2. Introducing Photo Share
2.3. Schema Migrations
2.4. Basic Active Record Classes
2.5. Attributes
2.6. Complex Classes
2.7. Behavior
2.8. Moving Forward
Active Record Relationships
3.1. belongs_to
3.2. has_many
3.3. has_one
3.4. What You Haven't Seen
3.5. Looking Ahead
Scaffolding
4.1. Using the Scaffold Method
4.2. Replacing Scaffolding
4.3. Generating Scaffolding Code
4.4. Moving Forward
Extending Views
5.1. The Big Picture
5.2. Seeing Real Photos
5.3. View Templates
5.4. Setting the Default Root
5.5. Stylesheets
5.6. Hierarchical Categories
5.7. Styling the Slideshows
Ajax
6.1. How Rails Implements Ajax
6.2. Playing a Slideshow
6.3. Using Drag-and-Drop to Reorder Slides
6.4. Drag and Drop Everything (Almost Everything)
6.5. Filtering by Category
Testing
7.1. Background
7.2. Ruby's Test::Unit
7.3. Testing in Rails
7.4. Wrapping Up
Installing Rails
1.1. Windows
2.1. OS X
3.1. Linux
Quick Reference
5.1. General
5.2. Testing
5.3. RJS (Ruby JavaScript)
5.4. Active Record
5.5. Controllers
5.6. Views
5.7. Ajax
5.8. Configuring Your Application
About the Authors
Colophon
Index
A
B
C
D
E
F
G
H
I
J
L
M
N
O
P
R
S
T
U
V
W
X
Y
Z

Ruby on Rails manual

Prev Page Next Page
Previous Page
Next Page

2.2. Introducing Photo Share

For the remainder of this site, we'll be working on a single application called Photo Share, a database-backed web application that allows users to share photos among acquaintances. We'll start with these simple requirements, called user stories:

  • Let a user view a set of photos on the Web so others can see them.

  • Organize photos in categories.

  • Organize and view slideshows from available photos.

2.2.1. Defining the Model

Rails is a database-centric development environment, so your development will usually begin with the model. You need to determine the types of objects your application will need. A good starting point is to underline the important nouns in a list of user stories. We've used italic to signify important nouns, so we'll have Active Record classes for photos, categories, and slideshows. We'll also need slides, to keep track of the position of each photo in a slideshow.

There are several important relationships:

  • A category has many photos, and a photo can have one or more categories.

  • A category can have other categories.

  • A slideshow has many slides.

  • A slide has one photo.

A simple diagram like the one in Figure 2-1 helps to show the entities and relationships in your model. Index cards work well. For many-to-one relationships, we'll use an arrow to mean belongs to, so the arrow will point from the one to the many. Two-sided arrows are many-to-many, and a line without arrows means one-to-one. We'll represent a tree with an arrow that points back to the originating class. We'll use Active Record to define each of these entities and manage each relationship. Now, let's code them in Active Record.

Figure 2-1. Photos are placed into nested categories and listed in slideshows

2.2.2. Configuring Active Record

As always, we start with a Rails project. First, create a Rails project called photos:

rails photos
cd photos

You've now got a Rails project called photos with three environments: development, test, and production. Rails uses separate databases for each environment (see the sidebar " "rubyrails-chp-2-sect-3.html#rubyrails-chp-2-sidebar-1">Three Databases"). To create a database, make sure the MySQL database is started and also start the mysql command prompt:

mysql -u <username> -p <password>

Now create a database called photos_development:

> mysql
...

mysql> create database photos_development;
Query OK, 1 row affected (0.05 sec)

Configure your database. This chapter uses a development database, so you need to edit database.yml to look like this:

development:
  adapter: mysql
  database: photos_development
  username: <your userid>
  password: <your password>
  host: localhost


Previous Page
Next Page