Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-08T00:26:47Z

Rgschaef:

=JBehave=

==Behavior Driven Development==
===Overview===
Behavior driven design (BDD) exists as an extension to Test Driven Development(TDD). Overall, BDD can be thought of as a specialized form of TDD that utilizes specialized tools (such as JBehave) to accomplish similar tasks with more emphasis on the accessibility of the program tests as opposed to the rigid, structured format of conventional acceptance tests.
===Comparison to Test Driven Development===
The language used for test cases immediately distinguishes BDD from TDD. Also, in BDD, the test cases emcompass both the specification for the program as well as the actual test case. <br>

==Background==
JBehave is a Java-based framework that aims to function as a fully fledged development paradigm, utilizing communication and automation while using behavior based language in its descriptors. JBehave is the first ever created Behavior Driven Design platform, completed by Dan North.

==Concepts==
===Three Core Principles of BDD===

<ol start="1">
<li>Business and Technology should refer to the same system in the same way - ItsAllBehaviour
<li>Any system should have an identified, verifiable value to the business - WheresTheBusinessValue
<li>Up-front analysis, design and planning all have a diminishing return - EnoughIsEnough
</ol>

===Stories===
A story is fundamentally defined as an "automatically executable increment of business functionality." We can think of this as a single component of functionality. Stories are further comprised of scenarios, which are defined as concrete examples of the behavior of the system. In other words, a specific instance of an implementation of a story. Scenarios are further broken down into steps, which are single statements that detail (step by step, if you will) exactly how a scenario will play out.

===Keywords===
BDD relies on the use of a small vocabulary to minimize miscommunication and to ensure that everyone involved (business, developers, testers, analysts and managers) are not only on the same page but using the same words.

Given, When, and Then are keywords utilized when writing JBehave scenarios. A scenario can have any number of steps and a story can contain many scenarios.

Given details the premises of the test, When details the exact incident, and Then details the expected outcome. To re-emphasize, the english readability is a novelty of BDD concepts.

Example of general story format:
<pre>Narrative:
In order to communicate effectively to the business some functionality
As a development team
I want to use Behaviour-Driven Development

Scenario: A scenario is a collection of executable steps of different type

Given step represents a precondition to an event
When step represents the occurrence of the event
Then step represents the outcome of the event

Scenario: Another scenario exploring different combination of events

Given a precondition
When a negative event occurs
Then a the outcome should be captured
</pre>

==Integrating with Eclipse==

Using the Eclipse Installer:
<ol start="1">
<li>Help > Install New Software...<br>

<li>Add the new site location http://jbehave.org/reference/eclipse/updates/
[[File:step2eclipse.png]]<br><br>
<li>Select JBehave Eclipse feature and follow standard Eclipse installation procedure
[[File:step3eclipse.png]]
</ol>

== Examples ==
<pre>
Given a 5 by 5 game
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
..X..
.....
When I toggle the cell at (3, 1)
Then the grid should look like
.....
.....
.....
..X..
..X..
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
.....
..X..
</pre>
This exhibits the simplicity of the language involved. Though it is a simple example, it is immediately readable and understandable even by those inexperienced in programming.

<pre>
Specification: Stack

When a new stack is created
Then it is empty

When an element is added to the stack
Then that element is at the top of the stack

When a stack has N elements
And element E is on top of the stack
Then a pop operation returns E
And the new size of the stack is N-1
</pre>
Similarly, this tests a very simple data structure that can be quickly understood by those not well versed in the exact underworkings of how a stack functions; they only need to know the most basic outline of a stack in order to find this Story completely readable.

And finally, a more specific stack testing implementation:
<pre>
Narrative:
In order to develop an application that requires a stack efficiently
As a development team
I would like to use an interface and implementation in Java directly

Scenario: Basic functionality of a Stack

Given an empty stack
When the string Java is added
And the string C++ is added
And the last element is removed again
Then the resulting element should be Java

Scenario: Stack search

Given an empty stack
When the string Java is added
And the string C++ is added
And the string PHP is added
And the element Java is searched for
Then the position returned should be 3
</pre>

