In previous articles we had discussed and introduced the principles behind the model-view-controller architectural pattern, and saw how each of the components is implemented within the Rails framework. Now lets use those knowledge on Rails’s code generation techniques to create components.

generate can be called from the command line and takes several parameters. The first parameter is the type of component that’s to be generated. You can probably guess which value I’m going to suggest you use for this parameter. We’re creating a model, so the parameter to pass is simply model. Let’s take a look at what happens when we pass that to the script: (more…)

MVC is a pattern for the architecture of a software application. It separates an application into the following three components:
? models, for handling data and business logic
? controllers, for handling the user interface and application logic
? views, for handling graphical user interface objects and presentation logic.
(more…)

Following last article discussing about development, test, and production, lets have a look at database architecture affecting by those three environment in Ruby.

(more…)

Rails encourages the use of a different environment for each of the stages in an application’s life cycle development, testing, and production. If you’ve been developing Web applications for a while, this is probably how you operate anyway;
Rails just formalizes these environments.

Development
In the development environment, changes to an application’s source code are immediately visible; all we need to do is reload the corresponding page in a web browser. Speed is not a critical factor in this environment; instead, the focus is on providing the developer with as much insight as possible into the components involved in displaying each page. When an error occurs in the development environment, the developer is able to tell at a glance which line of code is responsible for the error, and how that particular line was invoked. This capability is provided by the stack trace (a comprehensive list of all the method calls leading up to the error), which is displayed when an unexpected error occurs.
(more…)

Ruby on Rails was first released long time ago, but like it or not its existing has become a household name or we could say a legend. Within that time, hundreds of thousands of developers the world over have adopted and adored this new framework, and actually until there are some developers keep doing it. Before we go deep in ruby, let’s take first introduction as we meet Ruby on Rails and explore its history.

You might wonder (especially for you who never heard it before), what exactly is Ruby on Rails? Ruby on Rails often describe as a full-stack web application framework, written in Ruby. However, depending on your previous programming experience, that answer might not make a whole lot of sense to you. Besides, the Ruby on Rails movement really needs to be viewed in the context of web development in general if it is to be fully appreciated.
(more…)