https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&feedformat=atom&user=Asankar3 2026-05-16T14:18:53Z User contributions MediaWiki 1.41.0 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_at&diff=82339 2013-10-31T23:14:59Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo&lt;ref&gt; http://www.webmonkey.com/2013/04/mozillas-servo/ &lt;/ref&gt; is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo&lt;ref&gt; http://paulrouget.com/e/servo/ &lt;/ref&gt; is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs. It's important to actually be fast. We must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has a fairly novel type system, specifically to enable safe parallel types and algorithms, and we have to figure out how to use it effectively.<br /> :*Language immaturity. The Rust compiler and language are not yet stable. Rust also has fewer libraries than C++ available; we can bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> :*Parallel-hostile libraries. Some third-party libraries we need don't play well in multi-threaded environments. Fonts in particular have been difficult. Even if libraries are technically thread-safe, often thread safety is achieved through a library-wide mutex lock, harming our opportunities for parallelism.<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> <br /> :*Each box represents a Rust task.<br /> :*Blue boxes represent the primary tasks in the browser pipeline.<br /> :*Gray boxes represent tasks auxiliary to the browser pipeline.<br /> :*White boxes represent worker tasks. Each such box represents several tasks, the precise number of which will vary with the workload.<br /> :*Dashed lines indicate supervisor relationships.<br /> :*Solid lines indicate communication channels.<br /> <br /> =='''Dynamic style additions/removals'''==<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> ==='''Work done in Part 1'''===<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_at&diff=82338 2013-10-31T23:14:23Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo&lt;ref&gt; http://www.webmonkey.com/2013/04/mozillas-servo/ &lt;/ref&gt; is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo&lt;ref&gt; http://paulrouget.com/e/servo/ &lt;/ref&gt; is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs. It's important to actually be fast. We must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has a fairly novel type system, specifically to enable safe parallel types and algorithms, and we have to figure out how to use it effectively.<br /> :*Language immaturity. The Rust compiler and language are not yet stable. Rust also has fewer libraries than C++ available; we can bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> :*Parallel-hostile libraries. Some third-party libraries we need don't play well in multi-threaded environments. Fonts in particular have been difficult. Even if libraries are technically thread-safe, often thread safety is achieved through a library-wide mutex lock, harming our opportunities for parallelism.<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> =='''Dynamic style additions/removals'''==<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> ==='''Work done in Part 1'''===<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> :*Each box represents a Rust task.<br /> :*Blue boxes represent the primary tasks in the browser pipeline.<br /> :*Gray boxes represent tasks auxiliary to the browser pipeline.<br /> :*White boxes represent worker tasks. Each such box represents several tasks, the precise number of which will vary with the workload.<br /> :*Dashed lines indicate supervisor relationships.<br /> :*Solid lines indicate communication channels.<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_at&diff=82337 2013-10-31T23:14:07Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo&lt;ref&gt; http://www.webmonkey.com/2013/04/mozillas-servo/ &lt;/ref&gt; is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo&lt;ref&gt; http://paulrouget.com/e/servo/ &lt;/ref&gt; is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs. It's important to actually be fast. We must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has a fairly novel type system, specifically to enable safe parallel types and algorithms, and we have to figure out how to use it effectively.<br /> :*Language immaturity. The Rust compiler and language are not yet stable. Rust also has fewer libraries than C++ available; we can bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> :*Parallel-hostile libraries. Some third-party libraries we need don't play well in multi-threaded environments. Fonts in particular have been difficult. Even if libraries are technically thread-safe, often thread safety is achieved through a library-wide mutex lock, harming our opportunities for parallelism.<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> =='''Dynamic style additions/removals'''==<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done in Part 1'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> :*Each box represents a Rust task.<br /> :*Blue boxes represent the primary tasks in the browser pipeline.<br /> :*Gray boxes represent tasks auxiliary to the browser pipeline.<br /> :*White boxes represent worker tasks. Each such box represents several tasks, the precise number of which will vary with the workload.<br /> :*Dashed lines indicate supervisor relationships.<br /> :*Solid lines indicate communication channels.<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_at&diff=82336 2013-10-31T23:13:24Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo&lt;ref&gt; http://www.webmonkey.com/2013/04/mozillas-servo/ &lt;/ref&gt; is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo&lt;ref&gt; http://paulrouget.com/e/servo/ &lt;/ref&gt; is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs. It's important to actually be fast. We must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has a fairly novel type system, specifically to enable safe parallel types and algorithms, and we have to figure out how to use it effectively.<br /> :*Language immaturity. The Rust compiler and language are not yet stable. Rust also has fewer libraries than C++ available; we can bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> :*Parallel-hostile libraries. Some third-party libraries we need don't play well in multi-threaded environments. Fonts in particular have been difficult. Even if libraries are technically thread-safe, often thread safety is achieved through a library-wide mutex lock, harming our opportunities for parallelism.<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> ==''Dynamic style additions/removals''==<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done in Part 1'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> :*Each box represents a Rust task.<br /> :*Blue boxes represent the primary tasks in the browser pipeline.<br /> :*Gray boxes represent tasks auxiliary to the browser pipeline.<br /> :*White boxes represent worker tasks. Each such box represents several tasks, the precise number of which will vary with the workload.<br /> :*Dashed lines indicate supervisor relationships.<br /> :*Solid lines indicate communication channels.<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_at&diff=82335 2013-10-31T23:12:49Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo&lt;ref&gt; http://www.webmonkey.com/2013/04/mozillas-servo/ &lt;/ref&gt; is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo&lt;ref&gt; http://paulrouget.com/e/servo/ &lt;/ref&gt; is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs. It's important to actually be fast. We must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has a fairly novel type system, specifically to enable safe parallel types and algorithms, and we have to figure out how to use it effectively.<br /> :*Language immaturity. The Rust compiler and language are not yet stable. Rust also has fewer libraries than C++ available; we can bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> :*Parallel-hostile libraries. Some third-party libraries we need don't play well in multi-threaded environments. Fonts in particular have been difficult. Even if libraries are technically thread-safe, often thread safety is achieved through a library-wide mutex lock, harming our opportunities for parallelism.<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> ==''Dynamic style additions/removals''==<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> ==='''Work done in Part 1'''===<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> :*Each box represents a Rust task.<br /> :*Blue boxes represent the primary tasks in the browser pipeline.<br /> :*Gray boxes represent tasks auxiliary to the browser pipeline.<br /> :*White boxes represent worker tasks. Each such box represents several tasks, the precise number of which will vary with the workload.<br /> :*Dashed lines indicate supervisor relationships.<br /> :*Solid lines indicate communication channels.<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_at&diff=82334 2013-10-31T23:10:59Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo&lt;ref&gt; http://www.webmonkey.com/2013/04/mozillas-servo/ &lt;/ref&gt; is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo&lt;ref&gt; http://paulrouget.com/e/servo/ &lt;/ref&gt; is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs. It's important to actually be fast. We must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has a fairly novel type system, specifically to enable safe parallel types and algorithms, and we have to figure out how to use it effectively.<br /> :*Language immaturity. The Rust compiler and language are not yet stable. Rust also has fewer libraries than C++ available; we can bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> :*Parallel-hostile libraries. Some third-party libraries we need don't play well in multi-threaded environments. Fonts in particular have been difficult. Even if libraries are technically thread-safe, often thread safety is achieved through a library-wide mutex lock, harming our opportunities for parallelism.<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done in Part 1'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> :*Each box represents a Rust task.<br /> :*Blue boxes represent the primary tasks in the browser pipeline.<br /> :*Gray boxes represent tasks auxiliary to the browser pipeline.<br /> :*White boxes represent worker tasks. Each such box represents several tasks, the precise number of which will vary with the workload.<br /> :*Dashed lines indicate supervisor relationships.<br /> :*Solid lines indicate communication channels.<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_at&diff=82332 2013-10-31T23:09:53Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo&lt;ref&gt; http://www.webmonkey.com/2013/04/mozillas-servo/ &lt;/ref&gt; is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo&lt;ref&gt; http://paulrouget.com/e/servo/ &lt;/ref&gt; is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs. It's important to actually be fast. We must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has a fairly novel type system, specifically to enable safe parallel types and algorithms, and we have to figure out how to use it effectively.<br /> :*Language immaturity. The Rust compiler and language are not yet stable. Rust also has fewer libraries than C++ available; we can bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> :*Parallel-hostile libraries. Some third-party libraries we need don't play well in multi-threaded environments. Fonts in particular have been difficult. Even if libraries are technically thread-safe, often thread safety is achieved through a library-wide mutex lock, harming our opportunities for parallelism.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done in Part 1'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> <br /> :*Each box represents a Rust task.<br /> :*Blue boxes represent the primary tasks in the browser pipeline.<br /> :*Gray boxes represent tasks auxiliary to the browser pipeline.<br /> :*White boxes represent worker tasks. Each such box represents several tasks, the precise number of which will vary with the workload.<br /> :*Dashed lines indicate supervisor relationships.<br /> :*Solid lines indicate communication channels.<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_at&diff=82331 2013-10-31T23:09:33Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo&lt;ref&gt; http://www.webmonkey.com/2013/04/mozillas-servo/ &lt;/ref&gt; is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo&lt;ref&gt; http://paulrouget.com/e/servo/ &lt;/ref&gt; is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs. It's important to actually be fast. We must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has a fairly novel type system, specifically to enable safe parallel types and algorithms, and we have to figure out how to use it effectively.<br /> :*Language immaturity. The Rust compiler and language are not yet stable. Rust also has fewer libraries than C++ available; we can bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> :*Parallel-hostile libraries. Some third-party libraries we need don't play well in multi-threaded environments. Fonts in particular have been difficult. Even if libraries are technically thread-safe, often thread safety is achieved through a library-wide mutex lock, harming our opportunities for parallelism.<br /> <br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done in Part 1'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> <br /> :*Each box represents a Rust task.<br /> :*Blue boxes represent the primary tasks in the browser pipeline.<br /> :*Gray boxes represent tasks auxiliary to the browser pipeline.<br /> :*White boxes represent worker tasks. Each such box represents several tasks, the precise number of which will vary with the workload.<br /> :*Dashed lines indicate supervisor relationships.<br /> :*Solid lines indicate communication channels.<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_at&diff=82325 2013-10-31T22:47:54Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo&lt;ref&gt; http://www.webmonkey.com/2013/04/mozillas-servo/ &lt;/ref&gt; is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo&lt;ref&gt; http://paulrouget.com/e/servo/ &lt;/ref&gt; is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> <br /> :*Each box represents a Rust task.<br /> :*Blue boxes represent the primary tasks in the browser pipeline.<br /> :*Gray boxes represent tasks auxiliary to the browser pipeline.<br /> :*White boxes represent worker tasks. Each such box represents several tasks, the precise number of which will vary with the workload.<br /> :*Dashed lines indicate supervisor relationships.<br /> :*Solid lines indicate communication channels.<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_at&diff=82318 2013-10-31T22:44:34Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo&lt;ref&gt; http://www.webmonkey.com/2013/04/mozillas-servo/ &lt;/ref&gt; is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> <br /> :*Each box represents a Rust task.<br /> :*Blue boxes represent the primary tasks in the browser pipeline.<br /> :*Gray boxes represent tasks auxiliary to the browser pipeline.<br /> :*White boxes represent worker tasks. Each such box represents several tasks, the precise number of which will vary with the workload.<br /> :*Dashed lines indicate supervisor relationships.<br /> :*Solid lines indicate communication channels.<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_at&diff=82309 2013-10-31T22:21:44Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> <br /> :*Each box represents a Rust task.<br /> :*Blue boxes represent the primary tasks in the browser pipeline.<br /> :*Gray boxes represent tasks auxiliary to the browser pipeline.<br /> :*White boxes represent worker tasks. Each such box represents several tasks, the precise number of which will vary with the workload.<br /> :*Dashed lines indicate supervisor relationships.<br /> :*Solid lines indicate communication channels.<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=82238 2013-10-31T04:12:47Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> :* Each box represents a Rust task.<br /> :* Blue boxes represent the primary tasks in the browser pipeline.<br /> :* Gray boxes represent tasks auxiliary to the browser pipeline.<br /> :* White boxes represent worker tasks. Each such box represents several tasks, the precise number of which will vary with the workload.<br /> :* Dashed lines indicate supervisor relationships.<br /> :* Solid lines indicate communication channels.<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_at&diff=82236 2013-10-31T04:11:51Z

