Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2014/oss M1453 sst

2014-10-27T05:52:43Z

Spuri3:

Expand the coverage of the developer tools for inspecting web content in Servo remotely from a Firefox browser - requires the ability to read JavaScript code in Firefox

==Background Information==
Firefox supports remote debugging - i.e. communicating with an arbitrary server that implements a protocol for exposing information about web content. Servo implements a very basic developer tools server that currently supports executing JS remotely and investigating the DOM tree in the document inspector. We want to expand these capabilities by allowing remote modification of the DOM tree, better JS console integration (exposing historical and real-time exceptions), and enabling server->client messages that are not responses to client->server messages.

===Developer tools===
The Mozilla debugging protocol allows a debugger to connect to a browser, discover what sorts of things are present to debug or inspect, select [http://en.wikipedia.org/wiki/JavaScript JavaScript] threads to watch, and observe and modify their execution. The protocol provides a unified view of JavaScript, [http://en.wikipedia.org/wiki/Document_Object_Model DOM] nodes, [http://en.wikipedia.org/wiki/Cascading_Style_Sheets CSS] rules, and the other technologies used in client-side web applications. The protocol ought to be sufficiently general to be extended for use with other sorts of clients (profilers, say) and servers (mail readers; random XULrunner applications).

All communication between debugger (client) and browser (server) is in the form of [http://en.wikipedia.org/wiki/JSON JSON] objects. This makes the protocol directly readable by humans, capable of graceful evolution, and easy to implement using stock libraries. In particular, it should be easy to create mock implementations for testing and experimentation.

The protocol operates at the JavaScript level, not at the [http://en.wikipedia.org/wiki/C%2B%2B C++] or machine level, and assumes that the JavaScript implementation itself is healthy and responsive. The JavaScript program being executed may well have gone wrong, but the JavaScript implementation's internal state must not be corrupt. Bugs in the implementation may cause the debugger to fail; bugs in the interpreted program must not.

Reference: https://wiki.mozilla.org/Remote_Debugging_Protocol

'''Setting up remote debugging'''

Firefox acts as the client and provides the user interface to control the developer tools. The guide to explain how to use remote debugging to inspect or debug code running in Firefox is [https://developer.mozilla.org/en-US/docs/Tools/Remote_Debugging/Thunderbird here]

===Servo===
Servo is an experimental web browser engine under development by [https://www.mozilla.org/en-US/research/ Mozilla Research]. It is an ambitious project aimed at rebuilding the browser on modern parallel hardware. Servo aims at addressing the causes of security vulnerabilities while designing a platform that can fully utilize the performance of tomorrow’s massively parallel hardware to enable new and richer experiences on the Web. Servo is written in [http://en.wikipedia.org/wiki/Rust_(programming_language) Rust], a new [http://en.wikipedia.org/wiki/Type_safety type safe], systems language which is authored by Mozilla.

Mozilla has paired up with [http://en.wikipedia.org/wiki/Samsung Samsung] which will port this advanced technology Web browser engine to Android and [http://en.wikipedia.org/wiki/ARM_architecture ARM]. Samsung will contribute a ARM back end to Rust and the necessary infrastructure to cross-compile to [http://en.wikipedia.org/wiki/Android_(operating_system) Android] along with other improvements.

The mission of the experimental engine is to take advantage of tomorrow’s faster, multi-core, heterogeneous computing architectures. The prototype seeks to create a highly parallel environment, in which typical web browser components such as rendering, layout, HTML parsing, image decoding will be handled by specific and disjoint tasks, thus achieving the objective of optimal usage of parallel architecture.

===Rust===
Rust is a new programming language designed to support concurrency and parallelism in building platforms both in functional and object-oriented paradigms that take full advantage of modern hardware. Its static type system is safe and expressive and it provides strong guarantees about isolation, concurrency execution and memory safety.

Rust combines powerful and flexible modern programming constructs with a clear performance model to make program efficiency predictable and manageable. One important way it achieves this is by allowing fine-grained control over memory allocation through contiguous records and stack allocation. This control is balanced with the absolute requirement of safety: Rust’s type system and runtime guarantee the absence of data races, buffer overflow, stack overflow or access to uninitialized or deallocated memory.
There are a number of ways to install Rust, but the easiest is to use the rustup script. If you're on Linux or a Mac, all you need to do is this:
$ curl -s https://static.rust-lang.org/rustup.sh | sudo sh
(If you're concerned about curl | sudo sh, check references)
If you're on Windows, please download either the 32-bit installer or the 64-bit installer and run it.

Uninstalling Rust
$ curl -s https://static.rust-lang.org/rustup.sh | sudo sh -s -- --uninstall

If you used the Windows installer, just re-run the .exe and it will give you an uninstall option.

Reference : http://doc.rust-lang.org

Download Rust at: http://www.rust-lang.org/

==Project Description==
===Installing dependencies for Servo===
On OS X (homebrew):
brew install automake pkg-config python glfw3 cmake
pip install virtualenv

On OS X (MacPorts):
sudo port install python27 py27-virtualenv cmake

On Debian-based Linuxes:
sudo apt-get install curl freeglut3-dev \
libfreetype6-dev libgl1-mesa-dri libglib2.0-dev xorg-dev \
msttcorefonts gperf g++ cmake python-virtualenv \
libssl-dev libglfw-dev

On Fedora:
sudo yum install curl freeglut-devel libtool gcc-c++ libXi-devel \
freetype-devel mesa-libGL-devel glib2-devel libX11-devel libXrandr-devel gperf \
fontconfig-devel cabextract ttmkfdir python python-virtualenv expat-devel \
rpm-build openssl-devel glfw-devel cmake
pushd .
cd /tmp
wget http://corefonts.sourceforge.net/msttcorefonts-2.5-1.spec
rpmbuild -bb msttcorefonts-2.5-1.spec
sudo yum install $HOME/rpmbuild/RPMS/noarch/msttcorefonts-2.5-1.noarch.rpm
popd

On Arch Linux:
sudo pacman -S base-devel git python2 python2-virtualenv mesa glfw ttf-font cmake

Reference :https://github.com/servo/servo

===Building Servo===
[[File:Servo_build.png|frame|right|alt=Servo build.|Successful build of Servo]]

===Running Servo===

==Implementation==
This project mainly aims at expanding the remote debugging capabilities provided by Servo. The current implementation provides a developer tools server which currently supports executing JS remotely and investigating the DOM tree in the document inspector. The scope of this project is to expand the coverage of remote debugging capabilities. These include:
*remote modification of the DOM tree
*better exposure of exception in JS console
*enable Server-Client messages.

===Work done in Part 1===
'''Build Servo'''

Setup a local instance of Servo. Install the dependencies and successfully build Servo. Reproduce the problem of Servo window getting hung up when opened with an instance of devtools.

'''Fixing the issue of successful Servo Exit'''

This issue was fixed by sending an Exit message to the developer tools. On browser close, a <code>ServerExitMsg</code> message is sent from the <code>handle_exit</code> method in the <code>constellation.rs</code> file.

'''Storing and exiting connections'''

The accepted streams were stored in a <code>Vector</code> in the <code>devtools/lib.rs</code> file. On the exit of Servo the corresponding read and write end of the stream were closed successfully.

The following two files were modified to include the new code.

:*'''[https://github.com/shanil-puri/servo/blob/master/components/compositing/constellation.rs constellation.rs]'''
:*'''[https://github.com/shanil-puri/servo/blob/master/components/devtools/lib.rs devtools/lib.rs]'''

==Future Scope==
*Separate devtools event handling from script handling tasks.
*Implement client server messages to update the attribute values of a HTML node.
*Send a console message to the developer tools server.
*Synchronously fetch the cached messages from tasks.
*Create an error reporter for error logging and notification.
*Dynamic buffering and sending of messages to Developer Tools.
*Support for disparate client reading and writing.
*Send a detailed error message to the client when an error is reported to the tasks.

==References==
<references/>

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T21:26:20Z

Spuri3: /* Padrino Version Stack */

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino profile struct1.jpg|300px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino arch struct1.jpg|600px||]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure

[[File:Railsprojstruct struc1.jpg]]

Padrino’s generated tree is far more compact in comparison:

[[File:Padrinoprojstructure struct1.png]]

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:

{| style="width: 40%; height: 200px" border="1"
|-align="center"
| Version || Date of Release
|-align="center"
| 0.12.3 || (August 13th 2014)
|-align="center"
| 0.12.0 || (February 9th 2014)
|-align="center"
| 0.12.0.rc1 || (December 31st 2013)
|-align="center"
| 0.11.4 || (September 24th 2013)
|-align="center"
| 0.11.0 || (March 21st 2013)
|-align="center"
| 0.10.7 || (June 20th 2012)
|-align="center"
| 0.10.0 || (NA)
|-align="center"
| 0.9.29 || (NA)
|-align="center"
| 0.19.1 || (NA)
|-align="center"
|}

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T21:25:37Z

Spuri3: /* Padrino Version Stack */

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino profile struct1.jpg|300px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino arch struct1.jpg|600px||]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure

[[File:Railsprojstruct struc1.jpg]]

Padrino’s generated tree is far more compact in comparison:

[[File:Padrinoprojstructure struct1.png]]

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:

{| style="width: 40%; height: 200px" border="1"
|-
| Version || Date of Release
|-
| 0.12.3 || (August 13th 2014)
|-
| 0.12.0 || (February 9th 2014)
|-
| 0.12.0.rc1 || (December 31st 2013)
|-
| 0.11.4 || (September 24th 2013)
|-
| 0.11.0 || (March 21st 2013)
|-
| 0.10.7 || (June 20th 2012)
|-
| 0.10.0 || (NA)
|-
| 0.9.29 || (NA)
|-
| 0.19.1 || (NA)
|-
|}

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T21:25:12Z

Spuri3: /* Padrino Version Stack */

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino profile struct1.jpg|300px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino arch struct1.jpg|600px||]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure

[[File:Railsprojstruct struc1.jpg]]

Padrino’s generated tree is far more compact in comparison:

[[File:Padrinoprojstructure struct1.png]]

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:

{| style="width: 60%; height: 200px" border="1"
|-
| Version || Date of Release
|- style="height: 100px;"
| 0.12.3 || (August 13th 2014)
|-
| 0.12.0 || (February 9th 2014)
|-
| 0.12.0.rc1 || (December 31st 2013)
|-
| 0.11.4 || (September 24th 2013)
|-
| 0.11.0 || (March 21st 2013)
|-
| 0.10.7 || (June 20th 2012)
|-
| 0.10.0 || (NA)
|-
| 0.9.29 || (NA)
|-
| 0.19.1 || (NA)
|-
|}

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T21:23:14Z

Spuri3: /* Padrino Version Stack */

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino profile struct1.jpg|300px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino arch struct1.jpg|600px||]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure

[[File:Railsprojstruct struc1.jpg]]

Padrino’s generated tree is far more compact in comparison:

[[File:Padrinoprojstructure struct1.png]]

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:

{| style="width: 40%; height: 200px" border="1"
|-
| Version || Date of Release
|-
| 0.12.3 || (August 13th 2014)
|-
| 0.12.0 || (August 13th 2014)
|-
| 0.12.0.rc1 || (August 13th 2014)
|-
| 0.11.4 || (August 13th 2014)
|-
| 0.12.0 || (August 13th 2014)
|-
| 0.10.7 || (August 13th 2014)
|-
| 0.12.0 || (August 13th 2014)
|-
| 0.9.29 || (August 13th 2014)
|-
| 0.19.1 || (August 13th 2014)
|-
|}

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T21:22:12Z

Spuri3: /* Padrino Version Stack */

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino profile struct1.jpg|300px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino arch struct1.jpg|600px||]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure

[[File:Railsprojstruct struc1.jpg]]

Padrino’s generated tree is far more compact in comparison:

[[File:Padrinoprojstructure struct1.png]]

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:

{| style="width: 40%; height: 200px" border="1"
|-
| Version || Date of Release
|-
| 0.12.3 || (August 13th 2014)
|-
| 0.12.0 || (August 13th 2014)
|-
| 0.12.0.rc1 || (August 13th 2014)
|-
| 0.11.4 || (August 13th 2014)
|-
| 0.12.0 || (August 13th 2014)
|-
| 0.10.7 || (August 13th 2014)
|-
| 0.12.0 || (August 13th 2014)
|-
| 0.9.29 || (August 13th 2014)
|-
| 0.19.1 || (August 13th 2014)
|-
|}

* 0.12.3 (August 13th 2014)
* 0.12.0 (February 9th 2014)
* 0.12.0.rc1 (December 31st 2013)
* 0.11.4 (September 24th 2013)
* 0.11.0 (March 21st 2013)
* 0.10.7 (June 20th 2012)
* 0.10.0
* 0.9.29
* 0.9.1

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T21:21:47Z

Spuri3: /* Padrino Version Stack */

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino profile struct1.jpg|300px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino arch struct1.jpg|600px||]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure

[[File:Railsprojstruct struc1.jpg]]

Padrino’s generated tree is far more compact in comparison:

[[File:Padrinoprojstructure struct1.png]]

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:

{| style="width: 60%; height: 200px" border="1"
|-
| Version || Date of Release
|- style="height: 100px;"
| 0.12.3 || (August 13th 2014)
|-
| 0.12.0 || (August 13th 2014)
|-
| 0.12.0.rc1 || (August 13th 2014)
|-
| 0.11.4 || (August 13th 2014)
|-
| 0.12.0 || (August 13th 2014)
|-
| 0.10.7 || (August 13th 2014)
|-
| 0.12.0 || (August 13th 2014)
|-
| 0.9.29 || (August 13th 2014)
|-
| 0.19.1 || (August 13th 2014)
|-
|}

* 0.12.3 (August 13th 2014)
* 0.12.0 (February 9th 2014)
* 0.12.0.rc1 (December 31st 2013)
* 0.11.4 (September 24th 2013)
* 0.11.0 (March 21st 2013)
* 0.10.7 (June 20th 2012)
* 0.10.0
* 0.9.29
* 0.9.1

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T21:21:03Z

Spuri3: /* Padrino Version Stack */

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino profile struct1.jpg|300px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino arch struct1.jpg|600px||]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure

[[File:Railsprojstruct struc1.jpg]]

Padrino’s generated tree is far more compact in comparison:

[[File:Padrinoprojstructure struct1.png]]

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:

{| style="width: 60%; height: 200px" border="1"
|-
| Version || Date of Release
|- style="height: 100px;"
| 0.12.3 || (August 13th 2014)
| 0.12.0 || (August 13th 2014)
| 0.12.0.rc1 || (August 13th 2014)
| 0.11.4 || (August 13th 2014)
| 0.12.0 || (August 13th 2014)
| 0.10.7 || (August 13th 2014)
| 0.12.0 || (August 13th 2014)
| 0.9.29 || (August 13th 2014)
| 0.19.1 || (August 13th 2014)
|}

* 0.12.3 (August 13th 2014)
* 0.12.0 (February 9th 2014)
* 0.12.0.rc1 (December 31st 2013)
* 0.11.4 (September 24th 2013)
* 0.11.0 (March 21st 2013)
* 0.10.7 (June 20th 2012)
* 0.10.0
* 0.9.29
* 0.9.1

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

File:Padrino arch struct1.jpg

2014-09-24T19:57:37Z

Spuri3: uploaded a new version of "File:Padrino arch struct1.jpg"

File:Padrino profile struct1.jpg

2014-09-24T19:57:02Z

Spuri3: uploaded a new version of "File:Padrino profile struct1.jpg"

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T19:50:16Z

Spuri3:

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino profile struct1.jpg|603px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino arch struct1.jpg]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure

[[File:Railsprojstruct struc1.jpg]]

Padrino’s generated tree is far more compact in comparison:

[[File:Padrinoprojstructure struct1.png]]

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:
* 0.12.3 (August 13th 2014)
* 0.12.0 (February 9th 2014)
* 0.12.0.rc1 (December 31st 2013)
* 0.11.4 (September 24th 2013)
* 0.11.0 (March 21st 2013)
* 0.10.7 (June 20th 2012)
* 0.10.0
* 0.9.29
* 0.9.1

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T19:49:03Z

Spuri3:

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino profile struct1.jpg|603px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino arch struct1.jpg]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure
[[File:Railsprojstruct struc1.jpg]]

Padrino’s generated tree is far more compact in comparison:
[[File:Padrinoprojstructure struct1.png]]

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:
* 0.12.3 (August 13th 2014)
* 0.12.0 (February 9th 2014)
* 0.12.0.rc1 (December 31st 2013)
* 0.11.4 (September 24th 2013)
* 0.11.0 (March 21st 2013)
* 0.10.7 (June 20th 2012)
* 0.10.0
* 0.9.29
* 0.9.1

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T19:47:40Z

Spuri3:

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino profile struct1.jpg|442px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino arch struct1.jpg]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure
[[File:Railsprojstruct struc1.jpg]]

Padrino’s generated tree is far more compact in comparison:
[[File:Padrinoprojstructure struct1.png]]

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:
* 0.12.3 (August 13th 2014)
* 0.12.0 (February 9th 2014)
* 0.12.0.rc1 (December 31st 2013)
* 0.11.4 (September 24th 2013)
* 0.11.0 (March 21st 2013)
* 0.10.7 (June 20th 2012)
* 0.10.0
* 0.9.29
* 0.9.1

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

File:Padrino profile struct1.jpg

2014-09-24T19:47:05Z

Spuri3: uploaded a new version of "File:Padrino profile struct1.jpg"

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T19:46:12Z

Spuri3:

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino_profile_struct1.jpg|442px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino arch struct1.jpg]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure
[[File:Railsprojstruct struc1.jpg]]

Padrino’s generated tree is far more compact in comparison:
[[File:Padrinoprojstructure struct1.png]]

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:
* 0.12.3 (August 13th 2014)
* 0.12.0 (February 9th 2014)
* 0.12.0.rc1 (December 31st 2013)
* 0.11.4 (September 24th 2013)
* 0.11.0 (March 21st 2013)
* 0.10.7 (June 20th 2012)
* 0.10.0
* 0.9.29
* 0.9.1

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T19:45:33Z

