CSC/ECE 517 Fall 2007/wiki2 1 rl: Difference between revisions
| Line 15: | Line 15: | ||
<li>'''MVC Architecture:''' All Rails applications use the MVC architecture. Rails projects are created with a placeholder for each concern, and these concerns always interact in the same standard way.</li> | <li>'''MVC Architecture:''' All Rails applications use the MVC architecture. Rails projects are created with a placeholder for each concern, and these concerns always interact in the same standard way.</li> | ||
<li>'''Scaffolds:''' Rails applications can take advantage of scaffolds out of the box. Essentially, Rails will generate all of the code necessary to do basic database interactions, such as create, read, update, and delete entries. This allows developers to quickly and easily begin working with their data model, and replace the generated code with customized versions piece by piece.</li> | <li>'''Scaffolds:''' Rails applications can take advantage of scaffolds out of the box. Essentially, Rails will generate all of the code necessary to do basic database interactions, such as create, read, update, and delete entries. This allows developers to quickly and easily begin working with their data model, and replace the generated code with customized versions piece by piece.</li> | ||
<li>'''Convention over Configuration:''' Rails uses sensible defaults, so as long as you follow convention, your application can be written with significantly less code and without the great number of configuration files seen in other web applications today. For example, if you create a model class called ''Product'', Rails will also generate for you a controller class named ProductsController, and will assume that your model is using a database table called ''products''. You only need to configure the table name if you are using a different value.</li> | <li>'''Convention over Configuration:''' Rails uses sensible defaults, so as long as you follow convention, your application can be written with significantly less code and without the great number of configuration files seen in other web applications today. For example, if you create a model class called ''Product'', Rails will also generate for you a controller class named ''ProductsController'', and will assume that your model is using a database table called ''products''. You only need to configure the table name if you are using a different value.</li> | ||
</ul> | </ul> | ||
Revision as of 23:18, 22 October 2007
Assignment
Compare Ruby on Rails with Apache Struts. The Apache Struts framework in the Java world occupies a position similar to Ruby on Rails, except that it is not as universally used. Compare the two. Which are the advantages of each for the developer? For the finished application?
Introduction
Ruby on Rails and Apache Struts are both web application frameworks based on the Model-View-Controller (MVC) architecture.
MVC Architecture
MVC separates an application into three components: the model, the view, and the controller. The model maintains the application state; it consists of both the data used by the application as well as the rules surrounding the use of that data. The view generates the user interface, which allows the user to view and interact with the data in the model. The controller takes input from the outside world, interprets the input, and manipulates the model accordingly. Separating these three concerns makes the application code easier to understand, reuse, and maintain.
Ruby on Rails
Ruby on Rails, also known as "Rails" or "RoR", is the standard Web application framework for the Ruby programming language. It is an open source project that was released in 2004, and was created to make web application development quick and easy. Rails attempts to achieve this through several means:
- MVC Architecture: All Rails applications use the MVC architecture. Rails projects are created with a placeholder for each concern, and these concerns always interact in the same standard way.
- Scaffolds: Rails applications can take advantage of scaffolds out of the box. Essentially, Rails will generate all of the code necessary to do basic database interactions, such as create, read, update, and delete entries. This allows developers to quickly and easily begin working with their data model, and replace the generated code with customized versions piece by piece.
- Convention over Configuration: Rails uses sensible defaults, so as long as you follow convention, your application can be written with significantly less code and without the great number of configuration files seen in other web applications today. For example, if you create a model class called Product, Rails will also generate for you a controller class named ProductsController, and will assume that your model is using a database table called products. You only need to configure the table name if you are using a different value.
Example? advantage: the short and clear URLs, new so not playing catchup on standards (page 2 of book), http://en.wikipedia.org/wiki/Convention_over_Configuration (hibernate) http://www.javalobby.org/java/forums/t65305.html
Apache Struts
What is Struts? Example?
A Comparison
page 1 of text
Advantages
Advantages for the Developer
Advantages for the Application
References
- Ruby on Rails and J2EE: Is there room for both?
- Rolling with Ruby on Rails Revisited
- Ruby on Rails
- Model-view-controller
- CSC517 Lecture 12: Ruby on Rails
- Agile Web Development with Rails