<p>Asankar3: Created page with &quot;='''Dynamic style additions/removals'''= This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo brows...&quot;</p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() method in [https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs] file has been [http://en.wikipedia.org/wiki/Code_refactoring refactored] to recognize when a style element is appended in an HTML file. Whenever a style element is appended, [https://github.com/mozilla/servo/blob/master/src/components/script/html/cssparse.rs CSS parser] need to be invoked that parses through the content present within the [http://www.w3schools.com/tags/tag_style.asp style element] and renders the output to the Layout task with all the CSS rules applied on the HTML content. Previously, the CSS style rules were applied only when the rules are appended using link element as an external stylesheet. <br /> <br /> '''Functionality Added :''' First the code will check whether the new child node that has been appended is a style node. If yes, A dummy URL is set into the URL variable, and the content that is present within the style tag is wrapped by &quot;NodeWrapping&quot; implementation and stored in a variable called &quot;data&quot; Then both URL and data are assigned to Inline Provenance - A member of enum variable &quot;CSSTaskNewFile&quot; that CSS parser uses to differentiate between link element and style element. Then css_spawn_parser method is called which does the parsing and renders the output to the Layout Task.<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/test/html/content/test_collections.html test_collections.html]'''<br /> :*'''[https://github.com/tmuthuk/servo/blob/master/src/components/script/dom/node.rs node.rs]'''<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013&diff=82233 2013-10-31T04:10:08Z

<p>Asankar3: </p> <hr /> <div>* [[ CSC/ECE 517 Fall 2012/ch1 1w23 ph ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w30 nn]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w21 w]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w01 aj]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w24 nv]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w29 rkld]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w25 aras]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w30 ps]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w19 rj]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w18 bs]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w17 pk]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w22 ss]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w12 vn]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w14 st]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w08 cc]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w10 ga ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w26 as ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w27 ma ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w13 aa ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w11 sv ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w07 d ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w20 gq ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w03 ss ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w28 nm ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w02 pp ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w6 zs ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w04 y ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w05 st ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w09 hs ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w32 av ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w48 x ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w43 av]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w46 ka]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w33 aa]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w35 sa ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w39 as ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w31 vm ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w43 sm ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w44 s ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w47 ka ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w34 fs ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w40 ao ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss fmv ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss vna ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss paa ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss mapFeeds ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss ssp ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch2 0e808 nsv ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss aoa ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss cmh ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss ans ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss ssv]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E818 mra ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss SocialMediaFeeds ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E811 syn ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E804 spb ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E812 amp ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss S805 ahs ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E820 gzs ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E816 cyy ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss M801 at ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E814 vd ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E815 saa]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E810 aas ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E805 kkn ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss M803 ana ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E802 jst ]]</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81299 2013-10-30T20:32:32Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layout''===<br /> The appendchild() is modified to recognize when an element is being appended and then the sent to layour.(To be modified).<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''test_collections.html'''<br /> :*'''node.rs'''<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81297 2013-10-30T20:31:36Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> ===''Appending an element and sending it to layour''===<br /> The following two files were modified to include the new code.<br /> <br /> :*'''test_collections.html'''<br /> :*'''node.rs'''<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81296 2013-10-30T20:30:57Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ====''Testing Dynamic elements in HTML''====<br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''test_collections.html'''<br /> :*'''node.rs'''<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81295 2013-10-30T20:30:26Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ===''Testing Dynamic elements in HTML''=== <br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''test_collections.html'''<br /> :*'''node.rs'''<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred for setting up the environment as it is simple and easy.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81292 2013-10-30T20:29:05Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ===''Testing Dynamic elements in HTML''=== <br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''test_collections.html'''<br /> :*'''node.rs'''<br /> <br /> Below is a pictorial representation of the servo task communication <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred as the installation steps for setting up the environment as simple compared to windows.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81285 2013-10-30T20:22:23Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ===''Testing Dynamic elements in HTML''=== <br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''test_collections.html'''<br /> :*'''node.rs'''<br /> <br /> [[File:task.jpg|center|alt=Sample task communication diagram| Fig 1: Servo Task Communication diagram]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred as the installation steps for setting up the environment as simple compared to windows.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=File:Task.jpg&diff=81283 2013-10-30T20:21:01Z

<p>Asankar3: Task Communication</p> <hr /> <div>Task Communication</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81277 2013-10-30T20:17:28Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ===''Testing Dynamic elements in HTML''=== <br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''test_collections.html'''<br /> :*'''node.rs'''<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: fil_name]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred as the installation steps for setting up the environment as simple compared to windows.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81276 2013-10-30T20:17:02Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> =='''Work done so far'''==<br /> ===''Testing Dynamic elements in HTML''=== <br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> The following two files were modified to include the new code.<br /> <br /> :*'''test_collections.html'''<br /> :*'''node.rs'''<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred as the installation steps for setting up the environment as simple compared to windows.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81271 2013-10-30T20:15:12Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> ==''Work done so far''==<br /> ===''Testing Dynamic elements in HTML''=== <br /> A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> :'''test_collections.html'''<br /> :'''node.rs'''<br /> <br /> <br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred as the installation steps for setting up the environment as simple compared to windows.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81268 2013-10-30T20:14:25Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> ==''Work done so far''==<br /> <br /> :* A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> :'''test_collections.html'''<br /> :'''node.rs'''<br /> <br /> <br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred as the installation steps for setting up the environment as simple compared to windows.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81267 2013-10-30T20:14:02Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> :*Performance. Parallel algorithms tend to involve tough trade offs and it must ensure that Rust itself has performance comparable to C++.<br /> :*Data structures. Rust has new type system, specifically to enable safe parallel types and algorithms.<br /> :*Language immaturity. The Rust compiler and language are yet to reach stability. Rust also has fewer libraries than C++ available. It is possible to bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> ===''Work done so far''===<br /> <br /> :* A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> :'''test_collections.html'''<br /> :'''node.rs'''<br /> <br /> <br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred as the installation steps for setting up the environment as simple compared to windows.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81263 2013-10-30T20:11:42Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Challenges''===<br /> <br /> Performance. Parallel algorithms tend to involve tough trade offs. It's important to actually be fast. We must ensure that Rust itself has performance comparable to C++.<br /> Data structures. Rust has a fairly novel type system, specifically to enable safe parallel types and algorithms, and we have to figure out how to use it effectively.<br /> Language immaturity. The Rust compiler and language are not yet stable. Rust also has fewer libraries than C++ available; we can bind to C++ libraries, but that involves more work than simply using the C++ header files.<br /> Parallel-hostile libraries. Some third-party libraries we need don't play well in multi-threaded environments. Fonts in particular have been difficult. Even if libraries are technically thread-safe, often thread safety is achieved through a library-wide mutex lock, harming our opportunities for parallelism.<br /> <br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> ===''Work done so far''===<br /> <br /> :* A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model to manipulate the HTML elements. The test demonstrates the following:<br /> <br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> :'''test_collections.html'''<br /> :'''node.rs'''<br /> <br /> <br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred as the installation steps for setting up the environment as simple compared to windows.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81254 2013-10-30T20:08:45Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> ===''Work done so far''===<br /> <br /> :* A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model. The test demonstrates the following:<br /> :*appending a new link element that references a stylesheet.<br /> :*appending a new style element that contains rule.<br /> :*removing an existing link element that references a stylesheet.<br /> :*remove an existing style element that contains rules.<br /> :*modifying the content of a style element (such as removing all content).<br /> :*modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> :'''test_collections.html'''<br /> :'''node.rs'''<br /> <br /> <br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred as the installation steps for setting up the environment as simple compared to windows.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81252 2013-10-30T20:07:23Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> ===''Work done so far''===<br /> <br /> :* A test html code that runs successfully in Firefox/chrome is created first before testing the changes in Servo. The test cases are written in Javascript using the Document Object Model. The test demonstrates the following:<br /> ::**appending a new link element that references a stylesheet.<br /> ::**appending a new style element that contains rule.<br /> ::**removing an existing link element that references a stylesheet.<br /> ::**remove an existing style element that contains rules.<br /> ::**modifying the content of a style element (such as removing all content).<br /> ::**modifying the href attribute of a link element that points at a stylesheet (such as referencing a new one that does not exist).<br /> <br /> :'''test_collections.html'''<br /> :'''node.rs'''<br /> <br /> <br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred as the installation steps for setting up the environment as simple compared to windows.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81221 2013-10-30T19:48:12Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> <br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, [http://en.wikipedia.org/wiki/JavaScript javascript]&lt;ref&gt;http://en.wikipedia.org/wiki/JavaScript&lt;/ref&gt;, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> <br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''&lt;ref&gt;http://en.wikipedia.org/wiki/Convention_over_configuration&lt;/ref&gt;=== <br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''&lt;ref&gt;http://guides.rubyonrails.org/getting_started.html&lt;/ref&gt;===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> '''Below is an example code for test driven development.'''<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* [http://guides.rubyonrails.org/layouts_and_rendering.html Partials] are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This [http://bundler.io/ bundler]&lt;ref&gt;http://bundler.io/&lt;/ref&gt; installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> <br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of [http://guides.rubyonrails.org/migrations.html Migration]&lt;ref&gt;http://guides.rubyonrails.org/migrations.html&lt;/ref&gt; Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as [http://coffeescript.org/ Coffeescript] can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> <br /> ===''Assets Pipeline''&lt;ref&gt;http://guides.rubyonrails.org/asset_pipeline.html&lt;/ref&gt;===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''&lt;ref&gt;http://blog.websitesframeworks.com/2013/03/web-framework-comparison-matt-raible-opinion-138/&lt;/ref&gt;==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient web framework used. GWT and GRAILS also are on par with RAILS.<br /> :* The graph depicts the five main features that any Agile Web Framework should support and these are supported by Rails thus giving both clients and developers a simple and efficient way to develop several complex web applications.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Appendix'''==<br /> ===''Setting up Servo''===<br /> There are two main steps to set up the environment for this project. Linux environment is preferred as the installation steps for setting up the environment as simple compared to windows.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;<br /> :* [https://github.com/mozilla/servo Build Servo] &lt;ref&gt; https://github.com/mozilla/servo &lt;/ref&gt;<br /> <br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81212 2013-10-30T19:44:55Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for dynamically appending, removing or modifying elements that causes a visible change.<br /> :*Recognize when an element is being appended and get the element to the layout.<br /> :*Network requests and removal of newly added stylesheets.<br /> <br /> <br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, [http://en.wikipedia.org/wiki/JavaScript javascript]&lt;ref&gt;http://en.wikipedia.org/wiki/JavaScript&lt;/ref&gt;, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> <br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''&lt;ref&gt;http://en.wikipedia.org/wiki/Convention_over_configuration&lt;/ref&gt;=== <br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''&lt;ref&gt;http://guides.rubyonrails.org/getting_started.html&lt;/ref&gt;===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> '''Below is an example code for test driven development.'''<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* [http://guides.rubyonrails.org/layouts_and_rendering.html Partials] are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This [http://bundler.io/ bundler]&lt;ref&gt;http://bundler.io/&lt;/ref&gt; installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> <br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of [http://guides.rubyonrails.org/migrations.html Migration]&lt;ref&gt;http://guides.rubyonrails.org/migrations.html&lt;/ref&gt; Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as [http://coffeescript.org/ Coffeescript] can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> <br /> ===''Assets Pipeline''&lt;ref&gt;http://guides.rubyonrails.org/asset_pipeline.html&lt;/ref&gt;===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''&lt;ref&gt;http://blog.websitesframeworks.com/2013/03/web-framework-comparison-matt-raible-opinion-138/&lt;/ref&gt;==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient web framework used. GWT and GRAILS also are on par with RAILS.<br /> :* The graph depicts the five main features that any Agile Web Framework should support and these are supported by Rails thus giving both clients and developers a simple and efficient way to develop several complex web applications.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Appendix'''<br /> ===''Setting up Servo''<br /> There are two main steps to set up the environment for this project.<br /> <br /> :* [https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust Build Rust] &lt;ref&gt; https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust &lt;/ref&gt;==<br /> :* Build Servo<br /> * [https://soundcloud.com SoundCloud]<br /> * [https://github.com/ GitHub]<br /> * [http://www.yellow.com YellowPages]<br /> * [http://www.shopify.com Shopify]<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81193 2013-10-30T19:31:48Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo?''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''What is this project about?''===<br /> <br /> This project deals mainly with communicating between tasks. <br /> <br /> :*Test cases for the following scenarios<br /> :**Dynamically appending, removing or changing elements that causes a visible change.<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, [http://en.wikipedia.org/wiki/JavaScript javascript]&lt;ref&gt;http://en.wikipedia.org/wiki/JavaScript&lt;/ref&gt;, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> <br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''&lt;ref&gt;http://en.wikipedia.org/wiki/Convention_over_configuration&lt;/ref&gt;=== <br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''&lt;ref&gt;http://guides.rubyonrails.org/getting_started.html&lt;/ref&gt;===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> '''Below is an example code for test driven development.'''<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* [http://guides.rubyonrails.org/layouts_and_rendering.html Partials] are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This [http://bundler.io/ bundler]&lt;ref&gt;http://bundler.io/&lt;/ref&gt; installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> <br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of [http://guides.rubyonrails.org/migrations.html Migration]&lt;ref&gt;http://guides.rubyonrails.org/migrations.html&lt;/ref&gt; Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as [http://coffeescript.org/ Coffeescript] can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> <br /> ===''Assets Pipeline''&lt;ref&gt;http://guides.rubyonrails.org/asset_pipeline.html&lt;/ref&gt;===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''&lt;ref&gt;http://blog.websitesframeworks.com/2013/03/web-framework-comparison-matt-raible-opinion-138/&lt;/ref&gt;==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient web framework used. GWT and GRAILS also are on par with RAILS.<br /> :* The graph depicts the five main features that any Agile Web Framework should support and these are supported by Rails thus giving both clients and developers a simple and efficient way to develop several complex web applications.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * [https://twitter.com Twitter]<br /> * [http://www.groupon.com Groupon]<br /> * [https://soundcloud.com SoundCloud]<br /> * [https://github.com/ GitHub]<br /> * [http://www.yellow.com YellowPages]<br /> * [http://www.shopify.com Shopify]<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81167 2013-10-30T19:22:27Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo ''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Why is the this project about?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, [http://en.wikipedia.org/wiki/JavaScript javascript]&lt;ref&gt;http://en.wikipedia.org/wiki/JavaScript&lt;/ref&gt;, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> <br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''&lt;ref&gt;http://en.wikipedia.org/wiki/Convention_over_configuration&lt;/ref&gt;=== <br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''&lt;ref&gt;http://guides.rubyonrails.org/getting_started.html&lt;/ref&gt;===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> '''Below is an example code for test driven development.'''<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* [http://guides.rubyonrails.org/layouts_and_rendering.html Partials] are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This [http://bundler.io/ bundler]&lt;ref&gt;http://bundler.io/&lt;/ref&gt; installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> <br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of [http://guides.rubyonrails.org/migrations.html Migration]&lt;ref&gt;http://guides.rubyonrails.org/migrations.html&lt;/ref&gt; Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as [http://coffeescript.org/ Coffeescript] can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> <br /> ===''Assets Pipeline''&lt;ref&gt;http://guides.rubyonrails.org/asset_pipeline.html&lt;/ref&gt;===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''&lt;ref&gt;http://blog.websitesframeworks.com/2013/03/web-framework-comparison-matt-raible-opinion-138/&lt;/ref&gt;==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient web framework used. GWT and GRAILS also are on par with RAILS.<br /> :* The graph depicts the five main features that any Agile Web Framework should support and these are supported by Rails thus giving both clients and developers a simple and efficient way to develop several complex web applications.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * [https://twitter.com Twitter]<br /> * [http://www.groupon.com Groupon]<br /> * [https://soundcloud.com SoundCloud]<br /> * [https://github.com/ GitHub]<br /> * [http://www.yellow.com YellowPages]<br /> * [http://www.shopify.com Shopify]<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81161 2013-10-30T19:20:27Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo ''=== <br /> <br /> Servo is a research project whose goal is to develop a new Web browser engine that makes use of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races. Given that C++ is poorly suited to prevent these problems, Servo is written in [http://en.wikipedia.org/wiki/Rust_%28programming_language%29 Rust programming language]. Rust provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine.<br /> <br /> ===''Why is the this project about?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, [http://en.wikipedia.org/wiki/JavaScript javascript]&lt;ref&gt;http://en.wikipedia.org/wiki/JavaScript&lt;/ref&gt;, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> <br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''&lt;ref&gt;http://en.wikipedia.org/wiki/Convention_over_configuration&lt;/ref&gt;=== <br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''&lt;ref&gt;http://guides.rubyonrails.org/getting_started.html&lt;/ref&gt;===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> '''Below is an example code for test driven development.'''<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* [http://guides.rubyonrails.org/layouts_and_rendering.html Partials] are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This [http://bundler.io/ bundler]&lt;ref&gt;http://bundler.io/&lt;/ref&gt; installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> <br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of [http://guides.rubyonrails.org/migrations.html Migration]&lt;ref&gt;http://guides.rubyonrails.org/migrations.html&lt;/ref&gt; Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as [http://coffeescript.org/ Coffeescript] can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> <br /> ===''Assets Pipeline''&lt;ref&gt;http://guides.rubyonrails.org/asset_pipeline.html&lt;/ref&gt;===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''&lt;ref&gt;http://blog.websitesframeworks.com/2013/03/web-framework-comparison-matt-raible-opinion-138/&lt;/ref&gt;==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient web framework used. GWT and GRAILS also are on par with RAILS.<br /> :* The graph depicts the five main features that any Agile Web Framework should support and these are supported by Rails thus giving both clients and developers a simple and efficient way to develop several complex web applications.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * [https://twitter.com Twitter]<br /> * [http://www.groupon.com Groupon]<br /> * [https://soundcloud.com SoundCloud]<br /> * [https://github.com/ GitHub]<br /> * [http://www.yellow.com YellowPages]<br /> * [http://www.shopify.com Shopify]<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81142 2013-10-30T19:11:20Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo ''=== <br /> <br /> :Servo is a research project to develop a new Web browser engine. Our goal is to create an architecture that takes advantage of parallelism at many levels while eliminating common sources of bugs and security vulnerabilities associated with incorrect memory management and data races.<br /> <br /> Because C++ is poorly suited to preventing these problems, Servo is written in Rust, a new language designed specifically with Servo's requirements in mind. Rust provides a task-parallel infrastructure and a strong type system that enforces memory safety and data race freedom.<br /> <br /> When making design decisions we will prioritize the features of the modern web platform that are amenable to high-performance, dynamic, and media-rich applications, potentially at the cost of features that cannot be optimized. We want to know what a fast and responsive web platform looks like, and to implement it.<br /> <br /> Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine. Although Servo is a research project, it is designed to be &quot;productizable&quot;—the code that we write should be of high enough quality that it could eventually be shipped to users.<br /> <br /> ===''Why do we need Agile development?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, [http://en.wikipedia.org/wiki/JavaScript javascript]&lt;ref&gt;http://en.wikipedia.org/wiki/JavaScript&lt;/ref&gt;, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> <br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''&lt;ref&gt;http://en.wikipedia.org/wiki/Convention_over_configuration&lt;/ref&gt;=== <br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''&lt;ref&gt;http://guides.rubyonrails.org/getting_started.html&lt;/ref&gt;===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> '''Below is an example code for test driven development.'''<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* [http://guides.rubyonrails.org/layouts_and_rendering.html Partials] are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This [http://bundler.io/ bundler]&lt;ref&gt;http://bundler.io/&lt;/ref&gt; installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> <br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of [http://guides.rubyonrails.org/migrations.html Migration]&lt;ref&gt;http://guides.rubyonrails.org/migrations.html&lt;/ref&gt; Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as [http://coffeescript.org/ Coffeescript] can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> <br /> ===''Assets Pipeline''&lt;ref&gt;http://guides.rubyonrails.org/asset_pipeline.html&lt;/ref&gt;===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''&lt;ref&gt;http://blog.websitesframeworks.com/2013/03/web-framework-comparison-matt-raible-opinion-138/&lt;/ref&gt;==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient web framework used. GWT and GRAILS also are on par with RAILS.<br /> :* The graph depicts the five main features that any Agile Web Framework should support and these are supported by Rails thus giving both clients and developers a simple and efficient way to develop several complex web applications.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * [https://twitter.com Twitter]<br /> * [http://www.groupon.com Groupon]<br /> * [https://soundcloud.com SoundCloud]<br /> * [https://github.com/ GitHub]<br /> * [http://www.yellow.com YellowPages]<br /> * [http://www.shopify.com Shopify]<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81138 2013-10-30T19:09:24Z

<p>Asankar3: </p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser. Here you can find a brief description about the servo project, rust programming language, requirements of this particular project, setting up of the development environment and other relevant details.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo ''=== <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. By involving continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software, it focuses on empowering people to collaborate and make decisions together quickly and effectively. Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> ===''Why do we need Agile development?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, [http://en.wikipedia.org/wiki/JavaScript javascript]&lt;ref&gt;http://en.wikipedia.org/wiki/JavaScript&lt;/ref&gt;, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> <br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''&lt;ref&gt;http://en.wikipedia.org/wiki/Convention_over_configuration&lt;/ref&gt;=== <br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''&lt;ref&gt;http://guides.rubyonrails.org/getting_started.html&lt;/ref&gt;===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> '''Below is an example code for test driven development.'''<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* [http://guides.rubyonrails.org/layouts_and_rendering.html Partials] are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This [http://bundler.io/ bundler]&lt;ref&gt;http://bundler.io/&lt;/ref&gt; installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> <br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of [http://guides.rubyonrails.org/migrations.html Migration]&lt;ref&gt;http://guides.rubyonrails.org/migrations.html&lt;/ref&gt; Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as [http://coffeescript.org/ Coffeescript] can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> <br /> ===''Assets Pipeline''&lt;ref&gt;http://guides.rubyonrails.org/asset_pipeline.html&lt;/ref&gt;===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''&lt;ref&gt;http://blog.websitesframeworks.com/2013/03/web-framework-comparison-matt-raible-opinion-138/&lt;/ref&gt;==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient web framework used. GWT and GRAILS also are on par with RAILS.<br /> :* The graph depicts the five main features that any Agile Web Framework should support and these are supported by Rails thus giving both clients and developers a simple and efficient way to develop several complex web applications.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * [https://twitter.com Twitter]<br /> * [http://www.groupon.com Groupon]<br /> * [https://soundcloud.com SoundCloud]<br /> * [https://github.com/ GitHub]<br /> * [http://www.yellow.com YellowPages]<br /> * [http://www.shopify.com Shopify]<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/oss_M801_as&diff=81126 2013-10-30T19:06:37Z

<p>Asankar3: Created page with &quot;='''Dynamic style additions/removals'''= This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo brows...&quot;</p> <hr /> <div>='''Dynamic style additions/removals'''=<br /> <br /> This article is about the project M801 - Dynamic style additions/removals, which is a part of the ongoing development on the Servo browser.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Introduction''' ==<br /> ==='' What is Servo ''=== <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. By involving continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software, it focuses on empowering people to collaborate and make decisions together quickly and effectively. Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> ===''Why do we need Agile development?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, [http://en.wikipedia.org/wiki/JavaScript javascript]&lt;ref&gt;http://en.wikipedia.org/wiki/JavaScript&lt;/ref&gt;, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> <br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''&lt;ref&gt;http://en.wikipedia.org/wiki/Convention_over_configuration&lt;/ref&gt;=== <br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''&lt;ref&gt;http://guides.rubyonrails.org/getting_started.html&lt;/ref&gt;===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> '''Below is an example code for test driven development.'''<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* [http://guides.rubyonrails.org/layouts_and_rendering.html Partials] are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This [http://bundler.io/ bundler]&lt;ref&gt;http://bundler.io/&lt;/ref&gt; installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> <br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of [http://guides.rubyonrails.org/migrations.html Migration]&lt;ref&gt;http://guides.rubyonrails.org/migrations.html&lt;/ref&gt; Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as [http://coffeescript.org/ Coffeescript] can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> <br /> ===''Assets Pipeline''&lt;ref&gt;http://guides.rubyonrails.org/asset_pipeline.html&lt;/ref&gt;===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''&lt;ref&gt;http://blog.websitesframeworks.com/2013/03/web-framework-comparison-matt-raible-opinion-138/&lt;/ref&gt;==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient web framework used. GWT and GRAILS also are on par with RAILS.<br /> :* The graph depicts the five main features that any Agile Web Framework should support and these are supported by Rails thus giving both clients and developers a simple and efficient way to develop several complex web applications.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * [https://twitter.com Twitter]<br /> * [http://www.groupon.com Groupon]<br /> * [https://soundcloud.com SoundCloud]<br /> * [https://github.com/ GitHub]<br /> * [http://www.yellow.com YellowPages]<br /> * [http://www.shopify.com Shopify]<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013&diff=81090 2013-10-30T18:56:11Z

<p>Asankar3: </p> <hr /> <div>* [[ CSC/ECE 517 Fall 2012/ch1 1w23 ph ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w30 nn]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w21 w]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w01 aj]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w24 nv]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w29 rkld]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w25 aras]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w30 ps]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w19 rj]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w18 bs]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w17 pk]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w22 ss]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w12 vn]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w14 st]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w08 cc]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w10 ga ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w26 as ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w27 ma ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w13 aa ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w11 sv ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w07 d ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w20 gq ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w03 ss ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w28 nm ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w02 pp ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w6 zs ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w04 y ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w05 st ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w09 hs ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w32 av ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w48 x ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w43 av]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w46 ka]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w33 aa]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w35 sa ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w39 as ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w31 vm ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w43 sm ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w44 s ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w47 ka ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w34 fs ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch1 1w40 ao ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss fmv ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss vna ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss paa ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss mapFeeds ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss ssp ]]<br /> * [[ CSC/ECE 517 Fall 2013/ch2 0e808 nsv ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss aoa ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss cmh ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss ans ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss ssv]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E818 mra ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss SocialMediaFeeds ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E811 syn ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E804 spb ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E812 amp ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss S805 ahs ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E820 gzs ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss E816 cyy ]]<br /> * [[ CSC/ECE 517 Fall 2013/oss M801 as ]]</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/ch1_1w39_as&diff=80069 2013-10-08T03:34:12Z

<p>Asankar3: </p> <hr /> <div>== '''Agile development with Rails''' ==<br /> <br /> This article focuses on how Rails enables ’agile development<br /> practices’ and the characteristics of Rails that support specific agile methodologies.<br /> <br /> <br /> __TOC__<br /> <br /> == '''Agile development''' ==<br /> ==='' What is Agile development? ''=== <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. By involving continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software, it focuses on empowering people to collaborate and make decisions together quickly and effectively. Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> ===''Why do we need Agile development?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, [http://en.wikipedia.org/wiki/JavaScript javascript]&lt;ref&gt;http://en.wikipedia.org/wiki/JavaScript&lt;/ref&gt;, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> <br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''&lt;ref&gt;http://en.wikipedia.org/wiki/Convention_over_configuration&lt;/ref&gt;=== <br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''&lt;ref&gt;http://guides.rubyonrails.org/getting_started.html&lt;/ref&gt;===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> Below is an example code for test driven development.<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* [http://guides.rubyonrails.org/layouts_and_rendering.html Partials] are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This [http://bundler.io/ bundler]&lt;ref&gt;http://bundler.io/&lt;/ref&gt; installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> <br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of [http://guides.rubyonrails.org/migrations.html Migration]&lt;ref&gt;http://guides.rubyonrails.org/migrations.html&lt;/ref&gt; Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as [http://coffeescript.org/ Coffeescript] can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> <br /> ===''Assets Pipeline''&lt;ref&gt;http://guides.rubyonrails.org/asset_pipeline.html&lt;/ref&gt;===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''&lt;ref&gt;http://blog.websitesframeworks.com/2013/03/web-framework-comparison-matt-raible-opinion-138/&lt;/ref&gt;==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient. GWT and GRAILS also are on par with RAILS.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * [https://twitter.com Twitter]<br /> * [http://www.groupon.com Groupon]<br /> * [https://soundcloud.com SoundCloud]<br /> * [https://github.com/ GitHub]<br /> * [http://www.yellow.com YellowPages]<br /> * [http://www.shopify.com Shopify]<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/ch1_1w39_as&diff=80066 2013-10-08T03:31:07Z

<p>Asankar3: </p> <hr /> <div>== '''Agile development with Rails''' ==<br /> <br /> This article focuses on how Rails enables ’agile development<br /> practices’ and the characteristics of Rails that support specific agile methodologies.<br /> <br /> {{TOC limit}}<br /> <br /> == '''Agile development''' ==<br /> ==='' What is Agile development? ''=== <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. By involving continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software, it focuses on empowering people to collaborate and make decisions together quickly and effectively. Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> ===''Why do we need Agile development?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, [http://en.wikipedia.org/wiki/JavaScript javascript]&lt;ref&gt;http://en.wikipedia.org/wiki/JavaScript&lt;/ref&gt;, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> <br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''&lt;ref&gt;http://en.wikipedia.org/wiki/Convention_over_configuration&lt;/ref&gt;=== <br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''&lt;ref&gt;http://guides.rubyonrails.org/getting_started.html&lt;/ref&gt;===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''&lt;ref&gt;http://www.agiledata.org/essays/tdd.html&lt;/ref&gt;===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> Below is an example code for test driven development.<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* [http://guides.rubyonrails.org/layouts_and_rendering.html Partials] are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This bundler installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of [http://guides.rubyonrails.org/migrations.html Migration]&lt;ref&gt;http://guides.rubyonrails.org/migrations.html&lt;/ref&gt; Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as [http://coffeescript.org/ Coffeescript] can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> <br /> ===''Assets Pipeline''&lt;ref&gt;http://guides.rubyonrails.org/asset_pipeline.html&lt;/ref&gt;===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''&lt;ref&gt;http://blog.websitesframeworks.com/2013/03/web-framework-comparison-matt-raible-opinion-138/&lt;/ref&gt;==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient. GWT and GRAILS also are on par with RAILS.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * [https://twitter.com Twitter]<br /> * [http://www.groupon.com Groupon]<br /> * [https://soundcloud.com SoundCloud]<br /> * [https://github.com/ GitHub]<br /> * [http://www.yellow.com YellowPages]<br /> * [http://www.shopify.com Shopify]<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/ch1_1w39_as&diff=80048 2013-10-08T03:21:15Z

<p>Asankar3: </p> <hr /> <div>This article focuses on how Rails enables ’agile development<br /> practices’ and the characteristics of Rails that support specific agile methodologies.<br /> <br /> {{TOC limit}}<br /> <br /> == '''Agile development''' ==<br /> ==='' What is Agile development? ''=== <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. By involving continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software, it focuses on empowering people to collaborate and make decisions together quickly and effectively. Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> ===''Why do we need Agile development?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, [http://en.wikipedia.org/wiki/JavaScript]&lt;ref&gt;http://en.wikipedia.org/wiki/JavaScript&lt;/ref&gt;, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> <br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''&lt;ref&gt;http://en.wikipedia.org/wiki/Convention_over_configuration&lt;/ref&gt;=== <br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> Below is an example code for test driven development.<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* Partials are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This bundler installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of Migration Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as Coffeescript can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> ===''Assets Pipeline''===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient. GWT and GRAILS also are on par with RAILS.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * [https://twitter.com Twitter]<br /> * [http://www.groupon.com Groupon]<br /> * [https://soundcloud.com SoundCloud]<br /> * [https://github.com/ GitHub]<br /> * [http://www.yellow.com YellowPages]<br /> * [http://www.shopify.com Shopify]<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/ch1_1w39_as&diff=80044 2013-10-08T03:20:09Z

<p>Asankar3: </p> <hr /> <div>This article focuses on how Rails enables ’agile development<br /> practices’ and the characteristics of Rails that support specific agile methodologies.<br /> <br /> {{TOC limit}}<br /> <br /> == '''Agile development''' ==<br /> ==='' What is Agile development? ''=== <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. By involving continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software, it focuses on empowering people to collaborate and make decisions together quickly and effectively. Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> ===''Why do we need Agile development?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, javascript, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''=== &lt;ref&gt;http://en.wikipedia.org/wiki/Convention_over_configuration&lt;/ref&gt;<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> Below is an example code for test driven development.<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* Partials are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This bundler installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of Migration Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as Coffeescript can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> ===''Assets Pipeline''===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient. GWT and GRAILS also are on par with RAILS.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * [https://twitter.com Twitter]<br /> * [http://www.groupon.com Groupon]<br /> * [https://soundcloud.com SoundCloud]<br /> * [https://github.com/ GitHub]<br /> * YellowPages<br /> * Shopify<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/ch1_1w39_as&diff=80039 2013-10-08T03:17:18Z

<p>Asankar3: </p> <hr /> <div>This article focuses on how Rails enables ’agile development<br /> practices’ and the characteristics of Rails that support specific agile methodologies.<br /> <br /> {{TOC limit}}<br /> <br /> == '''Agile development''' ==<br /> ==='' What is Agile development? ''=== <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. By involving continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software, it focuses on empowering people to collaborate and make decisions together quickly and effectively. Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> ===''Why do we need Agile development?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, javascript, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|center|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> Below is an example code for test driven development.<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* Partials are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This bundler installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of Migration Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as Coffeescript can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> ===''Assets Pipeline''===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient. GWT and GRAILS also are on par with RAILS.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * Twitter<br /> * Groupon<br /> * SoundCloud<br /> * GitHub<br /> * YellowPages<br /> * Shopify<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/ch1_1w39_as&diff=80038 2013-10-08T03:17:00Z

<p>Asankar3: </p> <hr /> <div>This article focuses on how Rails enables ’agile development<br /> practices’ and the characteristics of Rails that support specific agile methodologies.<br /> <br /> {{TOC limit}}<br /> <br /> == '''Agile development''' ==<br /> ==='' What is Agile development? ''=== <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. By involving continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software, it focuses on empowering people to collaborate and make decisions together quickly and effectively. Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> ===''Why do we need Agile development?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, javascript, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|frame|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> Below is an example code for test driven development.<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* Partials are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This bundler installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of Migration Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as Coffeescript can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> ===''Assets Pipeline''===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient. GWT and GRAILS also are on par with RAILS.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * Twitter<br /> * Groupon<br /> * SoundCloud<br /> * GitHub<br /> * YellowPages<br /> * Shopify<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/ch1_1w39_as&diff=80037 2013-10-08T03:16:25Z

<p>Asankar3: </p> <hr /> <div>This article focuses on how Rails enables ’agile development<br /> practices’ and the characteristics of Rails that support specific agile methodologies.<br /> <br /> {{TOC limit}}<br /> <br /> == '''Agile development''' ==<br /> ==='' What is Agile development? ''=== <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. By involving continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software, it focuses on empowering people to collaborate and make decisions together quickly and effectively. Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> ===''Why do we need Agile development?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, javascript, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|frame|25 px|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> Below is an example code for test driven development.<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* Partials are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This bundler installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of Migration Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as Coffeescript can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> ===''Assets Pipeline''===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient. GWT and GRAILS also are on par with RAILS.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * Twitter<br /> * Groupon<br /> * SoundCloud<br /> * GitHub<br /> * YellowPages<br /> * Shopify<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/ch1_1w39_as&diff=80036 2013-10-08T03:15:54Z

<p>Asankar3: </p> <hr /> <div>This article focuses on how Rails enables ’agile development<br /> practices’ and the characteristics of Rails that support specific agile methodologies.<br /> <br /> {{TOC limit}}<br /> <br /> == '''Agile development''' ==<br /> ==='' What is Agile development? ''=== <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. By involving continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software, it focuses on empowering people to collaborate and make decisions together quickly and effectively. Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> ===''Why do we need Agile development?''===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===''Principles of agile development'' &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===''Some well known agile development methods''===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, javascript, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> [[File:tdd39.jpg|frame|alt=Test driven development| Fig 2: TDD cycle]]<br /> <br /> Below is an example code for test driven development.<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* Partials are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This bundler installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of Migration Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as Coffeescript can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> ===''Assets Pipeline''===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient. GWT and GRAILS also are on par with RAILS.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> =='''Future of Agile in Rails'''&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * Twitter<br /> * Groupon<br /> * SoundCloud<br /> * GitHub<br /> * YellowPages<br /> * Shopify<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development.<br /> <br /> =='''References'''==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=File:Tdd39.jpg&diff=80033 2013-10-08T03:14:24Z

<p>Asankar3: uploaded a new version of &amp;quot;File:Tdd39.jpg&amp;quot;</p> <hr /> <div></div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/ch1_1w39_as&diff=80025 2013-10-08T03:09:51Z

<p>Asankar3: </p> <hr /> <div>This article focuses on how Rails enables ’agile development<br /> practices’ and the characteristics of Rails that support specific agile methodologies.<br /> <br /> {{TOC limit}}<br /> <br /> == '''Agile development''' ==<br /> === What is Agile development? === <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. By involving continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software, it focuses on empowering people to collaborate and make decisions together quickly and effectively. Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> <br /> ===Why do we need Agile development?===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===Principles of agile development &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===Some well known agile development methods===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, javascript, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> Below is an example code for test driven development.<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* Partials are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This bundler installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of Migration Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as Coffeescript can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> ===''Assets Pipeline''===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient. GWT and GRAILS also are on par with RAILS.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> ==Future of Agile in Rails&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle. Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * Twitter<br /> * Groupon<br /> * SoundCloud<br /> * GitHub<br /> * YellowPages<br /> * Shopify<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development. <br /> <br /> ==References==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/ch1_1w39_as&diff=80022 2013-10-08T03:07:28Z

<p>Asankar3: </p> <hr /> <div>This article focuses on how Rails enables ’agile development<br /> practices’ and the characteristics of Rails that support specific agile methodologies.<br /> <br /> {{TOC limit}}<br /> <br /> == '''Agile development''' ==<br /> === What is Agile development? === <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. By involving continuous planning, testing, integration, and other forms of continuous evolution of both the project and the software, it focuses on empowering people to collaborate and make decisions together quickly and effectively. Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> <br /> ===Why do we need Agile development?===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===Principles of agile development &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===Some well known agile development methods===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, javascript, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> Below is an example code for test driven development.<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* Partials are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This bundler installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of Migration Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as Coffeescript can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> ===''Assets Pipeline''===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient. GWT and GRAILS also are on par with RAILS.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> ==Future of Agile in Rails&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle.<br /> <br /> Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * Twitter<br /> * Groupon<br /> * SoundCloud<br /> * GitHub<br /> * YellowPages<br /> * Shopify<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development. <br /> <br /> ==References==<br /> &lt;references/&gt;</div>

Asankar3 https://wiki.expertiza.ncsu.edu/index.php?title=CSC/ECE_517_Fall_2013/ch1_1w39_as&diff=80020 2013-10-08T03:06:18Z

<p>Asankar3: </p> <hr /> <div>This article focuses on how Rails enables ’agile development<br /> practices’ and the characteristics of Rails that support specific agile methodologies.<br /> <br /> {{TOC limit}}<br /> <br /> == '''Agile development''' ==<br /> === What is Agile development? === <br /> <br /> [http://en.wikipedia.org/wiki/Agile_software_development :Agile development]&lt;ref&gt; http://en.wikipedia.org/wiki/Agile_software_development &lt;/ref&gt; is a methodology where requirements and solutions are developed based on [http://en.wikipedia.org/wiki/Iterative_and_incremental_development iterative and incremental development] &lt;ref&gt;http://en.wikipedia.org/wiki/Iterative_and_incremental_development&lt;/ref&gt; through collaboration between self-organizing, cross-functional teams. Using agile development methodology, a high quality software can be developed by programmers in a minimal amount of time. It involves continuous planning, continuous testing, continuous integration, and other forms of continuous evolution of both the project and the software. It focuses on empowering people to collaborate and make decisions together quickly and effectively.<br /> <br /> Some of the process under agile development includes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.<br /> <br /> <br /> ===Why do we need Agile development?===<br /> <br /> :*Visibility through active customer involvement<br /> :*Flexibility/Agility - ability to accept changes<br /> :*Quality - testing integrated throughout the lifecycle<br /> :*Speedy delivery<br /> :*Customer satisfaction - feeling of a right product<br /> <br /> [[File:agl39.jpg|center|alt=Agile development| Fig 1: Agile development]]<br /> <br /> ===Principles of agile development &lt;ref&gt; http://ruby.about.com/od/rubyonrails/a/agile.htm &lt;/ref&gt; ===<br /> :*Iterative Development: Iterative development allows the clients to direct the development process in order to get the software features they want. Working software is delivered to the client at regular, short intervals. Client feedback is used to make changes to the software specifications at any stage in the development.<br /> <br /> :*Open Collaboration: Open, unrestricted communication between programmers and clients are driving force behind agile development. The programming team must work closely with the customer and also communicate freely with each other. Face to face communication is preferred over specification documents, so working in an open office with no cubicles is ideal.<br /> <br /> :*Adaptability: In agile development, changes to the software specifications are welcome even in late stages of development. Principles like Don't Repeat Yourself (DRY) are used to facilitate this. Customers gets hands-on experience with the development of the product, hence they will be able to better communicate their needs. Hence, changes in the market or company structure can be accomodated in the software at any time of the development cycle.<br /> <br /> ===Some well known agile development methods===<br /> <br /> Well-known agile software development methods include:<br /> :* [http://en.wikipedia.org/wiki/Specification_by_example Acceptance Test Driven Development (ATDD)]<br /> :* [http://en.wikipedia.org/wiki/Dynamic_systems_development_method Dynamic Systems Development Method (DSDM)]<br /> :* [http://en.wikipedia.org/wiki/Extreme_programming Extreme Programming (XP)]<br /> :* [http://en.wikipedia.org/wiki/Feature-driven_development Feature Driven Development (FDD)]<br /> :* [http://en.wikipedia.org/wiki/Lean_software_development Lean software development]<br /> :* [http://en.wikipedia.org/wiki/Scrum_(software_development) Scrum]<br /> :* [http://en.wikipedia.org/wiki/Story-driven_modeling Story-driven modeling]<br /> <br /> <br /> =='''Why Use Ruby on Rails for Agile?'''==<br /> ===''Speedy and Effective Development''===<br /> :* Rails provides a very fast mode to write code in a multitude of languages such as html, javascript, ruby, css, etc that are used to build a web-application by providing preconfigured environments and wire-framed models.<br /> :* Smoother pace of work, thus putting less pressure on the debugger when it comes to debugging.<br /> :* Without investing much resources, it can build business models and deliver functionalities, giving scope to customers to innovate and input faster.<br /> ===''Open Source''===<br /> :* The frequently used features and common functionalities can be implemented easily as they are available as Ruby gems.<br /> :* Provides developers the flexibility to customize and thus encouraging them to make large contributions.<br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> ===''Convention over Configuration''===<br /> :* By following this design paradigm, rails makes it simple for the developer as he need not specify or waste time to decide conventional aspects. <br /> :* On agreeing to implement simple and common things in a single way, it makes it easy for any new developer to work immediately on an existing project. <br /> :* This also rules out the need for explicit configuration ( except for unconventional/ customizable aspects).<br /> <br /> =='''How Rails supports Agile Methodologies'''==<br /> ===''Generators and Scaffolds''===<br /> :* The command “rails generate” uses templates to create models, controllers, views, databases, etc which helps to setup a test application.<br /> rails generate controller sample index<br /> ::The above command generates controllers sample_controller, views sample/index, assets, tests and other helpers with the route 'get' sample/index <br /> :* The scaffolding can be easily done to deploy any basic web -application, and developers can extend them to implement their functionalities. This overcomes the initial hurdle.<br /> rails generate scaffold Exam course:string score:float<br /> ::It generates all the required directories for an MVC application for a model Exam and also creates db migration CreateExams<br /> <br /> ===''Ready Setup for Multi-environment''===<br /> :* Rails application provides development, production and testing environments with built-in configurations setup and thus is a huge time saver for an application which is required to be deployed in multiple environments.<br /> :* The built-in rails web-server has the development environment as the default environment. <br /> :* Simple deployment allows developers to have face-face client meetings and thus make instantaneous changes based on the client requirements.<br /> <br /> '''Built in configuration of DB in database.yml in development environment'''<br /> development:<br /> adapter: sqlite3<br /> database: db/development.sqlite3<br /> pool: 5<br /> timeout: 5000<br /> <br /> ===''Test-Driven Development''===<br /> :* Built in mocking and stubbing frameworks are available which assists “how to write code”. This follows a red, green and refactor which is an important aspect of agile development.<br /> :* RSpec is one of the famous testing framework tools used with rails. <br /> :* Other testing tools can also be swapped in.<br /> <br /> Below is an example code for test driven development.<br /> <br /> describe &quot;Static pages&quot; do<br /> describe &quot;Home page&quot; do<br /> before { visit root_path }<br /> it &quot;should have the words 'Backchannel App' in it&quot; do<br /> expect(page).to have_content('Back Channel App')<br /> end<br /> end<br /> <br /> ===''Don’t Repeat Yourself (DRY)''===<br /> :* Repeated code is written in helpers and libraries, making a single destination and thus updations become simpler by updating at just one place.<br /> :* Partials are a way of rendering repeated HTML code. Rails understand a file which starts with an underscore, say, _partial.html as a partial to be included in the shared html file which renders it.<br /> '''Using partials''':<br /> :'''new.html.erb'''<br /> <br /> New Venture<br /> &lt;%= error_messages_for :venture%&gt;<br /> &lt;%= render partial: &quot;form&quot;, locals: {venture: @venture} %&gt;<br /> <br /> :'''_form.html.erb'''<br /> &lt;%= form_for(venture) do |f| %&gt; <br /> Venture name<br /> &lt;%= f.text_field :name %&gt;<br /> &lt;%= f.submit %&gt; <br /> &lt;% end %&gt;<br /> <br /> ===''Dependency Management''===<br /> :* Rails acts more than a web framework by providing the necessary utility and support tools and adding dependencies to individual projects in a jiffy using the “bundler”. <br /> :* This bundler installs all the relevant gem files and also can be updated when more dependencies are added. No need to search for packages or jars.<br /> ===''Easy Migration''===<br /> :* Rails helps you to keep easy track of database changes with the help of Migration Objects. It gives the flexibility to rollback and update.<br /> :* It also allows you to maintain various versions of database for the multi-environment. On running rake db::migrate, the desired database is migrated and deployed with the working rails server.<br /> :* New technologies such as Coffeescript can also be easily embedded by installing the relevant gems thus adapting to the changing technology.<br /> ===''Assets Pipeline''===<br /> :* The assets pipeline is a new feature embedded in rails ( which is now extracted into sprockets-rails gem), concatenates and compresses javascript and css files.<br /> :* This renders a web page with reduced number of requests from the browser as files are grouped and whitespaces are trimmed.<br /> :* Precompiled files can also be attached.<br /> <br /> =='''Comparison of Rails with other Agile Web Frameworks'''==<br /> :* This graph shows some of Rabies matrix weights to compare rails with other agile web frameworks. Among the ones compared, Rails is one of the most favourite and production efficient. GWT and GRAILS also are on par with RAILS.<br /> <br /> [[File:Stats.JPG|25 px|upright=0.85|center|frame|alt=Puzzle globe logo|center| Fig 3:Comparison of Agile Web Frameworks]]<br /> '''''Weights Explained'''''<br /> :*''Components'': Reusable components accelerate development<br /> :*''Templating'': Rating based on the number of UI templating options are available for the framework<br /> :*''Plugins and Add-ons'': Rating based on if they framework has a plugin architecture and how many plugins are available<br /> :*''Scalability'': Rating based on how much the framework relies on session state for functionality<br /> :*''REST Support'': Does the framework have the ability to produce JSON and XML instead of simply returning HTML? Can it consume JSON and XML as well?<br /> :*''Degree of Risk'': This rating is mostly for businesses. If the framework is new, there’s inherently some risk in choosing it for your applications<br /> :*''Testing'': Tools for testing allow to find errors faster<br /> <br /> ==Future of Agile in Rails&lt;ref&gt; http://www.richappsconsulting.com/blog/blog-detail/agile-web-development-with-rails-an-overview/ &lt;/ref&gt;==<br /> Ruby on Rails is a framework that makes it easier to develop, deploy and maintain web applications. Soon after its initial release, Rails went from being an unfamiliar tool to being a wide-reaching phenomenon. It has become the framework of choice for the implementation of a wide range of Web 2.0 applications as it is both simple and subtle.<br /> <br /> Rails is often utilized by web developers for its suitability for short, client-driven projects. Many entrepreneurs and businesses have chosen Ruby on Rails to create their web application. Here are few well known web services that are run on Ruby on Rails:<br /> <br /> * Twitter<br /> * Groupon<br /> * SoundCloud<br /> * GitHub<br /> * YellowPages<br /> * Shopify<br /> <br /> Due to its simple nature and easy to use features as well as the speed of project completion, Rails is an ideal platform for Agile development practices. Keeping in view its accordance with the Agile Manifesto, it is not hard to predict that Rails will be the future of Agile development. <br /> <br /> ==References==<br /> &lt;references/&gt;</div>

Asankar3