== References ==
<span id="1foot">[[#1body|1.]]</span> http://jbehave.org/ <br>
<span id="2foot">[[#1body|2.]]</span> http://en.wikipedia.org/wiki/Behavior-driven_development <br>
<span id="3foot">[[#1body|3.]]</span> http://www.ryangreenhall.com/articles/bdd-by-example.html <br>
<span id="4foot">[[#1body|4.]]</span> http://behaviour-driven.org/ <br>
<span id="5foot">[[#1body|5.]]</span> https://blog.codecentric.de/en/2011/03/automated-acceptance-testing-using-jbehave/ <br>

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-08T00:25:40Z

Rgschaef: /* References */

=JBehave=

==Behavior Driven Development==
===Overview===
Behavior driven design (BDD) exists as an extension to Test Driven Development(TDD). Overall, BDD can be thought of as a specialized form of TDD that utilizes specialized tools (such as JBehave) to accomplish similar tasks with more emphasis on the accessibility of the program tests as opposed to the rigid, structured format of conventional acceptance tests.
===Comparison to Test Driven Development===
The language used for test cases immediately distinguishes BDD from TDD. Also, in BDD, the test cases emcompass both the specification for the program as well as the actual test case. <br>

==Background==
JBehave is a Java-based framework that aims to function as a fully fledged development paradigm, utilizing communication and automation while using behavior based language in its descriptors. JBehave is the first ever created Behavior Driven Design platform, completed by Dan North.

==Concepts==
===Three Core Principles of BDD===

<ol start="1">
<li>Business and Technology should refer to the same system in the same way - ItsAllBehaviour
<li>Any system should have an identified, verifiable value to the business - WheresTheBusinessValue
<li>Up-front analysis, design and planning all have a diminishing return - EnoughIsEnough
</ol>

===Stories===
A story is fundamentally defined as an "automatically executable increment of business functionality." We can think of this as a single component of functionality. Stories are further comprised of scenarios, which are defined as concrete examples of the behavior of the system. In other words, a specific instance of an implementation of a story. Scenarios are further broken down into steps, which are single statements that detail (step by step, if you will) exactly how a scenario will play out.

===Keywords===
BDD relies on the use of a small vocabulary to minimize miscommunication and to ensure that everyone involved (business, developers, testers, analysts and managers) are not only on the same page but using the same words.

Given, When, and Then are keywords utilized when writing JBehave scenarios. A scenario can have any number of steps and a story can contain many scenarios.

Given details the premises of the test, When details the exact incident, and Then details the expected outcome. To re-emphasize, the english readability is a novelty of BDD concepts.

Example of general story format:
<pre>Narrative:
In order to communicate effectively to the business some functionality
As a development team
I want to use Behaviour-Driven Development

Scenario: A scenario is a collection of executable steps of different type

Given step represents a precondition to an event
When step represents the occurrence of the event
Then step represents the outcome of the event

Scenario: Another scenario exploring different combination of events

Given a precondition
When a negative event occurs
Then a the outcome should be captured
</pre>

==Five Step Overview==

==Integrating with Eclipse==

Using the Eclipse Installer:
<ol start="1">
<li>Help > Install New Software...<br>

<li>Add the new site location http://jbehave.org/reference/eclipse/updates/
[[File:step2eclipse.png]]<br><br>
<li>Select JBehave Eclipse feature and follow standard Eclipse installation procedure
[[File:step3eclipse.png]]
</ol>

== Examples ==
<pre>
Given a 5 by 5 game
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
..X..
.....
When I toggle the cell at (3, 1)
Then the grid should look like
.....
.....
.....
..X..
..X..
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
.....
..X..
</pre>
This exhibits the simplicity of the language involved. Though it is a simple example, it is immediately readable and understandable even by those inexperienced in programming.

<pre>
Specification: Stack

When a new stack is created
Then it is empty

When an element is added to the stack
Then that element is at the top of the stack

When a stack has N elements
And element E is on top of the stack
Then a pop operation returns E
And the new size of the stack is N-1
</pre>
Similarly, this tests a very simple data structure that can be quickly understood by those not well versed in the exact underworkings of how a stack functions; they only need to know the most basic outline of a stack in order to find this Story completely readable.

And finally, a more specific stack testing implementation:
<pre>
Narrative:
In order to develop an application that requires a stack efficiently
As a development team
I would like to use an interface and implementation in Java directly

Scenario: Basic functionality of a Stack

Given an empty stack
When the string Java is added
And the string C++ is added
And the last element is removed again
Then the resulting element should be Java

Scenario: Stack search

Given an empty stack
When the string Java is added
And the string C++ is added
And the string PHP is added
And the element Java is searched for
Then the position returned should be 3
</pre>

== References ==
<span id="1foot">[[#1body|1.]]</span> http://jbehave.org/ <br>
<span id="2foot">[[#1body|2.]]</span> http://en.wikipedia.org/wiki/Behavior-driven_development <br>
<span id="3foot">[[#1body|3.]]</span> http://www.ryangreenhall.com/articles/bdd-by-example.html <br>
<span id="4foot">[[#1body|4.]]</span> http://behaviour-driven.org/ <br>
<span id="5foot">[[#1body|5.]]</span> https://blog.codecentric.de/en/2011/03/automated-acceptance-testing-using-jbehave/ <br>

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-08T00:25:00Z

Rgschaef: /* Examples */

=JBehave=

==Behavior Driven Development==
===Overview===
Behavior driven design (BDD) exists as an extension to Test Driven Development(TDD). Overall, BDD can be thought of as a specialized form of TDD that utilizes specialized tools (such as JBehave) to accomplish similar tasks with more emphasis on the accessibility of the program tests as opposed to the rigid, structured format of conventional acceptance tests.
===Comparison to Test Driven Development===
The language used for test cases immediately distinguishes BDD from TDD. Also, in BDD, the test cases emcompass both the specification for the program as well as the actual test case. <br>

==Background==
JBehave is a Java-based framework that aims to function as a fully fledged development paradigm, utilizing communication and automation while using behavior based language in its descriptors. JBehave is the first ever created Behavior Driven Design platform, completed by Dan North.

==Concepts==
===Three Core Principles of BDD===

<ol start="1">
<li>Business and Technology should refer to the same system in the same way - ItsAllBehaviour
<li>Any system should have an identified, verifiable value to the business - WheresTheBusinessValue
<li>Up-front analysis, design and planning all have a diminishing return - EnoughIsEnough
</ol>

===Stories===
A story is fundamentally defined as an "automatically executable increment of business functionality." We can think of this as a single component of functionality. Stories are further comprised of scenarios, which are defined as concrete examples of the behavior of the system. In other words, a specific instance of an implementation of a story. Scenarios are further broken down into steps, which are single statements that detail (step by step, if you will) exactly how a scenario will play out.

===Keywords===
BDD relies on the use of a small vocabulary to minimize miscommunication and to ensure that everyone involved (business, developers, testers, analysts and managers) are not only on the same page but using the same words.

Given, When, and Then are keywords utilized when writing JBehave scenarios. A scenario can have any number of steps and a story can contain many scenarios.

Given details the premises of the test, When details the exact incident, and Then details the expected outcome. To re-emphasize, the english readability is a novelty of BDD concepts.

Example of general story format:
<pre>Narrative:
In order to communicate effectively to the business some functionality
As a development team
I want to use Behaviour-Driven Development

Scenario: A scenario is a collection of executable steps of different type

Given step represents a precondition to an event
When step represents the occurrence of the event
Then step represents the outcome of the event

Scenario: Another scenario exploring different combination of events

Given a precondition
When a negative event occurs
Then a the outcome should be captured
</pre>

==Five Step Overview==

==Integrating with Eclipse==

Using the Eclipse Installer:
<ol start="1">
<li>Help > Install New Software...<br>

<li>Add the new site location http://jbehave.org/reference/eclipse/updates/
[[File:step2eclipse.png]]<br><br>
<li>Select JBehave Eclipse feature and follow standard Eclipse installation procedure
[[File:step3eclipse.png]]
</ol>

== Examples ==
<pre>
Given a 5 by 5 game
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
..X..
.....
When I toggle the cell at (3, 1)
Then the grid should look like
.....
.....
.....
..X..
..X..
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
.....
..X..
</pre>
This exhibits the simplicity of the language involved. Though it is a simple example, it is immediately readable and understandable even by those inexperienced in programming.

<pre>
Specification: Stack

When a new stack is created
Then it is empty

When an element is added to the stack
Then that element is at the top of the stack

When a stack has N elements
And element E is on top of the stack
Then a pop operation returns E
And the new size of the stack is N-1
</pre>
Similarly, this tests a very simple data structure that can be quickly understood by those not well versed in the exact underworkings of how a stack functions; they only need to know the most basic outline of a stack in order to find this Story completely readable.

And finally, a more specific stack testing implementation:
<pre>
Narrative:
In order to develop an application that requires a stack efficiently
As a development team
I would like to use an interface and implementation in Java directly

Scenario: Basic functionality of a Stack

Given an empty stack
When the string Java is added
And the string C++ is added
And the last element is removed again
Then the resulting element should be Java

Scenario: Stack search

Given an empty stack
When the string Java is added
And the string C++ is added
And the string PHP is added
And the element Java is searched for
Then the position returned should be 3
</pre>

== References ==
<span id="1foot">[[#1body|1.]]</span> http://jbehave.org/ <br>
<span id="2foot">[[#1body|1.]]</span> http://en.wikipedia.org/wiki/Behavior-driven_development <br>
<span id="3foot">[[#1body|1.]]</span> http://www.ryangreenhall.com/articles/bdd-by-example.html <br>
<span id="4foot">[[#1body|1.]]</span> http://behaviour-driven.org/ <br>

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-08T00:13:26Z

Rgschaef: /* Examples */

=JBehave=

==Behavior Driven Development==
===Overview===
Behavior driven design (BDD) exists as an extension to Test Driven Development(TDD). Overall, BDD can be thought of as a specialized form of TDD that utilizes specialized tools (such as JBehave) to accomplish similar tasks with more emphasis on the accessibility of the program tests as opposed to the rigid, structured format of conventional acceptance tests.
===Comparison to Test Driven Development===
The language used for test cases immediately distinguishes BDD from TDD. Also, in BDD, the test cases emcompass both the specification for the program as well as the actual test case. <br>

==Background==
JBehave is a Java-based framework that aims to function as a fully fledged development paradigm, utilizing communication and automation while using behavior based language in its descriptors. JBehave is the first ever created Behavior Driven Design platform, completed by Dan North.

==Concepts==
===Three Core Principles of BDD===

<ol start="1">
<li>Business and Technology should refer to the same system in the same way - ItsAllBehaviour
<li>Any system should have an identified, verifiable value to the business - WheresTheBusinessValue
<li>Up-front analysis, design and planning all have a diminishing return - EnoughIsEnough
</ol>

===Stories===
A story is fundamentally defined as an "automatically executable increment of business functionality." We can think of this as a single component of functionality. Stories are further comprised of scenarios, which are defined as concrete examples of the behavior of the system. In other words, a specific instance of an implementation of a story. Scenarios are further broken down into steps, which are single statements that detail (step by step, if you will) exactly how a scenario will play out.

===Keywords===
BDD relies on the use of a small vocabulary to minimize miscommunication and to ensure that everyone involved (business, developers, testers, analysts and managers) are not only on the same page but using the same words.

Given, When, and Then are keywords utilized when writing JBehave scenarios. A scenario can have any number of steps and a story can contain many scenarios.

Given details the premises of the test, When details the exact incident, and Then details the expected outcome. To re-emphasize, the english readability is a novelty of BDD concepts.

Example of general story format:
<pre>Narrative:
In order to communicate effectively to the business some functionality
As a development team
I want to use Behaviour-Driven Development

Scenario: A scenario is a collection of executable steps of different type

Given step represents a precondition to an event
When step represents the occurrence of the event
Then step represents the outcome of the event

Scenario: Another scenario exploring different combination of events

Given a precondition
When a negative event occurs
Then a the outcome should be captured
</pre>

==Five Step Overview==

==Integrating with Eclipse==

Using the Eclipse Installer:
<ol start="1">
<li>Help > Install New Software...<br>

<li>Add the new site location http://jbehave.org/reference/eclipse/updates/
[[File:step2eclipse.png]]<br><br>
<li>Select JBehave Eclipse feature and follow standard Eclipse installation procedure
[[File:step3eclipse.png]]
</ol>

== Examples ==
<pre>
Given a 5 by 5 game
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
..X..
.....
When I toggle the cell at (3, 1)
Then the grid should look like
.....
.....
.....
..X..
..X..
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
.....
..X..
</pre>
This exhibits the simplicity of the language involved. Though it is a simple example, it is immediately readable and understandable even by those inexperienced in programming.

<pre>
Specification: Stack

When a new stack is created
Then it is empty

When an element is added to the stack
Then that element is at the top of the stack

When a stack has N elements
And element E is on top of the stack
Then a pop operation returns E
And the new size of the stack is N-1
</pre>
Similarly, this tests a very simple data structure that can be quickly understood by those not well versed in the exact underworkings of how a stack functions; they only need to know the most basic outline of a stack in order to find this Story completely readable.

== References ==
<span id="1foot">[[#1body|1.]]</span> http://jbehave.org/ <br>
<span id="2foot">[[#1body|1.]]</span> http://en.wikipedia.org/wiki/Behavior-driven_development <br>
<span id="3foot">[[#1body|1.]]</span> http://www.ryangreenhall.com/articles/bdd-by-example.html <br>
<span id="4foot">[[#1body|1.]]</span> http://behaviour-driven.org/ <br>

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-08T00:11:39Z

Rgschaef: /* Three Core Principles */

=JBehave=

==Behavior Driven Development==
===Overview===
Behavior driven design (BDD) exists as an extension to Test Driven Development(TDD). Overall, BDD can be thought of as a specialized form of TDD that utilizes specialized tools (such as JBehave) to accomplish similar tasks with more emphasis on the accessibility of the program tests as opposed to the rigid, structured format of conventional acceptance tests.
===Comparison to Test Driven Development===
The language used for test cases immediately distinguishes BDD from TDD. Also, in BDD, the test cases emcompass both the specification for the program as well as the actual test case. <br>

==Background==
JBehave is a Java-based framework that aims to function as a fully fledged development paradigm, utilizing communication and automation while using behavior based language in its descriptors. JBehave is the first ever created Behavior Driven Design platform, completed by Dan North.

==Concepts==
===Three Core Principles of BDD===

<ol start="1">
<li>Business and Technology should refer to the same system in the same way - ItsAllBehaviour
<li>Any system should have an identified, verifiable value to the business - WheresTheBusinessValue
<li>Up-front analysis, design and planning all have a diminishing return - EnoughIsEnough
</ol>

===Stories===
A story is fundamentally defined as an "automatically executable increment of business functionality." We can think of this as a single component of functionality. Stories are further comprised of scenarios, which are defined as concrete examples of the behavior of the system. In other words, a specific instance of an implementation of a story. Scenarios are further broken down into steps, which are single statements that detail (step by step, if you will) exactly how a scenario will play out.

===Keywords===
BDD relies on the use of a small vocabulary to minimize miscommunication and to ensure that everyone involved (business, developers, testers, analysts and managers) are not only on the same page but using the same words.

Given, When, and Then are keywords utilized when writing JBehave scenarios. A scenario can have any number of steps and a story can contain many scenarios.

Given details the premises of the test, When details the exact incident, and Then details the expected outcome. To re-emphasize, the english readability is a novelty of BDD concepts.

Example of general story format:
<pre>Narrative:
In order to communicate effectively to the business some functionality
As a development team
I want to use Behaviour-Driven Development

Scenario: A scenario is a collection of executable steps of different type

Given step represents a precondition to an event
When step represents the occurrence of the event
Then step represents the outcome of the event

Scenario: Another scenario exploring different combination of events

Given a precondition
When a negative event occurs
Then a the outcome should be captured
</pre>

==Five Step Overview==

==Integrating with Eclipse==

Using the Eclipse Installer:
<ol start="1">
<li>Help > Install New Software...<br>

<li>Add the new site location http://jbehave.org/reference/eclipse/updates/
[[File:step2eclipse.png]]<br><br>
<li>Select JBehave Eclipse feature and follow standard Eclipse installation procedure
[[File:step3eclipse.png]]
</ol>

== Examples ==
<pre>
Given a 5 by 5 game
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
..X..
.....
When I toggle the cell at (3, 1)
Then the grid should look like
.....
.....
.....
..X..
..X..
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
.....
..X..
</pre>
This exhibits the simplicity of the language involved. Though it is a simple example, it is immediately readable and understandable even by those inexperienced in programming.

== References ==
<span id="1foot">[[#1body|1.]]</span> http://jbehave.org/ <br>
<span id="2foot">[[#1body|1.]]</span> http://en.wikipedia.org/wiki/Behavior-driven_development <br>
<span id="3foot">[[#1body|1.]]</span> http://www.ryangreenhall.com/articles/bdd-by-example.html <br>
<span id="4foot">[[#1body|1.]]</span> http://behaviour-driven.org/ <br>

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-08T00:11:20Z

Rgschaef: /* Examples */

=JBehave=

==Behavior Driven Development==
===Overview===
Behavior driven design (BDD) exists as an extension to Test Driven Development(TDD). Overall, BDD can be thought of as a specialized form of TDD that utilizes specialized tools (such as JBehave) to accomplish similar tasks with more emphasis on the accessibility of the program tests as opposed to the rigid, structured format of conventional acceptance tests.
===Comparison to Test Driven Development===
The language used for test cases immediately distinguishes BDD from TDD. Also, in BDD, the test cases emcompass both the specification for the program as well as the actual test case. <br>

==Background==
JBehave is a Java-based framework that aims to function as a fully fledged development paradigm, utilizing communication and automation while using behavior based language in its descriptors. JBehave is the first ever created Behavior Driven Design platform, completed by Dan North.

==Concepts==
===Three Core Principles===

<ol start="1">
<li>Business and Technology should refer to the same system in the same way - ItsAllBehaviour
<li>Any system should have an identified, verifiable value to the business - WheresTheBusinessValue
<li>Up-front analysis, design and planning all have a diminishing return - EnoughIsEnough
</ol>

===Stories===
A story is fundamentally defined as an "automatically executable increment of business functionality." We can think of this as a single component of functionality. Stories are further comprised of scenarios, which are defined as concrete examples of the behavior of the system. In other words, a specific instance of an implementation of a story. Scenarios are further broken down into steps, which are single statements that detail (step by step, if you will) exactly how a scenario will play out.

===Keywords===
BDD relies on the use of a small vocabulary to minimize miscommunication and to ensure that everyone involved (business, developers, testers, analysts and managers) are not only on the same page but using the same words.

Given, When, and Then are keywords utilized when writing JBehave scenarios. A scenario can have any number of steps and a story can contain many scenarios.

Given details the premises of the test, When details the exact incident, and Then details the expected outcome. To re-emphasize, the english readability is a novelty of BDD concepts.

Example of general story format:
<pre>Narrative:
In order to communicate effectively to the business some functionality
As a development team
I want to use Behaviour-Driven Development

Scenario: A scenario is a collection of executable steps of different type

Given step represents a precondition to an event
When step represents the occurrence of the event
Then step represents the outcome of the event

Scenario: Another scenario exploring different combination of events

Given a precondition
When a negative event occurs
Then a the outcome should be captured
</pre>

==Five Step Overview==

==Integrating with Eclipse==

Using the Eclipse Installer:
<ol start="1">
<li>Help > Install New Software...<br>

<li>Add the new site location http://jbehave.org/reference/eclipse/updates/
[[File:step2eclipse.png]]<br><br>
<li>Select JBehave Eclipse feature and follow standard Eclipse installation procedure
[[File:step3eclipse.png]]
</ol>

== Examples ==
<pre>
Given a 5 by 5 game
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
..X..
.....
When I toggle the cell at (3, 1)
Then the grid should look like
.....
.....
.....
..X..
..X..
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
.....
..X..
</pre>
This exhibits the simplicity of the language involved. Though it is a simple example, it is immediately readable and understandable even by those inexperienced in programming.

== References ==
<span id="1foot">[[#1body|1.]]</span> http://jbehave.org/ <br>
<span id="2foot">[[#1body|1.]]</span> http://en.wikipedia.org/wiki/Behavior-driven_development <br>
<span id="3foot">[[#1body|1.]]</span> http://www.ryangreenhall.com/articles/bdd-by-example.html <br>
<span id="4foot">[[#1body|1.]]</span> http://behaviour-driven.org/ <br>

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-08T00:09:46Z

Rgschaef: /* Examples */

=JBehave=

==Behavior Driven Development==
===Overview===
Behavior driven design (BDD) exists as an extension to Test Driven Development(TDD). Overall, BDD can be thought of as a specialized form of TDD that utilizes specialized tools (such as JBehave) to accomplish similar tasks with more emphasis on the accessibility of the program tests as opposed to the rigid, structured format of conventional acceptance tests.
===Comparison to Test Driven Development===
The language used for test cases immediately distinguishes BDD from TDD. Also, in BDD, the test cases emcompass both the specification for the program as well as the actual test case. <br>

==Background==
JBehave is a Java-based framework that aims to function as a fully fledged development paradigm, utilizing communication and automation while using behavior based language in its descriptors. JBehave is the first ever created Behavior Driven Design platform, completed by Dan North.

==Concepts==
===Three Core Principles===

<ol start="1">
<li>Business and Technology should refer to the same system in the same way - ItsAllBehaviour
<li>Any system should have an identified, verifiable value to the business - WheresTheBusinessValue
<li>Up-front analysis, design and planning all have a diminishing return - EnoughIsEnough
</ol>

===Stories===
A story is fundamentally defined as an "automatically executable increment of business functionality." We can think of this as a single component of functionality. Stories are further comprised of scenarios, which are defined as concrete examples of the behavior of the system. In other words, a specific instance of an implementation of a story. Scenarios are further broken down into steps, which are single statements that detail (step by step, if you will) exactly how a scenario will play out.

===Keywords===
BDD relies on the use of a small vocabulary to minimize miscommunication and to ensure that everyone involved (business, developers, testers, analysts and managers) are not only on the same page but using the same words.

Given, When, and Then are keywords utilized when writing JBehave scenarios. A scenario can have any number of steps and a story can contain many scenarios.

Given details the premises of the test, When details the exact incident, and Then details the expected outcome. To re-emphasize, the english readability is a novelty of BDD concepts.

Example of general story format:
<pre>Narrative:
In order to communicate effectively to the business some functionality
As a development team
I want to use Behaviour-Driven Development

Scenario: A scenario is a collection of executable steps of different type

Given step represents a precondition to an event
When step represents the occurrence of the event
Then step represents the outcome of the event

Scenario: Another scenario exploring different combination of events

Given a precondition
When a negative event occurs
Then a the outcome should be captured
</pre>

==Five Step Overview==

==Integrating with Eclipse==

Using the Eclipse Installer:
<ol start="1">
<li>Help > Install New Software...<br>

<li>Add the new site location http://jbehave.org/reference/eclipse/updates/
[[File:step2eclipse.png]]<br><br>
<li>Select JBehave Eclipse feature and follow standard Eclipse installation procedure
[[File:step3eclipse.png]]
</ol>

== Examples ==
<pre>
Given a 5 by 5 game
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
..X..
.....
When I toggle the cell at (3, 1)
Then the grid should look like
.....
.....
.....
..X..
..X..
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
.....
..X..
</pre>
This exhibits the three principles of good BDD;

== References ==
<span id="1foot">[[#1body|1.]]</span> http://jbehave.org/ <br>
<span id="2foot">[[#1body|1.]]</span> http://en.wikipedia.org/wiki/Behavior-driven_development <br>
<span id="3foot">[[#1body|1.]]</span> http://www.ryangreenhall.com/articles/bdd-by-example.html <br>
<span id="4foot">[[#1body|1.]]</span> http://behaviour-driven.org/ <br>

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-08T00:09:17Z

Rgschaef: /* Examples */

=JBehave=

==Behavior Driven Development==
===Overview===
Behavior driven design (BDD) exists as an extension to Test Driven Development(TDD). Overall, BDD can be thought of as a specialized form of TDD that utilizes specialized tools (such as JBehave) to accomplish similar tasks with more emphasis on the accessibility of the program tests as opposed to the rigid, structured format of conventional acceptance tests.
===Comparison to Test Driven Development===
The language used for test cases immediately distinguishes BDD from TDD. Also, in BDD, the test cases emcompass both the specification for the program as well as the actual test case. <br>

==Background==
JBehave is a Java-based framework that aims to function as a fully fledged development paradigm, utilizing communication and automation while using behavior based language in its descriptors. JBehave is the first ever created Behavior Driven Design platform, completed by Dan North.

==Concepts==
===Three Core Principles===

<ol start="1">
<li>Business and Technology should refer to the same system in the same way - ItsAllBehaviour
<li>Any system should have an identified, verifiable value to the business - WheresTheBusinessValue
<li>Up-front analysis, design and planning all have a diminishing return - EnoughIsEnough
</ol>

===Stories===
A story is fundamentally defined as an "automatically executable increment of business functionality." We can think of this as a single component of functionality. Stories are further comprised of scenarios, which are defined as concrete examples of the behavior of the system. In other words, a specific instance of an implementation of a story. Scenarios are further broken down into steps, which are single statements that detail (step by step, if you will) exactly how a scenario will play out.

===Keywords===
BDD relies on the use of a small vocabulary to minimize miscommunication and to ensure that everyone involved (business, developers, testers, analysts and managers) are not only on the same page but using the same words.

Given, When, and Then are keywords utilized when writing JBehave scenarios. A scenario can have any number of steps and a story can contain many scenarios.

Given details the premises of the test, When details the exact incident, and Then details the expected outcome. To re-emphasize, the english readability is a novelty of BDD concepts.

Example of general story format:
<pre>Narrative:
In order to communicate effectively to the business some functionality
As a development team
I want to use Behaviour-Driven Development

Scenario: A scenario is a collection of executable steps of different type

Given step represents a precondition to an event
When step represents the occurrence of the event
Then step represents the outcome of the event

Scenario: Another scenario exploring different combination of events

Given a precondition
When a negative event occurs
Then a the outcome should be captured
</pre>

==Five Step Overview==

==Integrating with Eclipse==

Using the Eclipse Installer:
<ol start="1">
<li>Help > Install New Software...<br>

<li>Add the new site location http://jbehave.org/reference/eclipse/updates/
[[File:step2eclipse.png]]<br><br>
<li>Select JBehave Eclipse feature and follow standard Eclipse installation procedure
[[File:step3eclipse.png]]
</ol>

== Examples ==
<pre>
Given a 5 by 5 game
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
..X..
.....
When I toggle the cell at (3, 1)
Then the grid should look like
.....
.....
.....
..X..
..X..
When I toggle the cell at (3, 2)
Then the grid should look like
.....
.....
.....
.....
..X..
</pre>

== References ==
<span id="1foot">[[#1body|1.]]</span> http://jbehave.org/ <br>
<span id="2foot">[[#1body|1.]]</span> http://en.wikipedia.org/wiki/Behavior-driven_development <br>
<span id="3foot">[[#1body|1.]]</span> http://www.ryangreenhall.com/articles/bdd-by-example.html <br>
<span id="4foot">[[#1body|1.]]</span> http://behaviour-driven.org/ <br>

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-08T00:08:18Z

Rgschaef: /* Stories */

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-08T00:07:58Z

Rgschaef: /* Three Core Principles */

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-08T00:07:39Z

Rgschaef: /* JBehave */

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-08T00:07:00Z

Rgschaef: /* JBehave */

=JBehave=
JBehave is the first ever created Behavior Driven Design platform, completed by Dan North.

==Behavior Driven Development==
===Overview===
Behavior driven design (BDD) exists as an extension to Test Driven Development(TDD). Overall, BDD can be thought of as a specialized form of TDD that utilizes specialized tools (such as JBehave) to accomplish similar tasks with more emphasis on the accessibility of the program tests as opposed to the rigid, structured format of conventional acceptance tests.
===Comparison to Test Driven Development===
The language used for test cases immediately distinguishes BDD from TDD. Also, in BDD, the test cases emcompass both the specification for the program as well as the actual test case. <br>

==Background==
JBehave is a Java-based framework that aims to function as a fully fledged development paradigm, utilizing communication and automation while using behavior based language in its descriptors.

==Concepts==
===Three Core Principles===

<ol start="1"
<li>Business and Technology should refer to the same system in the same way - ItsAllBehaviour
<li>Any system should have an identified, verifiable value to the business - WheresTheBusinessValue
<li>Up-front analysis, design and planning all have a diminishing return - EnoughIsEnough
</ol>

===Stories===
A story is fundamentally defined as an "automatically executable increment of business functionality." We can think of this as a single component of functionality. Stories are further comprised of scenarios, which are defined as concrete examples of the behavior of the system. In other words, a specific instance of an implementation of a story. Scenarios are further broken down into steps, which are single statements that detail (step by step, if you will) exactly how a scenario will play out.

===Keywords===
BDD relies on the use of a small vocabulary to minimize miscommunication and to ensure that everyone involved (business, developers, testers, analysts and managers) are not only on the same page but using the same words.

Given, When, and Then are keywords utilized when writing JBehave scenarios. A scenario can have any number of steps and a story can contain many scenarios.

Given details the premises of the test, When details the exact incident, and Then details the expected outcome. To re-emphasize, the english readability is a novelty of BDD concepts.

Example of general story format:
<pre>Narrative:
In order to communicate effectively to the business some functionality
As a development team
I want to use Behaviour-Driven Development

Scenario: A scenario is a collection of executable steps of different type

Given step represents a precondition to an event
When step represents the occurrence of the event
Then step represents the outcome of the event

Scenario: Another scenario exploring different combination of events

Given a precondition
When a negative event occurs
Then a the outcome should be captured
</pre>

==Five Step Overview==

==Integrating with Eclipse==

Using the Eclipse Installer:
<ol start="1">
<li>Help > Install New Software...<br>

<li>Add the new site location http://jbehave.org/reference/eclipse/updates/
[[File:step2eclipse.png]]<br><br>
<li>Select JBehave Eclipse feature and follow standard Eclipse installation procedure
[[File:step3eclipse.png]]
</ol>

== Examples ==

== References ==
<span id="1foot">[[#1body|1.]]</span> http://jbehave.org/ <br>
<span id="2foot">[[#1body|1.]]</span> http://en.wikipedia.org/wiki/Behavior-driven_development <br>
<span id="3foot">[[#1body|1.]]</span> http://www.ryangreenhall.com/articles/bdd-by-example.html <br>
<span id="4foot">[[#1body|1.]]</span> http://behaviour-driven.org/ <br>

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-07T23:59:55Z

Rgschaef: /* Integrating with Eclipse */

File:Step3eclipse.png

2014-10-07T23:59:26Z

Rgschaef:

File:Step2eclipse.png

2014-10-07T23:58:33Z

Rgschaef:

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-07T23:58:16Z

Rgschaef: /* Integrating with Eclipse */

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-07T23:57:59Z

Rgschaef: /* Integrating with Eclipse */

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-07T23:56:22Z

Rgschaef: /* Integrating with Eclipse */

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-07T23:55:11Z

Rgschaef: /* Integrating with Eclipse */

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-07T23:54:43Z

Rgschaef: /* Integrating with Eclipse */

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-07T23:51:09Z

Rgschaef: /* Integrating with Eclipse */

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-07T23:43:01Z

Rgschaef: /* Concepts */

CSC/ECE 517 Fall 2014/ch1a 25 rs

2014-10-07T23:38:14Z

Rgschaef: Created page with "=JBehave= ==Behavior Driven Development== ===Overview=== Behavior driven design (BDD) exists as an extension to Test Driven Development(TDD). Overall, BDD can be thought of as ..."

CSC/ECE 517 Fall 2014

2014-10-07T23:11:00Z

Rgschaef:

*[[CSC/ECE_517_Fall_2014/sample_page]]
*[[CSC/ECE_517_Fall_2014/ch1a 22 as]]
*[[CSC/ECE 517 Fall 2014/ch1a 19 mx]]
*[[CSC/ECE 517 Fall 2014/ch1a 3 zq]]
*[[CSC/ECE 517 Fall 2014/ch1a 4 lf]]
*[[CSC/ECE 517 Fall 2014/ch1a 4 wl]]
*[[CSC/ECE 517 Fall 2014/ch1a a7 ch]]
*[[CSC/ECE 517 Fall 2014/ch1a 25 rs]]
*[[CSC/ECE 517 Fall 2014/ch1a 25 jf]]
*[[CSC/ECE 517 Fall 2014/ch1a 8 os]]
*[[CSC/ECE 517 Fall 2014/ch1a 8 sn]]
*[[CSC/ECE 517 Fall 2014/ch1a 15 gs]]
*[[CSC/ECE 517 Fall 2014/ch1a 10 hu]]
*[[CSC/ECE 517 Fall 2014/ch1a 20 kv]]
*[[CSC/ECE 517 Fall 2014/ch1a 21 as]]
*[[CSC/ECE 517 Fall 2014/ch1a 24 sa]]
*[[CSC/ECE 517 Fall 2014/ch1a 26 sn]]
*[[CSC/ECE 517 Fall 2014/ch1a 6 rl]]
*[[CSC/ECE 517 Fall 2014/ch1a 2 ss]]
*[[CSC/ECE 517 Fall 2014/ch1a 16 av]]
*[[CSC/ECE 517 Fall 2014/ch1a 1 rm]]
*[[CSC/ECE 517 Fall 2014/ch1a 1 sj]]
*[[CSC/ECE 517 Fall 2014/ch1a 23 ss]]
*[[CSC/ECE 517 Fall 2014/ch1a 20 rn]]
*[[CSC/ECE 517 Fall 2014/ch1a 22 sp]]
*[[CSC/ECE 517 Fall 2014/ch1a 26 gn]]

*[[CSC/ECE 517 Fall 2014/ch1a 13 va]]
*[[CSC/ECE 517 Fall 2014/ch1a 9 aa]]
*[[CSC/ECE 517 Fall 2014/ch1a 9 kn]]
*[[CSC/ECE 517 Fall 2014/ch1a 11 ap]]
*[[CSC/ECE 517 Fall 2014/ch1a 25 ks]]
*[[CSC/ECE 517 Fall 2014/ch1a 7 kz]]
*[[CSC/ECE_517_Fall_2014/ch1a_6_bn]]
*[[CSC/ECE_517_Fall_2014/ch1a 10 zz]]
*[[CSC/ECE_517_Fall_2014/ch1a 16 va]]
*[[CSC/ECE_517_Fall_2014/ch1a F1415 rv]]
*[[CSC/ECE_517_Fall_2014/ch1a_3_cp]]
*[[CSC/ECE 517 Fall 2014/ch1b 26 sa]]
*[[CSC/ECE_517_Fall_2014/ch1b_28_cg]]
*[[CSC/ECE_517_Fall_2014/ch1b 29 ry]]
*[[CSC/ECE_517_Fall_2014/ch1b 30 cs]]
*[[CSC/ECE_517_Fall_2014/ch1b_33_jy]]
*[[CSC/ECE_517_Fall_2014/ch1b_27_js]]

CSC/ECE 517 Fall 2014/ch1a a7 ch

2014-09-30T02:46:48Z

Rgschaef: /* Comparison to other Frameworks */

= Web2py Framework =
Web2py is a free open source full-stack framework for rapid development of fast, scalable, secure and portable database-driven web-based applications written in Python.<sup><span id="1body">[[#1foot|[1]]]</span></sup>
== Background ==
Web2py was originally introduced as a teaching tool to used to demonstrate ease of use and deployment. It was modeled after [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and [http://en.wikipedia.org/wiki/Django_(web_framework) Django], and as such focuses on rapid development and adheres to the [http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller Model View Controller] architecture pattern.

Here are some of the features of Web2py<sup><span id="3body">[[#3foot|[2]]]</span></sup><sup><span id="4body">[[#4foot|[3]]]</span></sup>:
* Web2py runs on Windows, Mac, Unix/Linux, Google App Engine, Amazon EC2, and almost any web hosting via Python 2.5/2.6/2.7/pypy, or Java with Jython.
* Accessible anywhere, without any installation required
* Open source licensed under the [http://www.gnu.org/licenses/lgpl.html GNU LGPL v3.0 License]
* Support for mutiple databases including: SQLite, PostgreSQL, MySQL, MSSQL, FireBird, Oracle, IBM DB2, Informix, Ingres, and Google App Engine
* Equipped with a Data Abstraction Layer that removes the requirement of knowing how to write SQL by doing it for you in real-time
* Role-based authorization of resources
* Error logging and ticketing system
* An web-based administrative interface for ease of interaction

== Examples ==
There are [http://web2py.com/poweredby several websites] currently powered by Web2py, including a [http://pymines.appspot.com/ website] hosting the ever-popular game [http://en.wikipedia.org/wiki/Minesweeper_(video_game) Minesweeper].

As previously mentioned, Web2py doesn't require that you install anything, you may access and demo the capabilities online through their [http://www.web2py.com/demo_admin/default/site demo administrative interface]. At the time of this article's writing, the save demo is not fully-functional.

You may download and run web2py by following the instructions on [http://www.web2py.com/init/default/download this page].

===Code Examples===

A complete list web2py-provided examples can be found [http://www.web2py.com/init/default/examples here].

====Hello World====
Creating a web2py application can be as simple as writing a few lines in a single controller file (default.py):

<pre>
def index(): return "Hello World"
</pre>

====File Upload<sup><span id="3body">[[#3foot|[3]]]</span></sup>====
In the Model:
<pre>
db=DAL('sqlite://storage.db')
db.define_table('image',
Field('name', notnull=True),
Field('file','upload'))
</pre>

In the Controller:
<pre>
def index():
form = SQLFORM(db.image).process()
if form.accepted:
response.flash = 'image uploaded'
return locals()
</pre>

In the View:
<pre>
{{extend 'layout.html'}}
<h1>Image upload form</h1>
{{=form}}
</pre>

[[File:ImageUpload.PNG]]

====Forms<sup><span id="5body">[[#5foot|[5]]]</span></sup>====

In the Model:
<pre>
db = DAL('sqlite://webform.sqlite')
db.define_table('register',
Field('first_name', requires=IS_NOT_EMPTY()),
Field('last_name', requires=IS_NOT_EMPTY()),
Field('email', requires=IS_NOT_EMPTY()))
</pre>

In the Controller:
<pre>
def display_your_form():
form = SQLFORM(db.register)
return dict(form=form)
</pre>

In the View:
<pre>
<center>
<br /><br /><br />
<h1>Web Form</h1>
<br />
<h2>Inputs:</h2>
{{=form}}
<h2>Submitted variables:</h2>
{{=BEAUTIFY(request.vars)}}
</center>
</pre>

[[File:Webform.png]]

==Architecture==

Web2py follows a Model-View-Controller (MVC) architecture.

* '''Model''' - The data
* '''View''' - Presents the data in a user-friendly way.
* '''Controller''' - Acts as the glue between the model and view and handles the logic for displaying the data.

[[File:MVC-Process.png]]

This diagram shows an example of how web2py handles requests and renders the request to the browser:

[[File:Architecture.PNG]]

==Comparison to other Frameworks==
Since web2py was inspiried by Rails and Django, it draws ideas from each.

The creators of web2py borrowed the Ruby on Rails approach of convention over configuration and Django's approach of generating forms from database tables and including a large amount of validators out of the box.

Overall, web2py can be viewed as less encompassing than Ruby on Rails and is directed towards a less advanced audience. It does not implement Active-Record or dependency injection and relies on a simplified database scheme. Because it relies on Python, it is a compiled language with more basic versioning, encryption, and custom queries and covers a less broad coding style (no imperative programming or aspect-oriented programming).

Django and web2py share a lot of common ground and many common features. They both are pre-compiled, Python-based, and have nearly identical database schemes (object-relational and document-relational). Django uses a unique template system called (wait for it) the Django Template System, supports a wide variety of version control, and has greater support for cloud hosting solutions.

===<u>Controllers</u>===

====Ruby on Rails====
<pre>
class MyTestController < ApplicationController
def index
render_text “Hello World”
end
end
</pre>

====Django====

Django requires the user to specify all of his/her imports in the code:

<pre>
from django.http import HttpResponse
def index(request):
return HttpResponse("Hello World”)
</pre>

====Web2py====
<pre>
def index():
return "Hello World"
</pre>

===<u>Models</u>===

====Ruby on Rails====
<pre>
class Article < ActiveRecord::Migration
def self.up
create_table :articles do |t|
t.column :name, :string
t.column :description, :text
end
end
end
</pre>

====Django====
<pre>
class Article(models.Model):
name = models.StringField()
description = models.TextField()
</pre>

====Web2py====
<pre>
Article=db.define_table(‘Article’,
SQLField(‘email’,’string’),
SQLField(‘description’,’text’)
</pre>

===<u>Views</u>===

====Ruby on Rails====
<pre>
<table>
<% @recipes.each do |recipe| %>
<tr>
<td><%= recipe.name %></td>
</tr>
<% end %>
</table>
</pre>

====Django====
<pre>
<table>
{% for recipe in recipes %}
<tr>
<td>{{recipe.name}}</td>
</tr>
{% endfor %}
</table>
</pre>

====Web2py====
<pre>
<table>
{{for recipe in recipes:}}>
<tr>
<td>{{=recipe.name}}</td>
</tr>
{{pass}}
</table>
</pre>

== Distinguishing Features ==

=== Model/Controller Execution ===
In web2py, the Model and Controller code is not modual; rather, they are executed in a global environment with each individual HTTP request. This is different from most web development frameworks and presents a unique set of advantages and disadvantages.

Advantages:
*Simplifies development - no need to import
*Provides a clean reset of objects with every HTTP request - no need to worry about object states, overriding requests, conflicting HTTP, etc.
*Multiple applications can exist within the same instance without conflicting with one another

Disadvantages:
*Models and Controllers are not class based - code sometimes must be frequently repeated
*Inability to inherit
*Non-modular; the developer must be mindful of the order of execution

=== Online IDE ===
web2py is fully supported by an online IDE. This covers the full development spectrum, including debugging, testing, maintenance, databases, internationalization, etc. This makes it simple to begin developement without setting up any kind of environment or even installing an IDE.

== Getting Started in web2py ==
Hosting your own Debian/Ubuntu installation:
<ol start="1">
<li>Install the 'unzip' package if you do not have it
<pre>sudo apt-get update
sudo apt-get install unzip</pre>
<li>Download the framework from the website and unzip it
<pre>wget http://www.web2py.com/examples/static/web2py_src.zip
unzip web2py_src.zip
cd web2py</pre>
<li>Run the web interface
<pre>python web2py.py</pre>
<li>If all goes well, you should be see your local web2py server running in the terminal window. Ctrl + C will terminate it.
[[File:web2pyserver.png]]
<li>To create SSL certificates for remote access, generate an RSA key and then output the file with the following commands:
<pre>openssl genrsa -out server.key 2048
openssl req -new -key server.key -out server.csr
openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt</pre>
[[File:rsa.png]]
<li>Now you can enable remote access by passing in a few parameters when you start up your server:
<pre>python web2py.py -a 'admin_password' -c server.crt -k server.key -i 0.0.0.0 -p 8000</pre>
<li>You can access your IDE through most browsers at https://your_ip:8000 (e.g. 127.0.0.1:8000 if accessing locally)
[[File:ide.png]]

</ol>

== References ==
<span id="1foot">[[#1body|1.]]</span> http://www.web2py.com/init/default/index <br>
<span id="2foot">[[#2body|2.]]</span> http://en.wikipedia.org/wiki/Web2py <br>
<span id="3foot">[[#3body|3.]]</span> http://www.web2py.com/init/default/what <br>
<span id="4foot">[[#4body|4.]]</span> http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2013/oss_SocialMediaFeeds <br>
<span id="5foot">[[#5body|5.]]</span> http://mherman.org/blog/2012/12/01/crash-course-in-web2py-part-2-web-forms/#.VBT9d_ldVuJ <br>
<span id="6foot">[[#6body|6.]]</span> http://www.web2py.com/examples/static/web2py_vs_others.pdf/ Web2py vs other frameworks <br>
<span id="7foot">[[#7body|7.]]</span> https://www.digitalocean.com/community/tutorials/how-to-use-the-web2py-framework-to-quickly-build-your-python-app<br>

File:Ide.png

2014-09-18T19:07:56Z

Rgschaef:

CSC/ECE 517 Fall 2014/ch1a a7 ch

2014-09-18T19:07:40Z

Rgschaef: /* Getting Started in web2py */

= Web2py Framework =
Web2py is a free open source full-stack framework for rapid development of fast, scalable, secure and portable database-driven web-based applications written in Python.<sup><span id="1body">[[#1foot|[1]]]</span></sup>
== Background ==
Web2py was originally introduced as a teaching tool to used to demonstrate ease of use and deployment. It was modeled after [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and [http://en.wikipedia.org/wiki/Django_(web_framework) Django], and as such focuses on rapid development and adheres to the [http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller Model View Controller] architecture pattern.

Here are some of the features of Web2py<sup><span id="3body">[[#3foot|[2]]]</span></sup><sup><span id="4body">[[#4foot|[3]]]</span></sup>:
* Web2py runs on Windows, Mac, Unix/Linux, Google App Engine, Amazon EC2, and almost any web hosting via Python 2.5/2.6/2.7/pypy, or Java with Jython.
* Accessible anywhere, without any installation required
* Open source licensed under the [http://www.gnu.org/licenses/lgpl.html GNU LGPL v3.0 License]
* Support for mutiple databases including: SQLite, PostgreSQL, MySQL, MSSQL, FireBird, Oracle, IBM DB2, Informix, Ingres, and Google App Engine
* Equipped with a Data Abstraction Layer that removes the requirement of knowing how to write SQL by doing it for you in real-time
* Role-based authorization of resources
* Error logging and ticketing system
* An web-based administrative interface for ease of interaction

== Examples ==
There are [http://web2py.com/poweredby several websites] currently powered by Web2py, including a [http://pymines.appspot.com/ website] hosting the ever-popular game [http://en.wikipedia.org/wiki/Minesweeper_(video_game) Minesweeper].

As previously mentioned, Web2py doesn't require that you install anything, you may access and demo the capabilities online through their [http://www.web2py.com/demo_admin/default/site demo administrative interface]. At the time of this article's writing, the save demo is not fully-functional.

You may download and run web2py by following the instructions on [http://www.web2py.com/init/default/download this page].

===Code Examples===

A complete list web2py-provided examples can be found [http://www.web2py.com/init/default/examples here].

====Hello World====
Creating a web2py application can be as simple as writing a few lines in a single controller file (default.py):

<pre>
def index(): return "Hello World"
</pre>

====File Upload<sup><span id="3body">[[#3foot|[3]]]</span></sup>====
In the Model:
<pre>
db=DAL('sqlite://storage.db')
db.define_table('image',
Field('name', notnull=True),
Field('file','upload'))
</pre>

In the Controller:
<pre>
def index():
form = SQLFORM(db.image).process()
if form.accepted:
response.flash = 'image uploaded'
return locals()
</pre>

In the View:
<pre>
{{extend 'layout.html'}}
<h1>Image upload form</h1>
{{=form}}
</pre>

[[File:ImageUpload.PNG]]

====Forms<sup><span id="5body">[[#5foot|[5]]]</span></sup>====

In the Model:
<pre>
db = DAL('sqlite://webform.sqlite')
db.define_table('register',
Field('first_name', requires=IS_NOT_EMPTY()),
Field('last_name', requires=IS_NOT_EMPTY()),
Field('email', requires=IS_NOT_EMPTY()))
</pre>

In the Controller:
<pre>
def display_your_form():
form = SQLFORM(db.register)
return dict(form=form)
</pre>

In the View:
<pre>
<center>
<br /><br /><br />
<h1>Web Form</h1>
<br />
<h2>Inputs:</h2>
{{=form}}
<h2>Submitted variables:</h2>
{{=BEAUTIFY(request.vars)}}
</center>
</pre>

[[File:Webform.png]]

==Architecture==

Web2py follows a Model-View-Controller (MVC) architecture.

* '''Model''' - The data
* '''View''' - Presents the data in a user-friendly way.
* '''Controller''' - Acts as the glue between the model and view and handles the logic for displaying the data.

[[File:MVC-Process.png]]

This diagram shows an example of how web2py handles requests and renders the request to the browser:

[[File:Architecture.PNG]]

==Comparison to other Frameworks==
Since web2py was inspiried by Rails and Django, it draws ideas from each.

The creators of web2py borrowed the Ruby on Rails approach of convention over configuration and Django's approach of generating forms from database tables and including a large amount of validators out of the box.
===<u>Controllers</u>===

====Ruby on Rails====
<pre>
class MyTestController < ApplicationController
def index
render_text “Hello World”
end
end
</pre>

====Django====

Django requires the user to specify all of his/her imports in the code:

<pre>
from django.http import HttpResponse
def index(request):
return HttpResponse("Hello World”)
</pre>

====Web2py====
<pre>
def index():
return "Hello World"
</pre>

===<u>Models</u>===

====Ruby on Rails====
<pre>
class Article < ActiveRecord::Migration
def self.up
create_table :articles do |t|
t.column :name, :string
t.column :description, :text
end
end
end
</pre>

====Django====
<pre>
class Article(models.Model):
name = models.StringField()
description = models.TextField()
</pre>

====Web2py====
<pre>
Article=db.define_table(‘Article’,
SQLField(‘email’,’string’),
SQLField(‘description’,’text’)
</pre>

===<u>Views</u>===

====Ruby on Rails====
<pre>
<table>
<% @recipes.each do |recipe| %>
<tr>
<td><%= recipe.name %></td>
</tr>
<% end %>
</table>
</pre>

====Django====
<pre>
<table>
{% for recipe in recipes %}
<tr>
<td>{{recipe.name}}</td>
</tr>
{% endfor %}
</table>
</pre>

====Web2py====
<pre>
<table>
{{for recipe in recipes:}}>
<tr>
<td>{{=recipe.name}}</td>
</tr>
{{pass}}
</table>
</pre>

== Distinguishing Features ==

=== Model/Controller Execution ===
In web2py, the Model and Controller code is not modual; rather, they are executed in a global environment with each individual HTTP request. This is different from most web development frameworks and presents a unique set of advantages and disadvantages.

Advantages:
*Simplifies development - no need to import
*Provides a clean reset of objects with every HTTP request - no need to worry about object states, overriding requests, conflicting HTTP, etc.
*Multiple applications can exist within the same instance without conflicting with one another

Disadvantages:
*Models and Controllers are not class based - code sometimes must be frequently repeated
*Inability to inherit
*Non-modular; the developer must be mindful of the order of execution

=== Online IDE ===
web2py is fully supported by an online IDE. This covers the full development spectrum, including debugging, testing, maintenance, databases, internationalization, etc. This makes it simple to begin developement without setting up any kind of environment or even installing an IDE.

== Getting Started in web2py ==
Hosting your own Debian/Ubuntu installation:
<ol start="1">
<li>Install the 'unzip' package if you do not have it
<pre>sudo apt-get update
sudo apt-get install unzip</pre>
<li>Download the framework from the website and unzip it
<pre>wget http://www.web2py.com/examples/static/web2py_src.zip
unzip web2py_src.zip
cd web2py</pre>
<li>Run the web interface
<pre>python web2py.py</pre>
<li>If all goes well, you should be see your local web2py server running in the terminal window. Ctrl + C will terminate it.
[[File:web2pyserver.png]]
<li>To create SSL certificates for remote access, generate an RSA key and then output the file with the following commands:
<pre>openssl genrsa -out server.key 2048
openssl req -new -key server.key -out server.csr
openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt</pre>
[[File:rsa.png]]
<li>Now you can enable remote access by passing in a few parameters when you start up your server:
<pre>python web2py.py -a 'admin_password' -c server.crt -k server.key -i 0.0.0.0 -p 8000</pre>
<li>You can access your IDE through most browsers at https://your_ip:8000 (e.g. 127.0.0.1:8000 if accessing locally)
[[File:ide.png]]

</ol>

== References ==
<span id="1foot">[[#1body|1.]]</span> http://www.web2py.com/init/default/index <br>
<span id="2foot">[[#2body|2.]]</span> http://en.wikipedia.org/wiki/Web2py <br>
<span id="3foot">[[#3body|3.]]</span> http://www.web2py.com/init/default/what <br>
<span id="4foot">[[#4body|4.]]</span> http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2013/oss_SocialMediaFeeds <br>
<span id="5foot">[[#5body|5.]]</span> http://mherman.org/blog/2012/12/01/crash-course-in-web2py-part-2-web-forms/#.VBT9d_ldVuJ <br>
<span id="6foot">[[#6body|6.]]</span> http://www.web2py.com/examples/static/web2py_vs_others.pdf/ Web2py vs other frameworks <br>
<span id="7foot">[[#7body|7.]]</span> https://www.digitalocean.com/community/tutorials/how-to-use-the-web2py-framework-to-quickly-build-your-python-app<br>

CSC/ECE 517 Fall 2014/ch1a a7 ch

2014-09-18T19:04:27Z

Rgschaef: /* Getting Started in web2py */

= Web2py Framework =
Web2py is a free open source full-stack framework for rapid development of fast, scalable, secure and portable database-driven web-based applications written in Python.<sup><span id="1body">[[#1foot|[1]]]</span></sup>
== Background ==
Web2py was originally introduced as a teaching tool to used to demonstrate ease of use and deployment. It was modeled after [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and [http://en.wikipedia.org/wiki/Django_(web_framework) Django], and as such focuses on rapid development and adheres to the [http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller Model View Controller] architecture pattern.

Here are some of the features of Web2py<sup><span id="3body">[[#3foot|[2]]]</span></sup><sup><span id="4body">[[#4foot|[3]]]</span></sup>:
* Web2py runs on Windows, Mac, Unix/Linux, Google App Engine, Amazon EC2, and almost any web hosting via Python 2.5/2.6/2.7/pypy, or Java with Jython.
* Accessible anywhere, without any installation required
* Open source licensed under the [http://www.gnu.org/licenses/lgpl.html GNU LGPL v3.0 License]
* Support for mutiple databases including: SQLite, PostgreSQL, MySQL, MSSQL, FireBird, Oracle, IBM DB2, Informix, Ingres, and Google App Engine
* Equipped with a Data Abstraction Layer that removes the requirement of knowing how to write SQL by doing it for you in real-time
* Role-based authorization of resources
* Error logging and ticketing system
* An web-based administrative interface for ease of interaction

== Examples ==
There are [http://web2py.com/poweredby several websites] currently powered by Web2py, including a [http://pymines.appspot.com/ website] hosting the ever-popular game [http://en.wikipedia.org/wiki/Minesweeper_(video_game) Minesweeper].

As previously mentioned, Web2py doesn't require that you install anything, you may access and demo the capabilities online through their [http://www.web2py.com/demo_admin/default/site demo administrative interface]. At the time of this article's writing, the save demo is not fully-functional.

You may download and run web2py by following the instructions on [http://www.web2py.com/init/default/download this page].

===Code Examples===

A complete list web2py-provided examples can be found [http://www.web2py.com/init/default/examples here].

====Hello World====
Creating a web2py application can be as simple as writing a few lines in a single controller file (default.py):

<pre>
def index(): return "Hello World"
</pre>

====File Upload<sup><span id="3body">[[#3foot|[3]]]</span></sup>====
In the Model:
<pre>
db=DAL('sqlite://storage.db')
db.define_table('image',
Field('name', notnull=True),
Field('file','upload'))
</pre>

In the Controller:
<pre>
def index():
form = SQLFORM(db.image).process()
if form.accepted:
response.flash = 'image uploaded'
return locals()
</pre>

In the View:
<pre>
{{extend 'layout.html'}}
<h1>Image upload form</h1>
{{=form}}
</pre>

[[File:ImageUpload.PNG]]

====Forms<sup><span id="5body">[[#5foot|[5]]]</span></sup>====

In the Model:
<pre>
db = DAL('sqlite://webform.sqlite')
db.define_table('register',
Field('first_name', requires=IS_NOT_EMPTY()),
Field('last_name', requires=IS_NOT_EMPTY()),
Field('email', requires=IS_NOT_EMPTY()))
</pre>

In the Controller:
<pre>
def display_your_form():
form = SQLFORM(db.register)
return dict(form=form)
</pre>

In the View:
<pre>
<center>
<br /><br /><br />
<h1>Web Form</h1>
<br />
<h2>Inputs:</h2>
{{=form}}
<h2>Submitted variables:</h2>
{{=BEAUTIFY(request.vars)}}
</center>
</pre>

[[File:Webform.png]]

==Architecture==

Web2py follows a Model-View-Controller (MVC) architecture.

* '''Model''' - The data
* '''View''' - Presents the data in a user-friendly way.
* '''Controller''' - Acts as the glue between the model and view and handles the logic for displaying the data.

[[File:MVC-Process.png]]

This diagram shows an example of how web2py handles requests and renders the request to the browser:

[[File:Architecture.PNG]]

==Comparison to other Frameworks==
Since web2py was inspiried by Rails and Django, it draws ideas from each.

The creators of web2py borrowed the Ruby on Rails approach of convention over configuration and Django's approach of generating forms from database tables and including a large amount of validators out of the box.
===<u>Controllers</u>===

====Ruby on Rails====
<pre>
class MyTestController < ApplicationController
def index
render_text “Hello World”
end
end
</pre>

====Django====

Django requires the user to specify all of his/her imports in the code:

<pre>
from django.http import HttpResponse
def index(request):
return HttpResponse("Hello World”)
</pre>

====Web2py====
<pre>
def index():
return "Hello World"
</pre>

===<u>Models</u>===

====Ruby on Rails====
<pre>
class Article < ActiveRecord::Migration
def self.up
create_table :articles do |t|
t.column :name, :string
t.column :description, :text
end
end
end
</pre>

====Django====
<pre>
class Article(models.Model):
name = models.StringField()
description = models.TextField()
</pre>

====Web2py====
<pre>
Article=db.define_table(‘Article’,
SQLField(‘email’,’string’),
SQLField(‘description’,’text’)
</pre>

===<u>Views</u>===

====Ruby on Rails====
<pre>
<table>
<% @recipes.each do |recipe| %>
<tr>
<td><%= recipe.name %></td>
</tr>
<% end %>
</table>
</pre>

====Django====
<pre>
<table>
{% for recipe in recipes %}
<tr>
<td>{{recipe.name}}</td>
</tr>
{% endfor %}
</table>
</pre>

====Web2py====
<pre>
<table>
{{for recipe in recipes:}}>
<tr>
<td>{{=recipe.name}}</td>
</tr>
{{pass}}
</table>
</pre>

== Distinguishing Features ==

=== Model/Controller Execution ===
In web2py, the Model and Controller code is not modual; rather, they are executed in a global environment with each individual HTTP request. This is different from most web development frameworks and presents a unique set of advantages and disadvantages.

Advantages:
*Simplifies development - no need to import
*Provides a clean reset of objects with every HTTP request - no need to worry about object states, overriding requests, conflicting HTTP, etc.
*Multiple applications can exist within the same instance without conflicting with one another

Disadvantages:
*Models and Controllers are not class based - code sometimes must be frequently repeated
*Inability to inherit
*Non-modular; the developer must be mindful of the order of execution

=== Online IDE ===
web2py is fully supported by an online IDE. This covers the full development spectrum, including debugging, testing, maintenance, databases, internationalization, etc. This makes it simple to begin developement without setting up any kind of environment or even installing an IDE.

== Getting Started in web2py ==
Hosting your own Debian/Ubuntu installation:
<ol start="1">
<li>Install the 'unzip' package if you do not have it
<pre>sudo apt-get update
sudo apt-get install unzip</pre>
<li>Download the framework from the website and unzip it
<pre>wget http://www.web2py.com/examples/static/web2py_src.zip
unzip web2py_src.zip
cd web2py</pre>
<li>Run the web interface
<pre>python web2py.py</pre>
<li>If all goes well, you should be see your local web2py server running in the terminal window. Ctrl + C will terminate it.
[[File:web2pyserver.png]]
<li>To create SSL certificates for remote access, generate an RSA key and then output the file with the following commands:
<pre>openssl genrsa -out server.key 2048
openssl req -new -key server.key -out server.csr
openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt</pre>
[[File:rsa.png]]
<li>Now you can enable remote access by passing in a few parameters when you start up your server:
<pre>python web2py.py -a 'admin_password' -c server.crt -k server.key -i 0.0.0.0 -p 8000</pre>
</ol>

== References ==
<span id="1foot">[[#1body|1.]]</span> http://www.web2py.com/init/default/index <br>
<span id="2foot">[[#2body|2.]]</span> http://en.wikipedia.org/wiki/Web2py <br>
<span id="3foot">[[#3body|3.]]</span> http://www.web2py.com/init/default/what <br>
<span id="4foot">[[#4body|4.]]</span> http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2013/oss_SocialMediaFeeds <br>
<span id="5foot">[[#5body|5.]]</span> http://mherman.org/blog/2012/12/01/crash-course-in-web2py-part-2-web-forms/#.VBT9d_ldVuJ <br>
<span id="6foot">[[#6body|6.]]</span> http://www.web2py.com/examples/static/web2py_vs_others.pdf/ Web2py vs other frameworks <br>
<span id="7foot">[[#7body|7.]]</span> https://www.digitalocean.com/community/tutorials/how-to-use-the-web2py-framework-to-quickly-build-your-python-app<br>

File:Rsa.png

2014-09-18T19:04:12Z

Rgschaef:

File:Web2pyserver.png

2014-09-18T00:00:01Z

Rgschaef:

CSC/ECE 517 Fall 2014/ch1a a7 ch

2014-09-17T23:59:51Z

Rgschaef: /* Getting Started in web2py */

= Web2py Framework =
Web2py is a free open source full-stack framework for rapid development of fast, scalable, secure and portable database-driven web-based applications written in Python.<sup><span id="1body">[[#1foot|[1]]]</span></sup>
== Background ==
Web2py was originally introduced as a teaching tool to used to demonstrate ease of use and deployment. It was modeled after [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and [http://en.wikipedia.org/wiki/Django_(web_framework) Django], and as such focuses on rapid development and adheres to the [http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller Model View Controller] architecture pattern.

Here are some of the features of Web2py<sup><span id="3body">[[#3foot|[2]]]</span></sup><sup><span id="4body">[[#4foot|[3]]]</span></sup>:
* Web2py runs on Windows, Mac, Unix/Linux, Google App Engine, Amazon EC2, and almost any web hosting via Python 2.5/2.6/2.7/pypy, or Java with Jython.
* Accessible anywhere, without any installation required
* Open source licensed under the [http://www.gnu.org/licenses/lgpl.html GNU LGPL v3.0 License]
* Support for mutiple databases including: SQLite, PostgreSQL, MySQL, MSSQL, FireBird, Oracle, IBM DB2, Informix, Ingres, and Google App Engine
* Equipped with a Data Abstraction Layer that removes the requirement of knowing how to write SQL by doing it for you in real-time
* Role-based authorization of resources
* Error logging and ticketing system
* An web-based administrative interface for ease of interaction

== Examples ==
There are [http://web2py.com/poweredby several websites] currently powered by Web2py, including a [http://pymines.appspot.com/ website] hosting the ever-popular game [http://en.wikipedia.org/wiki/Minesweeper_(video_game) Minesweeper].

As previously mentioned, Web2py doesn't require that you install anything, you may access and demo the capabilities online through their [http://www.web2py.com/demo_admin/default/site demo administrative interface]. At the time of this article's writing, the save demo is not fully-functional.

You may download and run web2py by following the instructions on [http://www.web2py.com/init/default/download this page].

===Code Examples===

A complete list web2py-provided examples can be found [http://www.web2py.com/init/default/examples here].

====Hello World====
Creating a web2py application can be as simple as writing a few lines in a single controller file (default.py):

<pre>
def index(): return "Hello World"
</pre>

====File Upload<sup><span id="3body">[[#3foot|[3]]]</span></sup>====
In the Model:
<pre>
db=DAL('sqlite://storage.db')
db.define_table('image',
Field('name', notnull=True),
Field('file','upload'))
</pre>

In the Controller:
<pre>
def index():
form = SQLFORM(db.image).process()
if form.accepted:
response.flash = 'image uploaded'
return locals()
</pre>

In the View:
<pre>
{{extend 'layout.html'}}
<h1>Image upload form</h1>
{{=form}}
</pre>

[[File:ImageUpload.PNG]]

====Forms<sup><span id="5body">[[#5foot|[5]]]</span></sup>====

In the Model:
<pre>
db = DAL('sqlite://webform.sqlite')
db.define_table('register',
Field('first_name', requires=IS_NOT_EMPTY()),
Field('last_name', requires=IS_NOT_EMPTY()),
Field('email', requires=IS_NOT_EMPTY()))
</pre>

In the Controller:
<pre>
def display_your_form():
form = SQLFORM(db.register)
return dict(form=form)
</pre>

In the View:
<pre>
<center>
<br /><br /><br />
<h1>Web Form</h1>
<br />
<h2>Inputs:</h2>
{{=form}}
<h2>Submitted variables:</h2>
{{=BEAUTIFY(request.vars)}}
</center>
</pre>

[[File:Webform.png]]

==Architecture==

Web2py follows a Model-View-Controller (MVC) architecture.

* '''Model''' - The data
* '''View''' - Presents the data in a user-friendly way.
* '''Controller''' - Acts as the glue between the model and view and handles the logic for displaying the data.

[[File:MVC-Process.png]]

This diagram shows an example of how web2py handles requests and renders the request to the browser:

[[File:Architecture.PNG]]

==Comparison to other Frameworks==
Since web2py was inspiried by Rails and Django, it draws ideas from each.

The creators of web2py borrowed the Ruby on Rails approach of convention over configuration and Django's approach of generating forms from database tables and including a large amount of validators out of the box.
===<u>Controllers</u>===

====Ruby on Rails====
<pre>
class MyTestController < ApplicationController
def index
render_text “Hello World”
end
end
</pre>

====Django====

Django requires the user to specify all of his/her imports in the code:

<pre>
from django.http import HttpResponse
def index(request):
return HttpResponse("Hello World”)
</pre>

====Web2py====
<pre>
def index():
return "Hello World"
</pre>

===<u>Models</u>===

====Ruby on Rails====
<pre>
class Article < ActiveRecord::Migration
def self.up
create_table :articles do |t|
t.column :name, :string
t.column :description, :text
end
end
end
</pre>

====Django====
<pre>
class Article(models.Model):
name = models.StringField()
description = models.TextField()
</pre>

====Web2py====
<pre>
Article=db.define_table(‘Article’,
SQLField(‘email’,’string’),
SQLField(‘description’,’text’)
</pre>

===<u>Views</u>===

====Ruby on Rails====
<pre>
<table>
<% @recipes.each do |recipe| %>
<tr>
<td><%= recipe.name %></td>
</tr>
<% end %>
</table>
</pre>

====Django====
<pre>
<table>
{% for recipe in recipes %}
<tr>
<td>{{recipe.name}}</td>
</tr>
{% endfor %}
</table>
</pre>

====Web2py====
<pre>
<table>
{{for recipe in recipes:}}>
<tr>
<td>{{=recipe.name}}</td>
</tr>
{{pass}}
</table>
</pre>

== Distinguishing Features ==

=== Model/Controller Execution ===
In web2py, the Model and Controller code is not modual; rather, they are executed in a global environment with each individual HTTP request. This is different from most web development frameworks and presents a unique set of advantages and disadvantages.

Advantages:
*Simplifies development - no need to import
*Provides a clean reset of objects with every HTTP request - no need to worry about object states, overriding requests, conflicting HTTP, etc.
*Multiple applications can exist within the same instance without conflicting with one another

Disadvantages:
*Models and Controllers are not class based - code sometimes must be frequently repeated
*Inability to inherit
*Non-modular; the developer must be mindful of the order of execution

=== Online IDE ===
web2py is fully supported by an online IDE. This covers the full development spectrum, including debugging, testing, maintenance, databases, internationalization, etc. This makes it simple to begin developement without setting up any kind of environment or even installing an IDE.

== Getting Started in web2py ==
Debian/Ubuntu installation:
<ol start="1">
<li>Install the 'unzip' package if you do not have it
<pre>sudo apt-get update
sudo apt-get install unzip</pre>
<li>Download the framework from the website and unzip it
<pre>wget http://www.web2py.com/examples/static/web2py_src.zip
unzip web2py_src.zip
cd web2py</pre>
<li>Run the web interface
<pre>python web2py.py</pre>
<li>If all goes well, you should be see your local web2py server running in the terminal window. Ctrl + C will terminate it.
[[File:web2pyserver.png]]
</ol>

== References ==
<span id="1foot">[[#1body|1.]]</span> http://www.web2py.com/init/default/index <br>
<span id="2foot">[[#2body|2.]]</span> http://en.wikipedia.org/wiki/Web2py <br>
<span id="3foot">[[#3body|3.]]</span> http://www.web2py.com/init/default/what <br>
<span id="4foot">[[#4body|4.]]</span> http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2013/oss_SocialMediaFeeds <br>
<span id="5foot">[[#5body|5.]]</span> http://mherman.org/blog/2012/12/01/crash-course-in-web2py-part-2-web-forms/#.VBT9d_ldVuJ <br>
<span id="6foot">[[#6body|6.]]</span> http://www.web2py.com/examples/static/web2py_vs_others.pdf/ Web2py vs other frameworks <br>
<span id="7foot">[[#7body|7.]]</span> https://www.digitalocean.com/community/tutorials/how-to-use-the-web2py-framework-to-quickly-build-your-python-app<br>

CSC/ECE 517 Fall 2014/ch1a a7 ch

2014-09-17T23:59:02Z

Rgschaef: /* Getting Started in web2py */

= Web2py Framework =
Web2py is a free open source full-stack framework for rapid development of fast, scalable, secure and portable database-driven web-based applications written in Python.<sup><span id="1body">[[#1foot|[1]]]</span></sup>
== Background ==
Web2py was originally introduced as a teaching tool to used to demonstrate ease of use and deployment. It was modeled after [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and [http://en.wikipedia.org/wiki/Django_(web_framework) Django], and as such focuses on rapid development and adheres to the [http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller Model View Controller] architecture pattern.

Here are some of the features of Web2py<sup><span id="3body">[[#3foot|[2]]]</span></sup><sup><span id="4body">[[#4foot|[3]]]</span></sup>:
* Web2py runs on Windows, Mac, Unix/Linux, Google App Engine, Amazon EC2, and almost any web hosting via Python 2.5/2.6/2.7/pypy, or Java with Jython.
* Accessible anywhere, without any installation required
* Open source licensed under the [http://www.gnu.org/licenses/lgpl.html GNU LGPL v3.0 License]
* Support for mutiple databases including: SQLite, PostgreSQL, MySQL, MSSQL, FireBird, Oracle, IBM DB2, Informix, Ingres, and Google App Engine
* Equipped with a Data Abstraction Layer that removes the requirement of knowing how to write SQL by doing it for you in real-time
* Role-based authorization of resources
* Error logging and ticketing system
* An web-based administrative interface for ease of interaction

== Examples ==
There are [http://web2py.com/poweredby several websites] currently powered by Web2py, including a [http://pymines.appspot.com/ website] hosting the ever-popular game [http://en.wikipedia.org/wiki/Minesweeper_(video_game) Minesweeper].

As previously mentioned, Web2py doesn't require that you install anything, you may access and demo the capabilities online through their [http://www.web2py.com/demo_admin/default/site demo administrative interface]. At the time of this article's writing, the save demo is not fully-functional.

You may download and run web2py by following the instructions on [http://www.web2py.com/init/default/download this page].

===Code Examples===

A complete list web2py-provided examples can be found [http://www.web2py.com/init/default/examples here].

====Hello World====
Creating a web2py application can be as simple as writing a few lines in a single controller file (default.py):

<pre>
def index(): return "Hello World"
</pre>

====File Upload<sup><span id="3body">[[#3foot|[3]]]</span></sup>====
In the Model:
<pre>
db=DAL('sqlite://storage.db')
db.define_table('image',
Field('name', notnull=True),
Field('file','upload'))
</pre>

In the Controller:
<pre>
def index():
form = SQLFORM(db.image).process()
if form.accepted:
response.flash = 'image uploaded'
return locals()
</pre>

In the View:
<pre>
{{extend 'layout.html'}}
<h1>Image upload form</h1>
{{=form}}
</pre>

[[File:ImageUpload.PNG]]

====Forms<sup><span id="5body">[[#5foot|[5]]]</span></sup>====

In the Model:
<pre>
db = DAL('sqlite://webform.sqlite')
db.define_table('register',
Field('first_name', requires=IS_NOT_EMPTY()),
Field('last_name', requires=IS_NOT_EMPTY()),
Field('email', requires=IS_NOT_EMPTY()))
</pre>

In the Controller:
<pre>
def display_your_form():
form = SQLFORM(db.register)
return dict(form=form)
</pre>

In the View:
<pre>
<center>
<br /><br /><br />
<h1>Web Form</h1>
<br />
<h2>Inputs:</h2>
{{=form}}
<h2>Submitted variables:</h2>
{{=BEAUTIFY(request.vars)}}
</center>
</pre>

[[File:Webform.png]]

==Architecture==

Web2py follows a Model-View-Controller (MVC) architecture.

* '''Model''' - The data
* '''View''' - Presents the data in a user-friendly way.
* '''Controller''' - Acts as the glue between the model and view and handles the logic for displaying the data.

[[File:MVC-Process.png]]

This diagram shows an example of how web2py handles requests and renders the request to the browser:

[[File:Architecture.PNG]]

==Comparison to other Frameworks==
Since web2py was inspiried by Rails and Django, it draws ideas from each.

The creators of web2py borrowed the Ruby on Rails approach of convention over configuration and Django's approach of generating forms from database tables and including a large amount of validators out of the box.
===<u>Controllers</u>===

====Ruby on Rails====
<pre>
class MyTestController < ApplicationController
def index
render_text “Hello World”
end
end
</pre>

====Django====

Django requires the user to specify all of his/her imports in the code:

<pre>
from django.http import HttpResponse
def index(request):
return HttpResponse("Hello World”)
</pre>

====Web2py====
<pre>
def index():
return "Hello World"
</pre>

===<u>Models</u>===

====Ruby on Rails====
<pre>
class Article < ActiveRecord::Migration
def self.up
create_table :articles do |t|
t.column :name, :string
t.column :description, :text
end
end
end
</pre>

====Django====
<pre>
class Article(models.Model):
name = models.StringField()
description = models.TextField()
</pre>

====Web2py====
<pre>
Article=db.define_table(‘Article’,
SQLField(‘email’,’string’),
SQLField(‘description’,’text’)
</pre>

===<u>Views</u>===

====Ruby on Rails====
<pre>
<table>
<% @recipes.each do |recipe| %>
<tr>
<td><%= recipe.name %></td>
</tr>
<% end %>
</table>
</pre>

====Django====
<pre>
<table>
{% for recipe in recipes %}
<tr>
<td>{{recipe.name}}</td>
</tr>
{% endfor %}
</table>
</pre>

====Web2py====
<pre>
<table>
{{for recipe in recipes:}}>
<tr>
<td>{{=recipe.name}}</td>
</tr>
{{pass}}
</table>
</pre>

== Distinguishing Features ==

=== Model/Controller Execution ===
In web2py, the Model and Controller code is not modual; rather, they are executed in a global environment with each individual HTTP request. This is different from most web development frameworks and presents a unique set of advantages and disadvantages.

Advantages:
*Simplifies development - no need to import
*Provides a clean reset of objects with every HTTP request - no need to worry about object states, overriding requests, conflicting HTTP, etc.
*Multiple applications can exist within the same instance without conflicting with one another

Disadvantages:
*Models and Controllers are not class based - code sometimes must be frequently repeated
*Inability to inherit
*Non-modular; the developer must be mindful of the order of execution

=== Online IDE ===
web2py is fully supported by an online IDE. This covers the full development spectrum, including debugging, testing, maintenance, databases, internationalization, etc. This makes it simple to begin developement without setting up any kind of environment or even installing an IDE.

== Getting Started in web2py ==
Debian/Ubuntu installation:
<ol start="1">
<li>Install the 'unzip' package if you do not have it
<pre>sudo apt-get update
sudo apt-get install unzip</pre>
<li>Download the framework from the website and unzip it
<pre>wget http://www.web2py.com/examples/static/web2py_src.zip
unzip web2py_src.zip
cd web2py</pre>
<li>Run the web interface
<pre>python web2py.py</pre>
<li>If all goes well, you should be see your local web2py server running in the terminal window. Ctrl + C will terminate it.
[[File:web2pyserver.jpg]]
</ol>

== References ==
<span id="1foot">[[#1body|1.]]</span> http://www.web2py.com/init/default/index <br>
<span id="2foot">[[#2body|2.]]</span> http://en.wikipedia.org/wiki/Web2py <br>
<span id="3foot">[[#3body|3.]]</span> http://www.web2py.com/init/default/what <br>
<span id="4foot">[[#4body|4.]]</span> http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2013/oss_SocialMediaFeeds <br>
<span id="5foot">[[#5body|5.]]</span> http://mherman.org/blog/2012/12/01/crash-course-in-web2py-part-2-web-forms/#.VBT9d_ldVuJ <br>
<span id="6foot">[[#6body|6.]]</span> http://www.web2py.com/examples/static/web2py_vs_others.pdf/ Web2py vs other frameworks <br>
<span id="7foot">[[#7body|7.]]</span> https://www.digitalocean.com/community/tutorials/how-to-use-the-web2py-framework-to-quickly-build-your-python-app<br>

CSC/ECE 517 Fall 2014/ch1a a7 ch

2014-09-17T23:54:30Z

Rgschaef: /* References */

= Web2py Framework =
Web2py is a free open source full-stack framework for rapid development of fast, scalable, secure and portable database-driven web-based applications written in Python.<sup><span id="1body">[[#1foot|[1]]]</span></sup>
== Background ==
Web2py was originally introduced as a teaching tool to used to demonstrate ease of use and deployment. It was modeled after [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and [http://en.wikipedia.org/wiki/Django_(web_framework) Django], and as such focuses on rapid development and adheres to the [http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller Model View Controller] architecture pattern.

Here are some of the features of Web2py<sup><span id="3body">[[#3foot|[2]]]</span></sup><sup><span id="4body">[[#4foot|[3]]]</span></sup>:
* Web2py runs on Windows, Mac, Unix/Linux, Google App Engine, Amazon EC2, and almost any web hosting via Python 2.5/2.6/2.7/pypy, or Java with Jython.
* Accessible anywhere, without any installation required
* Open source licensed under the [http://www.gnu.org/licenses/lgpl.html GNU LGPL v3.0 License]
* Support for mutiple databases including: SQLite, PostgreSQL, MySQL, MSSQL, FireBird, Oracle, IBM DB2, Informix, Ingres, and Google App Engine
* Equipped with a Data Abstraction Layer that removes the requirement of knowing how to write SQL by doing it for you in real-time
* Role-based authorization of resources
* Error logging and ticketing system
* An web-based administrative interface for ease of interaction

== Examples ==
There are [http://web2py.com/poweredby several websites] currently powered by Web2py, including a [http://pymines.appspot.com/ website] hosting the ever-popular game [http://en.wikipedia.org/wiki/Minesweeper_(video_game) Minesweeper].

As previously mentioned, Web2py doesn't require that you install anything, you may access and demo the capabilities online through their [http://www.web2py.com/demo_admin/default/site demo administrative interface]. At the time of this article's writing, the save demo is not fully-functional.

You may download and run web2py by following the instructions on [http://www.web2py.com/init/default/download this page].

===Code Examples===

A complete list web2py-provided examples can be found [http://www.web2py.com/init/default/examples here].

====Hello World====
Creating a web2py application can be as simple as writing a few lines in a single controller file (default.py):

<pre>
def index(): return "Hello World"
</pre>

====File Upload<sup><span id="3body">[[#3foot|[3]]]</span></sup>====
In the Model:
<pre>
db=DAL('sqlite://storage.db')
db.define_table('image',
Field('name', notnull=True),
Field('file','upload'))
</pre>

In the Controller:
<pre>
def index():
form = SQLFORM(db.image).process()
if form.accepted:
response.flash = 'image uploaded'
return locals()
</pre>

In the View:
<pre>
{{extend 'layout.html'}}
<h1>Image upload form</h1>
{{=form}}
</pre>

[[File:ImageUpload.PNG]]

====Forms<sup><span id="5body">[[#5foot|[5]]]</span></sup>====

In the Model:
<pre>
db = DAL('sqlite://webform.sqlite')
db.define_table('register',
Field('first_name', requires=IS_NOT_EMPTY()),
Field('last_name', requires=IS_NOT_EMPTY()),
Field('email', requires=IS_NOT_EMPTY()))
</pre>

In the Controller:
<pre>
def display_your_form():
form = SQLFORM(db.register)
return dict(form=form)
</pre>

In the View:
<pre>
<center>
<br /><br /><br />
<h1>Web Form</h1>
<br />
<h2>Inputs:</h2>
{{=form}}
<h2>Submitted variables:</h2>
{{=BEAUTIFY(request.vars)}}
</center>
</pre>

[[File:Webform.png]]

==Architecture==

Web2py follows a Model-View-Controller (MVC) architecture.

* '''Model''' - The data
* '''View''' - Presents the data in a user-friendly way.
* '''Controller''' - Acts as the glue between the model and view and handles the logic for displaying the data.

[[File:MVC-Process.png]]

This diagram shows an example of how web2py handles requests and renders the request to the browser:

[[File:Architecture.PNG]]

==Comparison to other Frameworks==
Since web2py was inspiried by Rails and Django, it draws ideas from each.

The creators of web2py borrowed the Ruby on Rails approach of convention over configuration and Django's approach of generating forms from database tables and including a large amount of validators out of the box.
===<u>Controllers</u>===

====Ruby on Rails====
<pre>
class MyTestController < ApplicationController
def index
render_text “Hello World”
end
end
</pre>

====Django====

Django requires the user to specify all of his/her imports in the code:

<pre>
from django.http import HttpResponse
def index(request):
return HttpResponse("Hello World”)
</pre>

====Web2py====
<pre>
def index():
return "Hello World"
</pre>

===<u>Models</u>===

====Ruby on Rails====
<pre>
class Article < ActiveRecord::Migration
def self.up
create_table :articles do |t|
t.column :name, :string
t.column :description, :text
end
end
end
</pre>

====Django====
<pre>
class Article(models.Model):
name = models.StringField()
description = models.TextField()
</pre>

====Web2py====
<pre>
Article=db.define_table(‘Article’,
SQLField(‘email’,’string’),
SQLField(‘description’,’text’)
</pre>

===<u>Views</u>===

====Ruby on Rails====
<pre>
<table>
<% @recipes.each do |recipe| %>
<tr>
<td><%= recipe.name %></td>
</tr>
<% end %>
</table>
</pre>

====Django====
<pre>
<table>
{% for recipe in recipes %}
<tr>
<td>{{recipe.name}}</td>
</tr>
{% endfor %}
</table>
</pre>

====Web2py====
<pre>
<table>
{{for recipe in recipes:}}>
<tr>
<td>{{=recipe.name}}</td>
</tr>
{{pass}}
</table>
</pre>

== Distinguishing Features ==

=== Model/Controller Execution ===
In web2py, the Model and Controller code is not modual; rather, they are executed in a global environment with each individual HTTP request. This is different from most web development frameworks and presents a unique set of advantages and disadvantages.

Advantages:
*Simplifies development - no need to import
*Provides a clean reset of objects with every HTTP request - no need to worry about object states, overriding requests, conflicting HTTP, etc.
*Multiple applications can exist within the same instance without conflicting with one another

Disadvantages:
*Models and Controllers are not class based - code sometimes must be frequently repeated
*Inability to inherit
*Non-modular; the developer must be mindful of the order of execution

=== Online IDE ===
web2py is fully supported by an online IDE. This covers the full development spectrum, including debugging, testing, maintenance, databases, internationalization, etc. This makes it simple to begin developement without setting up any kind of environment or even installing an IDE.

== Getting Started in web2py ==
Debian/Ubuntu installation:
<ol start="1">
<li>Install the 'unzip' package if you do not have it
<pre>sudo apt-get update
sudo apt-get install unzip</pre>
<li>Download the framework from the website and unzip it
<pre>wget http://www.web2py.com/examples/static/web2py_src.zip
unzip web2py_src.zip
cd web2py</pre>
<li>
<li>
</ol>

== References ==
<span id="1foot">[[#1body|1.]]</span> http://www.web2py.com/init/default/index <br>
<span id="2foot">[[#2body|2.]]</span> http://en.wikipedia.org/wiki/Web2py <br>
<span id="3foot">[[#3body|3.]]</span> http://www.web2py.com/init/default/what <br>
<span id="4foot">[[#4body|4.]]</span> http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2013/oss_SocialMediaFeeds <br>
<span id="5foot">[[#5body|5.]]</span> http://mherman.org/blog/2012/12/01/crash-course-in-web2py-part-2-web-forms/#.VBT9d_ldVuJ <br>
<span id="6foot">[[#6body|6.]]</span> http://www.web2py.com/examples/static/web2py_vs_others.pdf/ Web2py vs other frameworks <br>
<span id="7foot">[[#7body|7.]]</span> https://www.digitalocean.com/community/tutorials/how-to-use-the-web2py-framework-to-quickly-build-your-python-app<br>

CSC/ECE 517 Fall 2014/ch1a a7 ch

2014-09-17T23:53:33Z

Rgschaef: /* Getting Started in web2py */

= Web2py Framework =
Web2py is a free open source full-stack framework for rapid development of fast, scalable, secure and portable database-driven web-based applications written in Python.<sup><span id="1body">[[#1foot|[1]]]</span></sup>
== Background ==
Web2py was originally introduced as a teaching tool to used to demonstrate ease of use and deployment. It was modeled after [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and [http://en.wikipedia.org/wiki/Django_(web_framework) Django], and as such focuses on rapid development and adheres to the [http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller Model View Controller] architecture pattern.

Here are some of the features of Web2py<sup><span id="3body">[[#3foot|[2]]]</span></sup><sup><span id="4body">[[#4foot|[3]]]</span></sup>:
* Web2py runs on Windows, Mac, Unix/Linux, Google App Engine, Amazon EC2, and almost any web hosting via Python 2.5/2.6/2.7/pypy, or Java with Jython.
* Accessible anywhere, without any installation required
* Open source licensed under the [http://www.gnu.org/licenses/lgpl.html GNU LGPL v3.0 License]
* Support for mutiple databases including: SQLite, PostgreSQL, MySQL, MSSQL, FireBird, Oracle, IBM DB2, Informix, Ingres, and Google App Engine
* Equipped with a Data Abstraction Layer that removes the requirement of knowing how to write SQL by doing it for you in real-time
* Role-based authorization of resources
* Error logging and ticketing system
* An web-based administrative interface for ease of interaction

== Examples ==
There are [http://web2py.com/poweredby several websites] currently powered by Web2py, including a [http://pymines.appspot.com/ website] hosting the ever-popular game [http://en.wikipedia.org/wiki/Minesweeper_(video_game) Minesweeper].

As previously mentioned, Web2py doesn't require that you install anything, you may access and demo the capabilities online through their [http://www.web2py.com/demo_admin/default/site demo administrative interface]. At the time of this article's writing, the save demo is not fully-functional.

You may download and run web2py by following the instructions on [http://www.web2py.com/init/default/download this page].

===Code Examples===

A complete list web2py-provided examples can be found [http://www.web2py.com/init/default/examples here].

====Hello World====
Creating a web2py application can be as simple as writing a few lines in a single controller file (default.py):

<pre>
def index(): return "Hello World"
</pre>

====File Upload<sup><span id="3body">[[#3foot|[3]]]</span></sup>====
In the Model:
<pre>
db=DAL('sqlite://storage.db')
db.define_table('image',
Field('name', notnull=True),
Field('file','upload'))
</pre>

In the Controller:
<pre>
def index():
form = SQLFORM(db.image).process()
if form.accepted:
response.flash = 'image uploaded'
return locals()
</pre>

In the View:
<pre>
{{extend 'layout.html'}}
<h1>Image upload form</h1>
{{=form}}
</pre>

[[File:ImageUpload.PNG]]

====Forms<sup><span id="5body">[[#5foot|[5]]]</span></sup>====

In the Model:
<pre>
db = DAL('sqlite://webform.sqlite')
db.define_table('register',
Field('first_name', requires=IS_NOT_EMPTY()),
Field('last_name', requires=IS_NOT_EMPTY()),
Field('email', requires=IS_NOT_EMPTY()))
</pre>

In the Controller:
<pre>
def display_your_form():
form = SQLFORM(db.register)
return dict(form=form)
</pre>

In the View:
<pre>
<center>
<br /><br /><br />
<h1>Web Form</h1>
<br />
<h2>Inputs:</h2>
{{=form}}
<h2>Submitted variables:</h2>
{{=BEAUTIFY(request.vars)}}
</center>
</pre>

[[File:Webform.png]]

==Architecture==

Web2py follows a Model-View-Controller (MVC) architecture.

* '''Model''' - The data
* '''View''' - Presents the data in a user-friendly way.
* '''Controller''' - Acts as the glue between the model and view and handles the logic for displaying the data.

[[File:MVC-Process.png]]

This diagram shows an example of how web2py handles requests and renders the request to the browser:

[[File:Architecture.PNG]]

==Comparison to other Frameworks==
Since web2py was inspiried by Rails and Django, it draws ideas from each.

The creators of web2py borrowed the Ruby on Rails approach of convention over configuration and Django's approach of generating forms from database tables and including a large amount of validators out of the box.
===<u>Controllers</u>===

====Ruby on Rails====
<pre>
class MyTestController < ApplicationController
def index
render_text “Hello World”
end
end
</pre>

====Django====

Django requires the user to specify all of his/her imports in the code:

<pre>
from django.http import HttpResponse
def index(request):
return HttpResponse("Hello World”)
</pre>

====Web2py====
<pre>
def index():
return "Hello World"
</pre>

===<u>Models</u>===

====Ruby on Rails====
<pre>
class Article < ActiveRecord::Migration
def self.up
create_table :articles do |t|
t.column :name, :string
t.column :description, :text
end
end
end
</pre>

====Django====
<pre>
class Article(models.Model):
name = models.StringField()
description = models.TextField()
</pre>

====Web2py====
<pre>
Article=db.define_table(‘Article’,
SQLField(‘email’,’string’),
SQLField(‘description’,’text’)
</pre>

===<u>Views</u>===

====Ruby on Rails====
<pre>
<table>
<% @recipes.each do |recipe| %>
<tr>
<td><%= recipe.name %></td>
</tr>
<% end %>
</table>
</pre>

====Django====
<pre>
<table>
{% for recipe in recipes %}
<tr>
<td>{{recipe.name}}</td>
</tr>
{% endfor %}
</table>
</pre>

====Web2py====
<pre>
<table>
{{for recipe in recipes:}}>
<tr>
<td>{{=recipe.name}}</td>
</tr>
{{pass}}
</table>
</pre>

== Distinguishing Features ==

=== Model/Controller Execution ===
In web2py, the Model and Controller code is not modual; rather, they are executed in a global environment with each individual HTTP request. This is different from most web development frameworks and presents a unique set of advantages and disadvantages.

Advantages:
*Simplifies development - no need to import
*Provides a clean reset of objects with every HTTP request - no need to worry about object states, overriding requests, conflicting HTTP, etc.
*Multiple applications can exist within the same instance without conflicting with one another

Disadvantages:
*Models and Controllers are not class based - code sometimes must be frequently repeated
*Inability to inherit
*Non-modular; the developer must be mindful of the order of execution

=== Online IDE ===
web2py is fully supported by an online IDE. This covers the full development spectrum, including debugging, testing, maintenance, databases, internationalization, etc. This makes it simple to begin developement without setting up any kind of environment or even installing an IDE.

== Getting Started in web2py ==
Debian/Ubuntu installation:
<ol start="1">
<li>Install the 'unzip' package if you do not have it
<pre>sudo apt-get update
sudo apt-get install unzip</pre>
<li>Download the framework from the website and unzip it
<pre>wget http://www.web2py.com/examples/static/web2py_src.zip
unzip web2py_src.zip
cd web2py</pre>
<li>
<li>
</ol>

== References ==
<span id="1foot">[[#1body|1.]]</span> http://www.web2py.com/init/default/index <br>
<span id="2foot">[[#2body|2.]]</span> http://en.wikipedia.org/wiki/Web2py <br>
<span id="3foot">[[#3body|3.]]</span> http://www.web2py.com/init/default/what <br>
<span id="4foot">[[#4body|4.]]</span> http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2013/oss_SocialMediaFeeds <br>
<span id="5foot">[[#5body|5.]]</span> http://mherman.org/blog/2012/12/01/crash-course-in-web2py-part-2-web-forms/#.VBT9d_ldVuJ <br>
<span id="6foot">[[#6body|6.]]</span> http://www.web2py.com/examples/static/web2py_vs_others.pdf/ Web2py vs other frameworks <br>

CSC/ECE 517 Fall 2014/ch1a a7 ch

2014-09-17T23:51:12Z

Rgschaef:

= Web2py Framework =
Web2py is a free open source full-stack framework for rapid development of fast, scalable, secure and portable database-driven web-based applications written in Python.<sup><span id="1body">[[#1foot|[1]]]</span></sup>
== Background ==
Web2py was originally introduced as a teaching tool to used to demonstrate ease of use and deployment. It was modeled after [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and [http://en.wikipedia.org/wiki/Django_(web_framework) Django], and as such focuses on rapid development and adheres to the [http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller Model View Controller] architecture pattern.

Here are some of the features of Web2py<sup><span id="3body">[[#3foot|[2]]]</span></sup><sup><span id="4body">[[#4foot|[3]]]</span></sup>:
* Web2py runs on Windows, Mac, Unix/Linux, Google App Engine, Amazon EC2, and almost any web hosting via Python 2.5/2.6/2.7/pypy, or Java with Jython.
* Accessible anywhere, without any installation required
* Open source licensed under the [http://www.gnu.org/licenses/lgpl.html GNU LGPL v3.0 License]
* Support for mutiple databases including: SQLite, PostgreSQL, MySQL, MSSQL, FireBird, Oracle, IBM DB2, Informix, Ingres, and Google App Engine
* Equipped with a Data Abstraction Layer that removes the requirement of knowing how to write SQL by doing it for you in real-time
* Role-based authorization of resources
* Error logging and ticketing system
* An web-based administrative interface for ease of interaction

== Examples ==
There are [http://web2py.com/poweredby several websites] currently powered by Web2py, including a [http://pymines.appspot.com/ website] hosting the ever-popular game [http://en.wikipedia.org/wiki/Minesweeper_(video_game) Minesweeper].

As previously mentioned, Web2py doesn't require that you install anything, you may access and demo the capabilities online through their [http://www.web2py.com/demo_admin/default/site demo administrative interface]. At the time of this article's writing, the save demo is not fully-functional.

You may download and run web2py by following the instructions on [http://www.web2py.com/init/default/download this page].

===Code Examples===

A complete list web2py-provided examples can be found [http://www.web2py.com/init/default/examples here].

====Hello World====
Creating a web2py application can be as simple as writing a few lines in a single controller file (default.py):

<pre>
def index(): return "Hello World"
</pre>

====File Upload<sup><span id="3body">[[#3foot|[3]]]</span></sup>====
In the Model:
<pre>
db=DAL('sqlite://storage.db')
db.define_table('image',
Field('name', notnull=True),
Field('file','upload'))
</pre>

In the Controller:
<pre>
def index():
form = SQLFORM(db.image).process()
if form.accepted:
response.flash = 'image uploaded'
return locals()
</pre>

In the View:
<pre>
{{extend 'layout.html'}}
<h1>Image upload form</h1>
{{=form}}
</pre>

[[File:ImageUpload.PNG]]

====Forms<sup><span id="5body">[[#5foot|[5]]]</span></sup>====

In the Model:
<pre>
db = DAL('sqlite://webform.sqlite')
db.define_table('register',
Field('first_name', requires=IS_NOT_EMPTY()),
Field('last_name', requires=IS_NOT_EMPTY()),
Field('email', requires=IS_NOT_EMPTY()))
</pre>

In the Controller:
<pre>
def display_your_form():
form = SQLFORM(db.register)
return dict(form=form)
</pre>

In the View:
<pre>
<center>
<br /><br /><br />
<h1>Web Form</h1>
<br />
<h2>Inputs:</h2>
{{=form}}
<h2>Submitted variables:</h2>
{{=BEAUTIFY(request.vars)}}
</center>
</pre>

[[File:Webform.png]]

==Architecture==

Web2py follows a Model-View-Controller (MVC) architecture.

* '''Model''' - The data
* '''View''' - Presents the data in a user-friendly way.
* '''Controller''' - Acts as the glue between the model and view and handles the logic for displaying the data.

[[File:MVC-Process.png]]

This diagram shows an example of how web2py handles requests and renders the request to the browser:

[[File:Architecture.PNG]]

==Comparison to other Frameworks==
Since web2py was inspiried by Rails and Django, it draws ideas from each.

The creators of web2py borrowed the Ruby on Rails approach of convention over configuration and Django's approach of generating forms from database tables and including a large amount of validators out of the box.
===<u>Controllers</u>===

====Ruby on Rails====
<pre>
class MyTestController < ApplicationController
def index
render_text “Hello World”
end
end
</pre>

====Django====

Django requires the user to specify all of his/her imports in the code:

<pre>
from django.http import HttpResponse
def index(request):
return HttpResponse("Hello World”)
</pre>

====Web2py====
<pre>
def index():
return "Hello World"
</pre>

===<u>Models</u>===

====Ruby on Rails====
<pre>
class Article < ActiveRecord::Migration
def self.up
create_table :articles do |t|
t.column :name, :string
t.column :description, :text
end
end
end
</pre>

====Django====
<pre>
class Article(models.Model):
name = models.StringField()
description = models.TextField()
</pre>

====Web2py====
<pre>
Article=db.define_table(‘Article’,
SQLField(‘email’,’string’),
SQLField(‘description’,’text’)
</pre>

===<u>Views</u>===

====Ruby on Rails====
<pre>
<table>
<% @recipes.each do |recipe| %>
<tr>
<td><%= recipe.name %></td>
</tr>
<% end %>
</table>
</pre>

====Django====
<pre>
<table>
{% for recipe in recipes %}
<tr>
<td>{{recipe.name}}</td>
</tr>
{% endfor %}
</table>
</pre>

====Web2py====
<pre>
<table>
{{for recipe in recipes:}}>
<tr>
<td>{{=recipe.name}}</td>
</tr>
{{pass}}
</table>
</pre>

== Distinguishing Features ==

=== Model/Controller Execution ===
In web2py, the Model and Controller code is not modual; rather, they are executed in a global environment with each individual HTTP request. This is different from most web development frameworks and presents a unique set of advantages and disadvantages.

Advantages:
*Simplifies development - no need to import
*Provides a clean reset of objects with every HTTP request - no need to worry about object states, overriding requests, conflicting HTTP, etc.
*Multiple applications can exist within the same instance without conflicting with one another

Disadvantages:
*Models and Controllers are not class based - code sometimes must be frequently repeated
*Inability to inherit
*Non-modular; the developer must be mindful of the order of execution

=== Online IDE ===
web2py is fully supported by an online IDE. This covers the full development spectrum, including debugging, testing, maintenance, databases, internationalization, etc. This makes it simple to begin developement without setting up any kind of environment or even installing an IDE.

== Getting Started in web2py ==
Debian/Ubuntu installation:
<ol start="1">
<li>Install the 'unzip' package if you do not have it
<pre>sudo apt-get update
sudo apt-get install unzip</pre>
<li>
</ol>

== References ==
<span id="1foot">[[#1body|1.]]</span> http://www.web2py.com/init/default/index <br>
<span id="2foot">[[#2body|2.]]</span> http://en.wikipedia.org/wiki/Web2py <br>
<span id="3foot">[[#3body|3.]]</span> http://www.web2py.com/init/default/what <br>
<span id="4foot">[[#4body|4.]]</span> http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2013/oss_SocialMediaFeeds <br>
<span id="5foot">[[#5body|5.]]</span> http://mherman.org/blog/2012/12/01/crash-course-in-web2py-part-2-web-forms/#.VBT9d_ldVuJ <br>
<span id="6foot">[[#6body|6.]]</span> http://www.web2py.com/examples/static/web2py_vs_others.pdf/ Web2py vs other frameworks <br>

CSC/ECE 517 Fall 2014/ch1a a7 ch

2014-09-17T23:46:08Z

Rgschaef: /* Distinguishing Features */

= Web2py Framework =
Web2py is a free open source full-stack framework for rapid development of fast, scalable, secure and portable database-driven web-based applications written in Python.<sup><span id="1body">[[#1foot|[1]]]</span></sup>
== Background ==
Web2py was originally introduced as a teaching tool to used to demonstrate ease of use and deployment. It was modeled after [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and [http://en.wikipedia.org/wiki/Django_(web_framework) Django], and as such focuses on rapid development and adheres to the [http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller Model View Controller] architecture pattern.

Here are some of the features of Web2py<sup><span id="3body">[[#3foot|[2]]]</span></sup><sup><span id="4body">[[#4foot|[3]]]</span></sup>:
* Web2py runs on Windows, Mac, Unix/Linux, Google App Engine, Amazon EC2, and almost any web hosting via Python 2.5/2.6/2.7/pypy, or Java with Jython.
* Accessible anywhere, without any installation required
* Open source licensed under the [http://www.gnu.org/licenses/lgpl.html GNU LGPL v3.0 License]
* Support for mutiple databases including: SQLite, PostgreSQL, MySQL, MSSQL, FireBird, Oracle, IBM DB2, Informix, Ingres, and Google App Engine
* Equipped with a Data Abstraction Layer that removes the requirement of knowing how to write SQL by doing it for you in real-time
* Role-based authorization of resources
* Error logging and ticketing system
* An web-based administrative interface for ease of interaction

== Examples ==
There are [http://web2py.com/poweredby several websites] currently powered by Web2py, including a [http://pymines.appspot.com/ website] hosting the ever-popular game [http://en.wikipedia.org/wiki/Minesweeper_(video_game) Minesweeper].

As previously mentioned, Web2py doesn't require that you install anything, you may access and demo the capabilities online through their [http://www.web2py.com/demo_admin/default/site demo administrative interface]. At the time of this article's writing, the save demo is not fully-functional.

You may download and run web2py by following the instructions on [http://www.web2py.com/init/default/download this page].

===Code Examples===

A complete list web2py-provided examples can be found [http://www.web2py.com/init/default/examples here].

====Hello World====
Creating a web2py application can be as simple as writing a few lines in a single controller file (default.py):

<pre>
def index(): return "Hello World"
</pre>

====File Upload<sup><span id="3body">[[#3foot|[3]]]</span></sup>====
In the Model:
<pre>
db=DAL('sqlite://storage.db')
db.define_table('image',
Field('name', notnull=True),
Field('file','upload'))
</pre>

In the Controller:
<pre>
def index():
form = SQLFORM(db.image).process()
if form.accepted:
response.flash = 'image uploaded'
return locals()
</pre>

In the View:
<pre>
{{extend 'layout.html'}}
<h1>Image upload form</h1>
{{=form}}
</pre>

[[File:ImageUpload.PNG]]

====Forms<sup><span id="5body">[[#5foot|[5]]]</span></sup>====

In the Model:
<pre>
db = DAL('sqlite://webform.sqlite')
db.define_table('register',
Field('first_name', requires=IS_NOT_EMPTY()),
Field('last_name', requires=IS_NOT_EMPTY()),
Field('email', requires=IS_NOT_EMPTY()))
</pre>

In the Controller:
<pre>
def display_your_form():
form = SQLFORM(db.register)
return dict(form=form)
</pre>

In the View:
<pre>
<center>
<br /><br /><br />
<h1>Web Form</h1>
<br />
<h2>Inputs:</h2>
{{=form}}
<h2>Submitted variables:</h2>
{{=BEAUTIFY(request.vars)}}
</center>
</pre>

[[File:Webform.png]]

==Architecture==

Web2py follows a Model-View-Controller (MVC) architecture.

* '''Model''' - The data
* '''View''' - Presents the data in a user-friendly way.
* '''Controller''' - Acts as the glue between the model and view and handles the logic for displaying the data.

[[File:MVC-Process.png]]

This diagram shows an example of how web2py handles requests and renders the request to the browser:

[[File:Architecture.PNG]]

==Comparison to other Frameworks==
Since web2py was inspiried by Rails and Django, it draws ideas from each.

The creators of web2py borrowed the Ruby on Rails approach of convention over configuration and Django's approach of generating forms from database tables and including a large amount of validators out of the box.
===<u>Controllers</u>===

====Ruby on Rails====
<pre>
class MyTestController < ApplicationController
def index
render_text “Hello World”
end
end
</pre>

====Django====

Django requires the user to specify all of his/her imports in the code:

<pre>
from django.http import HttpResponse
def index(request):
return HttpResponse("Hello World”)
</pre>

====Web2py====
<pre>
def index():
return "Hello World"
</pre>

===<u>Models</u>===

====Ruby on Rails====
<pre>
class Article < ActiveRecord::Migration
def self.up
create_table :articles do |t|
t.column :name, :string
t.column :description, :text
end
end
end
</pre>

====Django====
<pre>
class Article(models.Model):
name = models.StringField()
description = models.TextField()
</pre>

====Web2py====
<pre>
Article=db.define_table(‘Article’,
SQLField(‘email’,’string’),
SQLField(‘description’,’text’)
</pre>

===<u>Views</u>===

====Ruby on Rails====
<pre>
<table>
<% @recipes.each do |recipe| %>
<tr>
<td><%= recipe.name %></td>
</tr>
<% end %>
</table>
</pre>

====Django====
<pre>
<table>
{% for recipe in recipes %}
<tr>
<td>{{recipe.name}}</td>
</tr>
{% endfor %}
</table>
</pre>

====Web2py====
<pre>
<table>
{{for recipe in recipes:}}>
<tr>
<td>{{=recipe.name}}</td>
</tr>
{{pass}}
</table>
</pre>

== Distinguishing Features ==

=== Model/Controller Execution ===
In web2py, the Model and Controller code is not modual; rather, they are executed in a global environment with each individual HTTP request. This is different from most web development frameworks and presents a unique set of advantages and disadvantages.

Advantages:
*Simplifies development - no need to import
*Provides a clean reset of objects with every HTTP request - no need to worry about object states, overriding requests, conflicting HTTP, etc.
*Multiple applications can exist within the same instance without conflicting with one another

Disadvantages:
*Models and Controllers are not class based - code sometimes must be frequently repeated
*Inability to inherit
*Non-modular; the developer must be mindful of the order of execution

=== Online IDE ===
web2py is fully supported by an online IDE. This covers the full development spectrum, including debugging, testing, maintenance, databases, internationalization, etc. This makes it simple to begin developement without setting up any kind of environment or even installing an IDE.

== References ==
<span id="1foot">[[#1body|1.]]</span> http://www.web2py.com/init/default/index <br>
<span id="2foot">[[#2body|2.]]</span> http://en.wikipedia.org/wiki/Web2py <br>
<span id="3foot">[[#3body|3.]]</span> http://www.web2py.com/init/default/what <br>
<span id="4foot">[[#4body|4.]]</span> http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2013/oss_SocialMediaFeeds <br>
<span id="5foot">[[#5body|5.]]</span> http://mherman.org/blog/2012/12/01/crash-course-in-web2py-part-2-web-forms/#.VBT9d_ldVuJ <br>
<span id="6foot">[[#6body|6.]]</span> http://www.web2py.com/examples/static/web2py_vs_others.pdf/ Web2py vs other frameworks <br>

CSC/ECE 517 Fall 2014/ch1a a7 ch

2014-09-17T23:45:53Z

Rgschaef: /* Distinguishing Features */

= Web2py Framework =
Web2py is a free open source full-stack framework for rapid development of fast, scalable, secure and portable database-driven web-based applications written in Python.<sup><span id="1body">[[#1foot|[1]]]</span></sup>
== Background ==
Web2py was originally introduced as a teaching tool to used to demonstrate ease of use and deployment. It was modeled after [http://en.wikipedia.org/wiki/Ruby_on_Rails Ruby on Rails] and [http://en.wikipedia.org/wiki/Django_(web_framework) Django], and as such focuses on rapid development and adheres to the [http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller Model View Controller] architecture pattern.

Here are some of the features of Web2py<sup><span id="3body">[[#3foot|[2]]]</span></sup><sup><span id="4body">[[#4foot|[3]]]</span></sup>:
* Web2py runs on Windows, Mac, Unix/Linux, Google App Engine, Amazon EC2, and almost any web hosting via Python 2.5/2.6/2.7/pypy, or Java with Jython.
* Accessible anywhere, without any installation required
* Open source licensed under the [http://www.gnu.org/licenses/lgpl.html GNU LGPL v3.0 License]
* Support for mutiple databases including: SQLite, PostgreSQL, MySQL, MSSQL, FireBird, Oracle, IBM DB2, Informix, Ingres, and Google App Engine
* Equipped with a Data Abstraction Layer that removes the requirement of knowing how to write SQL by doing it for you in real-time
* Role-based authorization of resources
* Error logging and ticketing system
* An web-based administrative interface for ease of interaction

== Examples ==
There are [http://web2py.com/poweredby several websites] currently powered by Web2py, including a [http://pymines.appspot.com/ website] hosting the ever-popular game [http://en.wikipedia.org/wiki/Minesweeper_(video_game) Minesweeper].

As previously mentioned, Web2py doesn't require that you install anything, you may access and demo the capabilities online through their [http://www.web2py.com/demo_admin/default/site demo administrative interface]. At the time of this article's writing, the save demo is not fully-functional.

You may download and run web2py by following the instructions on [http://www.web2py.com/init/default/download this page].

===Code Examples===

A complete list web2py-provided examples can be found [http://www.web2py.com/init/default/examples here].

====Hello World====
Creating a web2py application can be as simple as writing a few lines in a single controller file (default.py):

<pre>
def index(): return "Hello World"
</pre>

====File Upload<sup><span id="3body">[[#3foot|[3]]]</span></sup>====
In the Model:
<pre>
db=DAL('sqlite://storage.db')
db.define_table('image',
Field('name', notnull=True),
Field('file','upload'))
</pre>

In the Controller:
<pre>
def index():
form = SQLFORM(db.image).process()
if form.accepted:
response.flash = 'image uploaded'
return locals()
</pre>

In the View:
<pre>
{{extend 'layout.html'}}
<h1>Image upload form</h1>
{{=form}}
</pre>

[[File:ImageUpload.PNG]]

====Forms<sup><span id="5body">[[#5foot|[5]]]</span></sup>====

In the Model:
<pre>
db = DAL('sqlite://webform.sqlite')
db.define_table('register',
Field('first_name', requires=IS_NOT_EMPTY()),
Field('last_name', requires=IS_NOT_EMPTY()),
Field('email', requires=IS_NOT_EMPTY()))
</pre>

In the Controller:
<pre>
def display_your_form():
form = SQLFORM(db.register)
return dict(form=form)
</pre>

In the View:
<pre>
<center>
<br /><br /><br />
<h1>Web Form</h1>
<br />
<h2>Inputs:</h2>
{{=form}}
<h2>Submitted variables:</h2>
{{=BEAUTIFY(request.vars)}}
</center>
</pre>

[[File:Webform.png]]

==Architecture==

Web2py follows a Model-View-Controller (MVC) architecture.

* '''Model''' - The data
* '''View''' - Presents the data in a user-friendly way.
* '''Controller''' - Acts as the glue between the model and view and handles the logic for displaying the data.

[[File:MVC-Process.png]]

This diagram shows an example of how web2py handles requests and renders the request to the browser:

[[File:Architecture.PNG]]

==Comparison to other Frameworks==
Since web2py was inspiried by Rails and Django, it draws ideas from each.

The creators of web2py borrowed the Ruby on Rails approach of convention over configuration and Django's approach of generating forms from database tables and including a large amount of validators out of the box.
===<u>Controllers</u>===

====Ruby on Rails====
<pre>
class MyTestController < ApplicationController
def index
render_text “Hello World”
end
end
</pre>

====Django====

Django requires the user to specify all of his/her imports in the code:

<pre>
from django.http import HttpResponse
def index(request):
return HttpResponse("Hello World”)
</pre>

====Web2py====
<pre>
def index():
return "Hello World"
</pre>

===<u>Models</u>===

====Ruby on Rails====
<pre>
class Article < ActiveRecord::Migration
def self.up
create_table :articles do |t|
t.column :name, :string
t.column :description, :text
end
end
end
</pre>

====Django====
<pre>
class Article(models.Model):
name = models.StringField()
description = models.TextField()
</pre>

====Web2py====
<pre>
Article=db.define_table(‘Article’,
SQLField(‘email’,’string’),
SQLField(‘description’,’text’)
</pre>

===<u>Views</u>===

====Ruby on Rails====
<pre>
<table>
<% @recipes.each do |recipe| %>
<tr>
<td><%= recipe.name %></td>
</tr>
<% end %>
</table>
</pre>

====Django====
<pre>
<table>
{% for recipe in recipes %}
<tr>
<td>{{recipe.name}}</td>
</tr>
{% endfor %}
</table>
</pre>

====Web2py====
<pre>
<table>
{{for recipe in recipes:}}>
<tr>
<td>{{=recipe.name}}</td>
</tr>
{{pass}}
</table>
</pre>

== Distinguishing Features ==

=== Model/Controller Execution ===
In web2py, the Model and Controller code is not modual; rather, they are executed in a global environment with each individual HTTP request. This is different from most web development frameworks and presents a unique set of advantages and disadvantages.

Advantages:
*Simplifies development - no need to import
*Provides a clean reset of objects with every HTTP request - no need to worry about object states, overriding requests, conflicting HTTP, etc.
*Multiple applications can exist within the same instance without conflicting with one another

Disadvantages:
*Models and Controllers are not class based - code sometimes must be frequently repeated
*Inability to inherit
*Non-modular; the developer must be mindful of the order of execution

=== Online IDE ===
web2py is fully supported by an online IDE. This covers the full development spectrum, including debugging, testing, maintenance, databases, internationalization, etc. This makes it simple to begin developement without setting up any kind of environment or even installing an IDE.

== References ==
<span id="1foot">[[#1body|1.]]</span> http://www.web2py.com/init/default/index <br>
<span id="2foot">[[#2body|2.]]</span> http://en.wikipedia.org/wiki/Web2py <br>
<span id="3foot">[[#3body|3.]]</span> http://www.web2py.com/init/default/what <br>
<span id="4foot">[[#4body|4.]]</span> http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2013/oss_SocialMediaFeeds <br>
<span id="5foot">[[#5body|5.]]</span> http://mherman.org/blog/2012/12/01/crash-course-in-web2py-part-2-web-forms/#.VBT9d_ldVuJ <br>
<span id="6foot">[[#6body|6.]]</span> http://www.web2py.com/examples/static/web2py_vs_others.pdf/ Web2py vs other frameworks <br>

CSC/ECE 517 Fall 2014/ch1a a7 ch

2014-09-17T23:30:51Z

Rgschaef: