You should already have installed Ruby on Rails for Project #2. If not, follow the installation instructions now. Once Rails is installed, create a Rails application for this project by invoking the following command:
rails project3
This will create a directory project3 that contains a
skeleton for the project. Your solutions for all of the problems
below should be implemented in this project.
Create a model, view, and controller in the project3
application, which together will display the names of all states
containing a given substring. Your code must implement the URL
/state/filter, which accepts a query value named
substring. The URL should produce a
Web page that lists in alphabetical order all states whose names
contain the given substring
(ignoring differences in case). For example, the Web page for
/state/filter?substring=al should list the states
Alaska, Alabama, and California. The page should also display the
substring that was used to filter the states. If there are no
matching states then the Web page should display a message indicating
that fact (rather than just showing nothing).
First, create a model that will manage the data. The model should be
implemented as a class named
State with a single class method State.filter
(a class method is one that can be invoked without an instance of the
class, like a static method in Java). State.filter should
take a single string argument and return an array containing the names
of all states whose names include the argument as a substring (ignoring
differences in case). To save typing you can download
states.rb,
which contains Ruby code to create an array containing the names
of all of the states. You can copy this code into your application.
Once you have defined the model you can then create the controller and view. Follow the Rails conventions for file and method naming and for where to put various functionality.
Use the Rails layout mechanism to create a default layout for the
state controller; if you implement this correctly
(i.e. in the file project3/app/views/layouts/application.html.erb),
the layout will be used automatically for the /state/filter
URL. The layout should handle everything except the contents of the
<body> element, so you can now remove the
boilerplate from your solution to Problem 1.
Modify the layout you just created so that it displays a personalized
header at the top of the page (the layout will now include some HTML
inside the <body> element). Use your imagination
and creativity to
create a header that is "uniquely you". This can include images,
graphics, whatever you like. Be creative! From now on, use this
layout for all of your Rails projects in the class. Each individual
page should be able to specify its own title, which gets used by the
default layout.
Define a new controller and view that implement the URL
/tabs/show2.
This URL must display a page containing
two sets of tabs separated by a half-inch or so of white space.
The first set must be exactly the same as your
solution to Problem 2 in Project 1. The second set must have the
same general appearance but must display different labels (which
you can choose). You must use a partial template named tabs
to generate the tabs; your view should invoke it twice. The partial
template takes two parameters. The first is an array of hashes,
one for each tab; each hash has a :label element containing
the text to display in the tab, and a :url element containing
the URL to visit when that tab is clicked. The second parameter for the
partial template is a string containing the label of the selected
tab; the partial template uses it to identify the selected tab and
display it differently.
cd to the directory
containing the application and invoke the following command:
ruby script/server
Use the standard class submission mechanism
to submit the entire application (everything in the project3
directory). Note: all of your generated HTML must validate as
proper XHTML (you do not need to validate your CSS for this project).