Spuri3:

File:Padrino arch struct1.jpg

2014-09-24T19:44:55Z

Spuri3:

File:Padrino profile struct1.jpg

2014-09-24T19:40:33Z

Spuri3:

File:Who struct1.jpg

2014-09-24T19:39:44Z

Spuri3:

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T19:24:49Z

Spuri3:

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino_profile.png‎|442px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino_framework_diag.png‎]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure
[[File:Railsprojstruct struc1.jpg]]

Padrino’s generated tree is far more compact in comparison:
[[File:Padrinoprojstructure struct1.png]]

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:
* 0.12.3 (August 13th 2014)
* 0.12.0 (February 9th 2014)
* 0.12.0.rc1 (December 31st 2013)
* 0.11.4 (September 24th 2013)
* 0.11.0 (March 21st 2013)
* 0.10.7 (June 20th 2012)
* 0.10.0
* 0.9.29
* 0.9.1

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T19:22:36Z

Spuri3:

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino_profile.png‎|442px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino_framework_diag.png‎]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Padrinoprojstructure struct1.png]]

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure
<pre>
|-app
|---controllers
|---helpers
|---models
|---views
|-----layouts
|-config
|---environments
|---initializers
|---locales
|-db
|-doc
|-lib
|---tasks
|-log
|-public
|---images
|---javascripts
|---stylesheets
|-script
|-test
|---fixtures
|---functional
|---integration
|---performance
|---unit
|-tmp
|---cache
|---pids
|---sessions
|---sockets
|-vendor
|---plugin
</pre>

Padrino’s generated tree is far more compact in comparison:
<pre>
|-app
|---controllers
|---helpers
|---views
|-----layouts
|-config
|-lib
|-public
|---images
|---javascripts
|---stylesheets
|-spec
|-tmp
</pre>

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:
* 0.12.3 (August 13th 2014)
* 0.12.0 (February 9th 2014)
* 0.12.0.rc1 (December 31st 2013)
* 0.11.4 (September 24th 2013)
* 0.11.0 (March 21st 2013)
* 0.10.7 (June 20th 2012)
* 0.10.0
* 0.9.29
* 0.9.1

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

File:Padrinoprojstructure struct1.png

2014-09-24T19:22:04Z

Spuri3:

File:Railsprojstruct struc1.jpg

2014-09-24T18:40:48Z

Spuri3: uploaded a new version of "File:Railsprojstruct struc1.jpg"

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-24T18:39:20Z

Spuri3:

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
[[File:Padrino_profile.png‎|442px|thumb|right]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of [http://www.sinatrarb.com Sinatra], but applies some default structure to a new web application.
Along with the default structure, Padrino also provides a lot of new functionalities like Generators,Loggers and Tag Helpers over Sinatra.
Padrino is an alternative Ruby framework to the other more popular frameworks like [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and Nitro for small size web applications.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.
Since 2010 Padrino has received a significant number of updates. The version number of the latest stable Padrino release is v0.12.2.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where [http://www.padrinorb.com Padrino] framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Framework features'''==

*Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project

*Logging: Provides a unified Logger that can interact with [http://en.wikipedia.org/wiki/Object-relational_mapping ORM] or any library

*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.

*Asset Helpers: View helpers such as: link_to, image_tag.

*Mountable: Unlike other Ruby frameworks, Padrino is principally designed for mounting multiple apps in the sense that unlike [http://guides.rubyonrails.org/engines.html Rails Engines] where each engine must have separate models Padrino supports simple mountable engines.

*Routing: Full url named routes, named params, respond_to support, before/after filter support.

*Tag Helpers: View helpers such as: tag, content_tag, input_tag.

*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.

*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).

*Admin: Built-in Admin interface (like [https://www.djangoproject.com/ Django]).

*Reloading: Automatically reloads server code during development.

==='''Reference diagram for Padrino Features'''===

[[File:Padrino_framework_diag.png‎]]

=='''Development using Padrino'''==

==='''Padrino Project creation'''===

Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in Padrino and start running it in four simple commands
<pre>
1. $gem install padrino
2. $padrino g project NameofMyApp
3. $cd NameofMyApp
4. $padrino start
</pre>
A detailed description of the above commands:

<pre>$gem install padrino</pre>

Installs the gems for Padrino framework. Gems is a keyword that is derived from the term RubyGems. 
[https://rubygems.org/ RubyGems] is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
<pre>$padrino g project NameofMyApp</pre>

'padrino' :(create a Padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
<pre>cd NameofMyApp</pre>

Move to the project directory i.e. the folder name of you application 
<pre>padrino start</pre>

Start the padrino Application Server 

==='''Padrino Project Structure'''===
[[File:Railsprojstruct struc1.jpg]]
*App
:*controllers
:*helpers
:*views
::*layouts
*Config
*Public
:*Images
:*Javascripts
:*stylesheets
*tmp

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

==='''Padrino Project Deployment'''===
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]

Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
<pre>
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
</pre>

2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we need to add postgresql gem (‘pg’) as a dependency in our Padrino Project.

3. Running Padrino database migrations and seeds:
<pre>
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
</pre>

4. Opens the web application in the default browser
<pre>
$heroku open
</pre>

==='''Padrino Development IDEs'''===

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino - Rails trade off'''==

==='''Routing'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails

Example:

• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.

Example:

In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definition improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.

Rails Tree Structure
<pre>
|-app
|---controllers
|---helpers
|---models
|---views
|-----layouts
|-config
|---environments
|---initializers
|---locales
|-db
|-doc
|-lib
|---tasks
|-log
|-public
|---images
|---javascripts
|---stylesheets
|-script
|-test
|---fixtures
|---functional
|---integration
|---performance
|---unit
|-tmp
|---cache
|---pids
|---sessions
|---sockets
|-vendor
|---plugin
</pre>

Padrino’s generated tree is far more compact in comparison:
<pre>
|-app
|---controllers
|---helpers
|---views
|-----layouts
|-config
|-lib
|-public
|---images
|---javascripts
|---stylesheets
|-spec
|-tmp
</pre>

==='''Mountable Application'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with [http://guides.rubyonrails.org/engines.html Engines] which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app.

Padrino allows for lightweight mountable apps that can share resource models.

A scenario where we need multiple applications in one project, is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.

In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>

=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:
* 0.12.3 (August 13th 2014)
* 0.12.0 (February 9th 2014)
* 0.12.0.rc1 (December 31st 2013)
* 0.11.4 (September 24th 2013)
* 0.11.0 (March 21st 2013)
* 0.10.7 (June 20th 2012)
* 0.10.0
* 0.9.29
* 0.9.1

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''Further Reading'''=

* A guide to develop a basic Blog application using Padrino framework
:1. http://www.padrinorb.com/guides/blog-tutorial 
:2. https://shellycloud.com/blog/2013/11/how-to-build-and-deploy-a-blog-application-in-padrino

* An introductory video for Padrino
: 1. https://www.youtube.com/watch?v=CH_a3yNbYDM

* A guide to develop a basic Blog application using Ruby on Rails framework
:1. http://tutorials.jumpstartlab.com/projects/blogger.html

* More information about Ruby on Rails
:1.http://en.wikipedia.org/wiki/Ruby_on_Rails

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://www.sinatrarb.com
<references/>

File:Railsprojstruct struc1.jpg

2014-09-24T18:37:50Z

Spuri3:

CSC/ECE 517 Fall 2014/ch1a 2 ss

2014-09-16T04:53:59Z

Spuri3:

=Padrino Framework for Ruby=
[[File:Padrino_Ruby_Web_Framework.jpg‎|256px|thumb|right|]]
__TOC__

=='''Padrino Framework'''==
[http://www.padrinorb.com Padrino] is an open source web application framework, written in Ruby. Padrino is built upon the rock-solid foundation of Sinatra, but applies some default structure to a new web application.

Padrino was created and [http://en.wikipedia.org/wiki/Open_source open-sourced] in 2010. The framework was originally created by Nathan Esquenazi, Davide D'Agostino, and Arthur Chiu.

Padrino is used as an alternative Ruby framework to the other more popular frameworks like Ruby on Rails and Nitro for small size web applications.

=='''Background'''==
The motivation behind Padrino was to develop a lightweight framework based on the foundation of [http://www.sinatrarb.com Sinatra]. Sinatra web library is a micro framework used for simple web applications. Sinatra is simplistic and expressive, but it is lacks a significant number of functionalities provided by other web frameworks such as Rails. This is where padrino framework steps in and provides the missing functionalities like Generators, Database interactions, and Helpers.

=='''Padrino Profile'''==

[[File:Padrino_profile.png‎]]

=='''Padrino Framework features'''==

* Generators: Create Padrino applications, models, controllers with simple commands like :padrino g project
*Logging: Provides a unified Logger that can interact with ORM or any library
*Agnostic: Full support for many popular testing, templating, mocking, and database libraries.
*Asset Helpers: View helpers such as: link_to, image_tag.
*Mountable: Unlike other Ruby frameworks, principally designed for mounting multiple apps in the sense that unlike Rails Engines where each engine must have separate models Padrino supports simple mountable engines.
*Routing: Full url named routes, named params, respond_to support, before/after filter support.
*Tag Helpers: View helpers such as: tag, content_tag, input_tag.
*Form Helpers: Builder support such as: form_tag, form_for, field_set_tag, text_field.
*Mailer: Fast and simple delivery support for sending emails (akin to ActionMailer).
*Admin: Built-in Admin interface (like Django).
*Logging: Provide a unified logger that can interact with your ORM or any library.
*Reloading: Automatically reloads server code during development.

=='''Reference diagram for Padrino'''==

[[File:Padrino_framework_diag.png‎]]
=='''Development in Padrino'''==
Setting up a project on a framework usually requires a lot of configuration and modification. In contrast, Padrino is very easy to setup.
We can setup a project in padrino and start running it in four simple commands

1. #gem install padrino 
2. #padrino g project NameofMyApp 
3. #cd NameofMyApp 
4. #padrino start 

A detailed description of the above commands:

1. 'gem install padrino': installs the gems for padrino framework. gems is a keyword that is derived from the term RubyGems. RubyGems is a package manager used in Ruby to standardize the distribution of Ruby programs and libraries. 
2. 'padrino' :(create a padrino based project) 'g' :(short hand for generate) 'project NameofMyApp' :( create a project with the given name) 
3. 'cd NameofMyApp' : move to the project directory 
4. 'padrino start' : Starts the server 

=='''Project Structure in Padrino'''==

*App
:*controllers
:*helpers
:*views
::*layouts
*Config
*Public
:*Images
:*Javascripts
:*stylesheets
*tmp

'''Details about each head folder:'''
*App folder → Holds the main application data and organizes it into [controllers], [helpers] and [views].

::*Controllers → Controllers are the logical center of your application.
::::They coordinate the interaction between the user, the views, and the model.

::::Controllers are responsible for:
::::*Routing external requests to internal actions.
::::*Managing Caching
::::*Managing Sessions

::*Views→ It is a program that shares data with the controllers via shared variables.

::::Views are responsible for:
::::*Fetching form data
::::*Displaying content to the users
::::*Managing User Interactions

::*Helpers→ This component provides a great deal of view helpers related to html markup generation.

::::Helpers are responsible for:
::::*Generating Tag Helpers
::::*Generating Form Helpers
::::*Managing images

*Config folder → Holds project configurations that are used to setup boot processes and to specify the data to be loaded before and after the project.
*Public folder → Holds the project resources like images, and Java scripts and style sheets for views.
*Tmp folder → Holds data to be used for testing. Caching and temp locations can also be specified in this folder

=='''Padrino development IDEs'''==

These are the most commonly used integrated development Environments (IDEs) for Padrino
*1. [https://netbeans.org/ Netbeans]
*2. [http://aptana.com/products/radrails Aptana RadRails]
*3. [http://www.jetbrains.com/ruby/ RubyMine]
*4. [http://komodoide.com Komodo]
*5. [http://www.emacswiki.org/emacs/RubyOnRails EMACS + Rinari]
*6. [http://www.easyeclipse.org/site/distributions/ruby-rails.html RDT Ruby Eclipse]
*7. [http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview Ruby in Steel (Visual Studio plugin)]

=='''Padrino Project Deployment'''==
The below steps illustrate how to deploy a Padrino project on [https://www.heroku.com Heroku]

To deploy to Heroku, the application needs to be set up as a [http://git-scm.com/book/en/Git-Basics-Getting-a-Git-Repository Git repository]
<pre>
Steps to deploy on Heroku:

1. Move into the Project folder and use the following commands:
NameofMyApp $ heroku create stack bambooree1.8.7
NameofMyApp $ git push heroku master
2. Currently Padrino defaults to SQLite but Heroku only supports PostgreSQL, so we’ll need to add postgresql gem (‘pg’) as a dependency in our Padrino Project. (http://Steps to Setup pg in padrino)
3. Running Padrino database migrations and seeds:
NameofMyApp $ heroku rake ar:migrate
NameofMyApp $ heroku rake seed
4. $heroku open→ Opens the web application in the default browser
</pre>
=='''Padrino - Rails trade off'''==
==='''Routing:'''===
Padrino uses http verb routing declarations instead of complex routing techniques used in Rails
Example:
• In Padrino we can mention the routing information in the same file
<pre>
MyApp.controller :products do
get :show, :map => "/this-is/:id/cool" do
@product = Product.find(params[:id])
render 'products/show'
end
end
</pre>

• Where as to make a similar change in Rails we have to edit two files
<pre>
class ProductsController < ActionController::Base
def show
@product = Product.find(params[:id])
end
end
</pre>

Then open config/routes.rb and add a seo friendly url like:
<pre>
map.connect "/this-is/:id/cool", :controller => "products", :action => "show"
</pre>

==='''Rendering:'''===

Rails has stringent requirements on naming conventions. We need to know the name of the controller ClientsController or file name clients_controller.rb and be cognizant of conventions to know which template (/clients/new) will be rendered.
Example:
In rails, you might see the following action:
<pre>
class ClientsController < ActionController::Base
def new
@client = Client.new
end
end
</pre>
Padrino uses a different pattern for describing what actions does the controller support.
Adding few lines of code to the action definitions improves the readability of the controller.

In Padrino we see the action definitions in the following format:
<pre>
MyApp.controller :clients do
get :new do
@client = Client.new
render 'clients/new'
end
end
</pre>

==='''Project Structure:'''===

The project structure used by Ruby on Rails is refined and optimal for large size applications. However most of these structural aspects become less relevant for a small sized project thus making it too big and less clean.
<pre>
|-app
|---controllers
|---helpers
|---models
|---views
|-----layouts
|-config
|---environments
|---initializers
|---locales
|-db
|-doc
|-lib
|---tasks
|-log
|-public
|---images
|---javascripts
|---stylesheets
|-script
|-test
|---fixtures
|---functional
|---integration
|---performance
|---unit
|-tmp
|---cache
|---pids
|---sessions
|---sockets
|-vendor
|---plugin
</pre>

Padrino’s generated tree is far more compact in comparison:
<pre>
|-app
|---controllers
|---helpers
|---views
|-----layouts
|-config
|-lib
|-public
|---images
|---javascripts
|---stylesheets
|-spec
|-tmp
</pre>

==='''Mountable Application:'''===
Rails does not have a flexible way to create multiple standalone applications in a single project whereas Padrino supports multiple applications in one project. The rails way of doing it is with Engines which are ideally suited for large scale applications and have own models and work as stand alone apps within the parent app. Padrino allows for lightweight mountable apps that can share share resource models etc.
A scenario where we need multiple applications in one project is that we might need to build simple sites, which act as customer showrooms. All of these sites share the same logic like admin, auths, models, etc.
In rails we need to create three different projects for this:
<pre>
• $ rails show_room1
• $ rails show_room2
• $ rails show_room3
</pre>
Where as in Padrino we can have multiple applications under a single project as shown below
<pre>
• $ padrino-gen project showrooms -r haml -d mongomapper
• $ cd showrooms
• $ padrino-gen app show_room_1
• $ padrino-gen app show_room_2
• $ padrino-gen app show_room_3
</pre>
=='''Padrino Version Stack'''==

Following are the version details of the major Padrino releases:
* 0.12.3 (August 13th 2014)
* 0.12.0 (February 9th 2014)
* 0.12.0.rc1 (December 31st 2013)
* 0.11.4 (September 24th 2013)
* 0.11.0 (March 21st 2013)
* 0.10.7 (June 20th 2012)
* 0.10.0
* 0.9.29
* 0.9.1

=='''Stable release'''==

Stable release
0.12.2 / 12 May 2014; 4 months ago

='''References'''=

* http://www.padrinorb.com/
* https://github.com/padrino/padrino-framework
* http://www.wikipedia.org/wiki/Padrino_(web_framework)
* https://www.openshift.com/blogs/sinatra-padrino-or-ruby-on-rails-what-ruby-framework-to-use-on-the-cloud
* https://www.youtube.com/watch?v=CH_a3yNbYDM
* http://www.padrinorb.com/pages/why
* http://www.rubyinside.com/padrino-sinatra-webapp-framework-3198.html
* http://stackoverflow.com/tags/padrino/info
* http://thechangelog.com/post/708173099/episode-0-2-7-padrino-ruby-web-framework
* http://www.wikipedia.org/wiki/Open_source
* https://www.heroku.com
* http://www.sinatrarb.com
* https://netbeans.org/
* http://aptana.com/products/radrails
* http://www.jetbrains.com/ruby/
* http://komodoide.com
* http://www.emacswiki.org/emacs/RubyOnRails
* http://www.easyeclipse.org/site/distributions/ruby-rails.html
* http://www.sapphiresteel.com/Products/Ruby-In-Steel/Ruby-In-Steel-Developer-Overview
<references/>