ramaze 0.3.9.1 → 2008.06

data/doc/INSTALL

@@ -1,34 +1,92 @@
-= Installating Ramaze
-
 * via RubyGems
 
-  The simplest way of installing Ramaze is via 
+  The simplest way of installing Ramaze is via the gem.
+
+  [Rubygems](http://rubygems.org) is the package manager for ruby apps and
+  libraries and provides you with the last tagged version of Ramaze.
 
-    $ gem install ramaze
+      $ gem install ramaze
 
-  in case you have RubyGems installed.
-  (this will work as soon as I have registered on RubyForge ;)
+  Versions are made as we see fit and get an announcment out (usually that's
+  the major obstacle as there is a lot to announce).
 
-* via install.rb
+  If you want to install the nightly gem of Ramaze you can do this with:
 
-  Ramaze provides a basic install.rb that should take care of the installation
-  you can use it like 
+      $ gem install ramaze --source=http://gem.ramaze.net/
 
-    $ ruby install.rb
+  We also use the gem building process on github, which locates gems at
+  http://gems.github.com - so you can get a version from there as well:
 
-  you may need root-privileges to do
-  that, depending on what options you provide.
-  (please note that I haven't tested the install.rb extensively yet, so if you
-  find some quirks, please send me patches or a simple note)
+      $ gem install manveru-ramaze --source=http://gems.github.com/
 
-* via darcs
+* via git
 
   To get the latest and sweetest, you can just pull from the repository and run
   Ramaze that way.
 
-    $ darcs get --partial http://manveru.mine.nu/ramaze
+      $ git clone git://github.com/manveru/ramaze.git
 
-  Please read the man page or `darcs help` for more information about updating
+  Please read the `man git` or `git help` for more information about updating
   and creating your own patches.
-  This is at the moment the premier way to use Ramaze, since it is the way I use
-  it.
+  This is at the moment the premier way to use Ramaze, since it is the way I
+  use it.
+
+  Some hints for the usage of Git.
+
+  * use `require 'ramaze'` from everywhere
+
+    Simply add the path to your repository to the RUBYLIB environment variable.
+    If you are using bash you can simply put following line into your .bashrc:
+
+        $ export RUBYLIB="$HOME/path/to/repo/lib/"
+
+    Of course you should put the real path instead, you can also add multiple
+    paths, or create your personal `site_ruby`:
+
+        $ export RUBYLIB="$HOME/ruby/ramaze/lib:$HOME/.site_ruby:$HOME/ruby/bacon/lib"
+
+  * use `require 'ramaze'` systemwide from everywhere
+
+    add a file to your `site_ruby` directory named 'ramaze.rb'
+    the content should be: `require '/path/to/git/repo/ramaze/lib/ramaze'`
+
+  * Pull the latest version
+
+        $ git pull
+
+  * Reset the repo to original state (if you screw up something)
+
+        $ git reset --hard # resets the whole repo
+
+  * Revert changes to (for example) lib/ramaze.rb only
+
+        $ git checkout master lib/ramaze.rb
+
+  * Add and commit all changes.
+
+        $ git commit -a
+
+  * Adding only specific changes.
+
+        # Add hunks you want to commit to the staging area (index)
+        $ git add -p
+
+  * Commit the changes into the history of your repository
+
+        # Create a commit from the hunks added
+        $ git commit
+
+  * output your patches into a bundle ready to be mailed (compress it before
+    sending to make sure it arrives in the way you sent it)
+
+    At the end of this process you will have a tar.bz2 for all your changes
+    that you can mail to ramaze@googlegroups.com
+
+        # make sure you are on latest revision to avoid conflicts
+        $ git pull
+
+        # create 00xx-blah.patch files against the remote repo
+        $ git format-patch origin/HEAD
+
+        # From here on you can use either git-send-email or go the manual route
+        $ tar -cjf ramaze_bundle.tar.bz2 *.patch

data/doc/LEGAL

@@ -20,7 +20,3 @@ lib/ramaze/spec/helper/simple_http.rb
 lib/ramaze/template/xslt.rb
   License: Ruby
   Author: Stephan Maka
-
-lib/vendor/bacon.rb
-  License: MIT
-  Author: Christian Neukirchen

data/doc/meta/announcement.txt

@@ -1,4 +1,4 @@
-This time we are proud to announce Version 0.3.5 of Ramaze, the light and
+This time we are proud to announce Version 2008.06 of Ramaze, the light and
 modular open source web framework.
 
 This release features a lot of work directly from our community and we are
@@ -10,11 +10,15 @@ implementation and usage. Ramaze is under development by a growing community
 and in production use at companies.
 
 
-Home page:   http://ramaze.net
-Screencasts: http://ramaze.net/screencasts
+Home page:    http://ramaze.net
+Screencasts:  http://ramaze.net/screencasts
 
-View source: http://source.ramaze.net
-Darcsweb:    http://darcs.ramaze.net
+View source:  http://source.ramaze.net
+Github:       http://github.com/manveru/ramaze
+
+Nightly gems:    http://gems.ramaze.net
+Git clone:       git://github.com/manveru/ramaze
+Current tarball: http://github.com/manveru/ramaze/tarball/master
 
 IRC: #ramaze on irc.freenode.net
 
@@ -32,59 +36,44 @@ Simple example:
   Ramaze.start
 
 
-Special (alphabetic) thanks go to:
+This is a special release, and the first of the upcoming new series of monthly releases.
+As you may have noticed, Ramaze has changed to a date base versioning system,
+although this means that people who have waited for a 1.0 for the past years
+may be disappointed it provides much larger flexibility in detecting new
+versions and comparing them with nightly builds.
+
+Another change is the switch from darcs to git and moving our primary
+repository to github. There have been serious performance issues regarding
+darcs as Ramaze gathered a longer history, using git allows us to move on at a
+faster pace again.
 
-  Aman 'tmm1' Gupta         - patches and support
-  Carlo Zottmann            - first patch!
-  Chris 'celldee' Duncan    - first patch!
-  Gabriele 'riffraff' Renzi - patches for file dispatcher
-  jeedee                    - new Ramaze logo
-  Jonathan 'Kashia' Buch    - patches and support
-  Keita Yamaguchi           - first patch!
-  Pistos                    - lots of friendly support
-  skaar                     - first patch!
-
-
-Selected summary of the 62 patches from 0.3.0 to 0.3.5:
-
-  Core
-    - Ramaze::Contrib::Route made available by default as Ramaze::Route
-      (backwards compatibility retained)
-    - Support added for ETag and If-Modified-Since in Dispatcher::File
-    - Adapter for LiteSpeed webserver added
-    - Added ability to set default session cookie options using Session::COOKIE
-    - Support added for Content-Language based localization and gettext
-
-  Templates
-    - Support added for passing in locals to render_template
-    - Added support for symbol argument to template_root
-    - render_template no longer requires template extensions
-    - Dots allowed in template extensions (template.html.erb)
-
-  Templating Engines
-    - Builder templating engine added to produce XML
-    - RedCloth templating engine added
-    - Amrita2 templating engine updated to latest release
-
-  Helpers
-    - Simple EmailHelper added
-    - IdentityHelper updated for latest ruby-openid
-    - MarukuHelper added
-    - AuthHelper cleaned up
-    - LinkHelper improved: A(), R(), Rs() and breadcrumbs
-
-  Examples
-    - All examples were standardized to include rubygems
-    - Simple file upload example added
-    - Search and diff functionality added to Rapaste
-
-  Misc
-    - Read and read/write issues fixed in Ramaze::Store
-    - Fix applied for running Ramaze apps within IDEs on Windows
+Please regard this release as a major step from the previous one, over 450
+patches have been applied and there were changes in the internal API.
+
+We are unable to nicely summarize these changes, so this release will not have
+a list of the most important ones, if you are concerned about a specific area
+feel free to ask on the Mailing list or stop by on IRC.
+
+Special (alphabetic) thanks go to:
 
+  Aman 'tmm1' Gupta         - Tons of patches, support
+  andy                      - Cleanup
+  Ara T. Howard             - Tagz templating engine
+  Clive Crous               - Patches, cleanup
+  evaryont                  - Patches for identity helper
+  James Tucker              - OSX compatibility, cleanup and fixes
+  Jonathan 'Kashia' Buch    - Patches, support and the first ramaze paper
+  Keita Yamaguchi           - Much work on the benchmark suite
+  Leo Borisenko             - Fix for SourceReload on windows
+  Pistos                    - Mathetes, patches and lots of friendly support
+  Riku Räisäenen            - Patches for scaffolding example
+  Ryan Grove                - Various fixes and patches
+  Sam Carr                  - Patches and action matching speedup
+  Thomas Leitner            - Patches for identity helper
+  Wang Jinjing              - patches, 1.9/1.8.7 compatibility
 
 A complete Changelog is available at
-http://darcs.ramaze.net/ramaze/doc/CHANGELOG
+http://github.com/manveru/ramaze/tree/master/doc/CHANGELOG?raw=true
 
 
 Known issues:

data/doc/meta/configuration.txt

@@ -18,9 +18,10 @@ Global with Ramaze so it is written Ramaze::Global.
 
 #### Basic assignment:
 
-  Global.spawn = 10
+  Global.port = 10
 
-if you do that before calling Ramaze::start Ramaze will spawn the given number of servers.
+if you do that before calling Ramaze::start Ramaze will choose the given number
+as port.
 
 
 #### Multiple assignment:

data/doc/readme_chunks/examples.txt

@@ -29,10 +29,10 @@ Examples include:
   Not yet fully functional, but coming along.
 
 * examples/whywiki
-  A basic examples of a minimalistic application, based on the Wiki of _why in
+  A basic examples of a minimalistic application, based on the Wiki of \_why in
   his camping-framework.
 
 * examples/templates
   examples of real usage of the templating-engines. Tries to implement the same
-  functionality in each template_*.rb file using a different engine.
+  functionality in each `template_*.rb` file using a different engine.
 

data/doc/readme_chunks/installing.txt

@@ -1,46 +1,92 @@
 * via RubyGems
 
-  The simplest way of installing Ramaze is via 
+  The simplest way of installing Ramaze is via the gem.
 
-    $ gem install ramaze
+  [Rubygems](http://rubygems.org) is the package manager for ruby apps and
+  libraries and provides you with the last tagged version of Ramaze.
 
-  in case you have RubyGems installed.
+      $ gem install ramaze
 
+  Versions are made as we see fit and get an announcment out (usually that's
+  the major obstacle as there is a lot to announce).
 
-* via darcs
+  If you want to install the nightly gem of Ramaze you can do this with:
+
+      $ gem install ramaze --source=http://gem.ramaze.net/
+
+  We also use the gem building process on github, which locates gems at
+  http://gems.github.com - so you can get a version from there as well:
+
+      $ gem install manveru-ramaze --source=http://gems.github.com/
+
+* via git
 
   To get the latest and sweetest, you can just pull from the repository and run
   Ramaze that way.
 
-    $ darcs get --partial http://darcs.ramaze.net/ramaze
+      $ git clone git://github.com/manveru/ramaze.git
 
-  Please read the man page or `darcs help` for more information about updating
+  Please read the `man git` or `git help` for more information about updating
   and creating your own patches.
-  This is at the moment the premier way to use Ramaze, since it is the way I use
-  it.
+  This is at the moment the premier way to use Ramaze, since it is the way I
+  use it.
+
+  Some hints for the usage of Git.
+
+  * use `require 'ramaze'` from everywhere
+
+    Simply add the path to your repository to the RUBYLIB environment variable.
+    If you are using bash you can simply put following line into your .bashrc:
+
+        $ export RUBYLIB="$HOME/path/to/repo/lib/"
+
+    Of course you should put the real path instead, you can also add multiple
+    paths, or create your personal `site_ruby`:
+
+        $ export RUBYLIB="$HOME/ruby/ramaze/lib:$HOME/.site_ruby:$HOME/ruby/bacon/lib"
+
+  * use `require 'ramaze'` systemwide from everywhere
+
+    add a file to your `site_ruby` directory named 'ramaze.rb'
+    the content should be: `require '/path/to/git/repo/ramaze/lib/ramaze'`
+
+  * Pull the latest version
+
+        $ git pull
+
+  * Reset the repo to original state (if you screw up something)
+
+        $ git reset --hard # resets the whole repo
+
+  * Revert changes to (for example) lib/ramaze.rb only
 
-  Some hints for the usage of Darcs.
+        $ git checkout master lib/ramaze.rb
 
-  * use require 'ramaze' from everywhere
+  * Add and commit all changes.
 
-    add a file to your site_ruby named 'ramaze.rb'
-    the content should be: "require '/path/to/darcs/repo/ramaze/lib/ramaze'"
+        $ git commit -a
 
-  * get the latest version (from inside the ramaze-directory)
+  * Adding only specific changes.
 
-    $ darcs pull
+        # Add hunks you want to commit to the staging area (index)
+        $ git add -p
 
-  * record a patch
+  * Commit the changes into the history of your repository
 
-    $ darcs record
+        # Create a commit from the hunks added
+        $ git commit
 
   * output your patches into a bundle ready to be mailed (compress it before
     sending to make sure it arrives in the way you sent it)
 
-    $ darcs send -o ramaze_bundle
-    $ gzip -c ramaze_bundle > ramaze_bundle.gz
+    At the end of this process you will have a tar.bz2 for all your changes
+    that you can mail to ramaze@googlegroups.com
 
+        # make sure you are on latest revision to avoid conflicts
+        $ git pull
 
-* via install.rb
+        # create 00xx-blah.patch files against the remote repo
+        $ git format-patch origin/HEAD
 
-  Support for install.rb has been canceled and the file removed.
+        # From here on you can use either git-send-email or go the manual route
+        $ tar -cjf ramaze_bundle.tar.bz2 *.patch

data/doc/tutorial/todolist.html

@@ -1,128 +1,86 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-  <html>
-    <head>
-      <title>Ramaze Tutorial: Todolist</title>
-      <style>
-        body {
-          background: #eee;
-        }
-        code {
-          background: #ddd;
-        }
-        pre code {
-          background: #ddd;
-          width: 70%;
-          display: block;
-          margin: 1em;
-          padding: 0.7em;
-          overflow: auto;
-        }
-      </style>
-      <meta content="text/html; charset=UTF-8" http-equiv="content-type" />
-    </head>
-    <body>
-      
-  <h1>To-do List Tutorial</h1>
-
-<div class="menu">
-  <h3>Table of Contents</h3>
-  <li>
-    <ol><a href="#Step_Zero,_Introduction">Step Zero, Introduction</a></ol>
-    <ol><a href="#First_Step,_Create">First Step, Create</a></ol>
-    <ol><a href="#Second_Step,_M,_like_Model">Second Step, M, like Model</a></ol>
-    <ol><a href="#Third_Step,_V,_like_View">Third Step, V, like View</a></ol>
-    <ol><a href="#Fourth_Step,_C,_like_Controller">Fourth Step, C, like Controller</a></ol>
-    <ol><a href="#Fifth_Step,_getting_dynamic">Fifth Step, getting dynamic</a></ol>
-    <ol><a href="#Sixth_Step,_open_and_close_tasks">Sixth Step, open and close tasks</a></ol>
-    <ol><a href="#Seventh_Step,_delete_tasks">Seventh Step, delete tasks</a></ol>
-    <ol><a href="#Eighth_Step,_Elements">Eighth Step, Elements</a></ol>
-    <ol><a href="#Ninth_Step,_Prettify">Ninth Step, Prettify</a></ol>
-    <ol><a href="#Tenth_Step,_Configuration">Tenth Step, Configuration</a></ol>
-    <ol><a href="#Eleventh_Step,_Refactor_with_AspectHelper">Eleventh Step, Refactor with AspectHelper</a></ol>
-    <ol><a href="#Twelfth_Step,_Validation_and_Errors">Twelfth Step, Validation and Errors</a></ol>
-  </li>
-</div>
-
-
-<a name="Step_Zero,_Introduction"><h2>Step Zero, Introduction</h2></a>
-
-<p>Welcome to our official tutorial, the mandatory to-do list.
-I'm writing this while doing the steps to assure it will work for you.</p>
-
-<p>The tutorial assumes that you have Ramaze installed already. The easiest way to
-do that is <code>gem install ramaze</code>, for other ways of installation please see the
-documentation at http://ramaze.rubyforge.org</p>
-
-<p>Should you encounter any problems while doing this tutorial, this might either
-be because Ramaze changed (which happens very often while it is still young)
-or I actually made some mistake while writing it.</p>
-
-<p>In either case it would make me (and all other poor fellows who happen to try
-this tutorial) very happy if you could spare some time and report the issue
-either on the Bug tracker at http://rubyforge.org/projects/ramaze or just
-drop by on IRC ( irc.freenode.org channel: #ramaze ).</p>
-
-<p>There is also a Mailing list available where you can keep yourself updated on
-what is going on with little effort, it is also located on the project-page at
-RubyForge.</p>
-
-<p>Additionally, we now have added tests for the resulting application that you
-can find in spec/examples/todolist.rb</p>
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1 plus MathML 2.0 plus SVG 1.1//EN" "http://www.w3.org/2002/04/xhtml-math-svg/xhtml-math-svg.dtd">
+<html xml:lang="en" xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/1999/xhtml">
+<head><meta content="application/xhtml+xml;charset=utf-8" http-equiv="Content-type" /><title>The official Ramaze todolist tutorial</title><style type="text/css">
+      .ruby .normal {}
+.ruby .comment { color: #005; font-style: italic; }
+.ruby .keyword { color: #A00; font-weight: bold; }
+.ruby .method { color: #077; }
+.ruby .class { color: #074; }
+.ruby .module { color: #050; }
+.ruby .punct { color: #447; font-weight: bold; }
+.ruby .symbol { color: #099; }
+.ruby .string { color: #944; background: #FFE; }
+.ruby .char { color: #F07; }
+.ruby .ident { color: #004; }
+.ruby .constant { color: #07F; }
+.ruby .regex { color: #B66; background: #FEF; }
+.ruby .number { color: #F99; }
+.ruby .attribute { color: #7BB; }
+.ruby .global { color: #7FB; }
+.ruby .expr { color: #227; }
+.ruby .escape { color: #277; }
+
+    </style></head>
+<body>
+<h1 id="todo_list_tutorial">To-do List Tutorial</h1>
+<div class="maruku_toc"><ul style="list-style: none;"><li><a href="#step_zero_introduction">Step Zero, Introduction</a></li><li><a href="#first_step_create">First Step, Create</a></li><li><a href="#second_step_m_like_model">Second Step, M, like Model</a></li><li><a href="#third_step_v_like_view">Third Step, V, like View</a></li><li><a href="#fourth_step_c_like_controller">Fourth Step, C, like Controller</a></li><li><a href="#fifth_step_getting_dynamic">Fifth Step, getting dynamic</a></li><li><a href="#sixth_step_open_and_close_tasks">Sixth Step, open and close tasks</a></li><li><a href="#seventh_step_delete_tasks">Seventh Step, delete tasks</a></li><li><a href="#eighth_step_elements">Eighth Step, Elements</a></li><li><a href="#ninth_step_prettify">Ninth Step, Prettify</a></li><li><a href="#tenth_step_configuration">Tenth Step, Configuration</a></li><li><a href="#eleventh_step_refactor_with_aspecthelper">Eleventh Step, Refactor with AspectHelper</a></li><li><a href="#twelfth_step_validation_and_errors">Twelfth Step, Validation and Errors</a></li></ul></div>
+<h2 id="step_zero_introduction">Step Zero, Introduction</h2>
+
+<p>Welcome to our official tutorial, the mandatory to-do list. I&#8217;m writing this while doing the steps to assure it will work for you.</p>
+
+<p>The tutorial assumes that you have Ramaze installed already. The easiest way to do that is <code>gem install ramaze</code>, for other ways of installation please see the documentation at http://ramaze.rubyforge.org</p>
+
+<p>Should you encounter any problems while doing this tutorial, this might either be because Ramaze changed (which happens very often while it is still young) or I actually made some mistake while writing it.</p>
+
+<p>In either case it would make me (and all other poor fellows who happen to try this tutorial) very happy if you could spare some time and report the issue either on the Bug tracker at http://rubyforge.org/projects/ramaze or just drop by on IRC ( irc.freenode.org channel: #ramaze ).</p>
+
+<p>There is also a Mailing list available where you can keep yourself updated on what is going on with little effort, it is also located on the project-page at RubyForge.</p>
+
+<p>Additionally, we now have added tests for the resulting application that you can find in spec/examples/todolist.rb</p>
 
 <p>Date of last update: Thu Jan 31 04:37:16 JST 2008</p>
 
-<p>Thanks in advance.
-The author of the tutorial, Michael 'manveru' Fellinger</p>
+<p>Thanks in advance. The author of the tutorial, Michael &#8216;manveru&#8217; Fellinger</p>
 
-<a name="First_Step,_Create"><h2>First Step, Create</h2></a>
+<h2 id="first_step_create">First Step, Create</h2>
 
-<p>We are using <code>ramaze --create todolist</code> to create a new application.
-Ramaze will then create the directory and fill it with a skeleton of a quite
-sophisticated hello-world example out of which we will create the actual
-to-do list.</p>
+<p>We are using <code>ramaze --create todolist</code> to create a new application. Ramaze will then create the directory and fill it with a skeleton of a quite sophisticated hello-world example out of which we will create the actual to-do list.</p>
 
 <p>So run:</p>
 
-<pre><code>$ ramaze --create todolist
-</code></pre>
+<pre><code>$ ramaze --create todolist</code></pre>
 
 <p>done.</p>
 
-<a name="Second_Step,_M,_like_Model"><h2>Second Step, M, like Model</h2></a>
+<h2 id="second_step_m_like_model">Second Step, M, like Model</h2>
 
-<p>Ramaze comes at the moment only with a simple wrapper of the YAML::Store.
-So we are going to base this on the tools available, you can just do the same
-with your ORM or database-library of choice.</p>
+<p>Ramaze comes at the moment only with a simple wrapper of the YAML::Store. So we are going to base this on the tools available, you can just do the same with your ORM or database-library of choice.</p>
 
 <p>So first, create a <code>model/todolist.rb</code> for our application:</p>
 
-<pre><code>require 'ramaze/store/default'
-TodoList = Ramaze::Store::Default.new('todolist.yaml')
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="ident">require</span> <span class="punct">&#39;</span><span class="string">ramaze/store/default</span><span class="punct">&#39;</span>
+<span class="constant">TodoList</span> <span class="punct">=</span> <span class="constant">Ramaze</span><span class="punct">::</span><span class="constant">Store</span><span class="punct">::</span><span class="constant">Default</span><span class="punct">.</span><span class="ident">new</span><span class="punct">(&#39;</span><span class="string">todolist.yaml</span><span class="punct">&#39;)</span></code></pre>
 
-<p>Let's add some items as well to have a base to start from.</p>
+<p>Let&#8217;s add some items as well to have a base to start from.</p>
 
-<pre><code>{ 'Laundry'     =&gt; {:done =&gt; false},
-  'Wash dishes' =&gt; {:done =&gt; false},
-}.each do |title, value|
-  TodoList[title] = value
-end
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="punct">{</span> <span class="punct">&#39;</span><span class="string">Laundry</span><span class="punct">&#39;</span>     <span class="punct">=&gt;</span> <span class="punct">{</span><span class="symbol">:done</span> <span class="punct">=&gt;</span> <span class="constant">false</span><span class="punct">},</span>
+  <span class="punct">&#39;</span><span class="string">Wash dishes</span><span class="punct">&#39;</span> <span class="punct">=&gt;</span> <span class="punct">{</span><span class="symbol">:done</span> <span class="punct">=&gt;</span> <span class="constant">false</span><span class="punct">},</span>
+<span class="punct">}.</span><span class="ident">each</span> <span class="keyword">do</span> <span class="punct">|</span><span class="ident">title</span><span class="punct">,</span> <span class="ident">value</span><span class="punct">|</span>
+  <span class="constant">TodoList</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span> <span class="punct">=</span> <span class="ident">value</span>
+<span class="keyword">end</span></code></pre>
 
-<a name="Third_Step,_V,_like_View"><h2>Third Step, V, like View</h2></a>
+<h2 id="third_step_v_like_view">Third Step, V, like View</h2>
 
-<p>Now let's get our hands dirty and just edit the templates for our to-do list.</p>
+<p>Now let&#8217;s get our hands dirty and just edit the templates for our to-do list.</p>
 
-<p>Start with editing <code>view/index.xhtml</code>, it is using the default templating
-of Ramaze, called Ezamar.</p>
+<p>Start with editing <code>view/index.xhtml</code>, it is using the default templating of Ramaze, called Ezamar.</p>
 
 <p>The index.xhtml currently contains a default welcome page, remove the contents.</p>
 
-<p>Let's put some things in there, I'll explain the syntax as we go, it's quite
-simple.</p>
+<p>Let&#8217;s put some things in there, I&#8217;ll explain the syntax as we go, it&#8217;s quite simple.</p>
 
-<pre><code>&lt;html&gt;
+<pre><code class="nagoro" lang="nagoro">&lt;html&gt;
   &lt;head&gt;
     &lt;title&gt;TodoList&lt;/title&gt;
   &lt;/head&gt;
@@ -131,139 +89,111 @@ simple.</p>
     &lt;ul&gt;
       &lt;?r
         TodoList.each do |title, value|
-          status = value[:done] ? 'done' : 'not done'
+          status = value[:done] ? &#39;done&#39; : &#39;not done&#39;
         ?&gt;
         &lt;li&gt;#{c title}: #{status}&lt;/li&gt;
       &lt;?r end ?&gt;
     &lt;/ul&gt;
   &lt;/body&gt;
-&lt;/html&gt;
-</code></pre>
+&lt;/html&gt;</code></pre>
 
-<p>I will assume that you are familiar with basic Ruby already, so we will
-concentrate on the things new here.</p>
+<p>I will assume that you are familiar with basic Ruby already, so we will concentrate on the things new here.</p>
 
-<p><code>&lt;?r ?&gt;</code> defines an area of ruby-code. Later, when the template is transformed
-into pure Ruby it will be evaluated. We iterate over the TodoList model and
-pass the title and value into a block. In that block we can just get the values
-of title and status (which we define based on the value) displayed on the
-page.</p>
+<p><code>&lt;?r ?&gt;</code> defines an area of ruby-code. Later, when the template is transformed into pure Ruby it will be evaluated. We iterate over the TodoList model and pass the title and value into a block. In that block we can just get the values of title and status (which we define based on the value) displayed on the page.</p>
 
-<p>The whole Template would expand to something like this (only showing the
-interesting part)</p>
+<p>The whole Template would expand to something like this (only showing the interesting part)</p>
 
-<pre><code>&lt;ul&gt;
+<pre><code class="nagoro" lang="nagoro">&lt;ul&gt;
   &lt;li&gt;Laundry: not done&lt;/li&gt;
   &lt;li&gt;Wash dishes: not done&lt;/li&gt;
-&lt;/ul&gt;
-</code></pre>
+&lt;/ul&gt;</code></pre>
 
-<p>That wasn't too bad, huh?</p>
+<p>That wasn&#8217;t too bad, huh?</p>
 
-<p>Now, so we can get our instant pleasure of seeing the result of our (hard) work,
-let's see how to start ramaze.</p>
+<p>Now, so we can get our instant pleasure of seeing the result of our (hard) work, let&#8217;s see how to start ramaze.</p>
 
 <p>In the <code>todolist</code> directory run <code>ramaze</code>.</p>
 
-<p>This will start an instance of Ramaze and run your application on it. You can
-now access it by browsing to http://localhost:7000/</p>
+<p>This will start an instance of Ramaze and run your application on it. You can now access it by browsing to http://localhost:7000/</p>
 
-<p>7000 is the default-port Ramaze will run on, to change it you can just run
-<code>ramaze -p 7070</code> or similar. Also be sure to look at the output of
-<code>ramaze --help</code> to see some other options.</p>
+<p>7000 is the default-port Ramaze will run on, to change it you can just run <code>ramaze -p 7070</code> or similar. Also be sure to look at the output of <code>ramaze --help</code> to see some other options.</p>
 
-<a name="Fourth_Step,_C,_like_Controller"><h2>Fourth Step, C, like Controller</h2></a>
+<h2 id="fourth_step_c_like_controller">Fourth Step, C, like Controller</h2>
 
 <p>The last part of the MVC-paradigm is the Controller.</p>
 
-<p>Wouldn't it be nice to have a way to add and remove items on our to-do list?
-Editing the model every time would be quite tiresome and limited.</p>
+<p>Wouldn&#8217;t it be nice to have a way to add and remove items on our to-do list? Editing the model every time would be quite tiresome and limited.</p>
 
-<p>Well, come along, I'll introduce you to Controller.</p>
+<p>Well, come along, I&#8217;ll introduce you to Controller.</p>
 
-<p>In the way MVC is structured, the Controller provides the data in a nice way
-for the View, removing all of the data-preparation and most of the logic from
-the templates. This makes it firstly simple to change the front end of your
-application and secondly provides excellent ways of changing the complete
-Structure of the Model or View independent from each other.</p>
+<p>In the way MVC is structured, the Controller provides the data in a nice way for the View, removing all of the data-preparation and most of the logic from the templates. This makes it firstly simple to change the front end of your application and secondly provides excellent ways of changing the complete Structure of the Model or View independent from each other.</p>
 
-<p>OK, enough of the theory, you will see the benefits in an instant. Go on and
-edit the file <code>controller/main.rb</code>.</p>
+<p>OK, enough of the theory, you will see the benefits in an instant. Go on and edit the file <code>controller/main.rb</code>.</p>
 
 <p>The contents of it are like following:</p>
 
-<pre><code>class MainController &lt; Controller
-  def index
-    @welcome = "Welcome to Ramaze!"
-  end
+<pre><code class="ruby" lang="ruby"><span class="keyword">class </span><span class="class">MainController</span> <span class="punct">&lt;</span> <span class="constant">Controller</span>
+  <span class="keyword">def </span><span class="method">index</span>
+    <span class="attribute">@welcome</span> <span class="punct">=</span> <span class="punct">&quot;</span><span class="string">Welcome to Ramaze!</span><span class="punct">&quot;</span>
+  <span class="keyword">end</span>
 
-  def notemplate
-    "there is no template associated with this action"
-  end
-end
-</code></pre>
+  <span class="keyword">def </span><span class="method">notemplate</span>
+    <span class="punct">&quot;</span><span class="string">there is no template associated with this action</span><span class="punct">&quot;</span>
+  <span class="keyword">end</span>
+<span class="keyword">end</span></code></pre>
 
-<p>The only methods right now are <code>#index</code> and <code>#notemplate</code>.
-The relationship between the methods on the controller and the templates is
-1:1, so the method <code>#index</code> is combined with the template <code>index.xhtml</code>. This
-combination is called an <code>action</code>.</p>
+<p>The only methods right now are <code>#index</code> and <code>#notemplate</code>. The relationship between the methods on the controller and the templates is 1:1, so the method <code>#index</code> is combined with the template <code>index.xhtml</code>. This combination is called an <code>action</code>.</p>
 
-<p>Let's get back to editing and change the method <code>#index</code> to this:</p>
+<p>Let&#8217;s get back to editing and change the method <code>#index</code> to this:</p>
 
-<pre><code>def index
-  @tasks = TodoList.original
-  @tasks.each do |title, value|
-    status = value[:done] ? 'done' : 'not done'
-    @tasks[title] = status
-  end
-end
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="keyword">def </span><span class="method">index</span>
+  <span class="attribute">@tasks</span> <span class="punct">=</span> <span class="constant">TodoList</span><span class="punct">.</span><span class="ident">original</span>
+  <span class="attribute">@tasks</span><span class="punct">.</span><span class="ident">each</span> <span class="keyword">do</span> <span class="punct">|</span><span class="ident">title</span><span class="punct">,</span> <span class="ident">value</span><span class="punct">|</span>
+    <span class="ident">status</span> <span class="punct">=</span> <span class="ident">value</span><span class="punct">[</span><span class="symbol">:done</span><span class="punct">]</span> <span class="punct">?</span> <span class="punct">&#39;</span><span class="string">done</span><span class="punct">&#39;</span> <span class="punct">:</span> <span class="punct">&#39;</span><span class="string">not done</span><span class="punct">&#39;</span>
+    <span class="attribute">@tasks</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span> <span class="punct">=</span> <span class="ident">status</span>
+  <span class="keyword">end</span>
+<span class="keyword">end</span></code></pre>
 
-<p>This will take care of the logic inside the template, which now should be
-changed to do following:</p>
+<p>This will take care of the logic inside the template, which now should be changed to do following:</p>
 
-<pre><code>&lt;html&gt;
-  &lt;head&gt;
-    &lt;title&gt;TodoList&lt;/title&gt;
-  &lt;/head&gt;
-  &lt;body&gt;
-    &lt;h1&gt;TodoList&lt;/h1&gt;
+<pre><code class="ruby" lang="ruby"><span class="punct">&lt;</span><span class="ident">html</span><span class="punct">&gt;</span>
+  <span class="punct">&lt;</span><span class="ident">head</span><span class="punct">&gt;</span>
+    <span class="punct">&lt;</span><span class="ident">title</span><span class="punct">&gt;</span><span class="constant">TodoList</span><span class="punct">&lt;/</span><span class="regex">title&gt;
+  &lt;</span><span class="punct">/</span><span class="ident">head</span><span class="punct">&gt;</span>
+  <span class="punct">&lt;</span><span class="ident">body</span><span class="punct">&gt;</span>
+    <span class="punct">&lt;</span><span class="ident">h1</span><span class="punct">&gt;</span><span class="constant">TodoList</span><span class="punct">&lt;/</span><span class="regex">h1&gt;
     &lt;?r if @tasks.empty? ?&gt;
       No Tasks
     &lt;?r else ?&gt;
       &lt;ul&gt;
         &lt;?r @tasks.each do |title, status| ?&gt;
-          &lt;li&gt;#{c title}: #{status}&lt;/li&gt;
-        &lt;?r end ?&gt;
-      &lt;/ul&gt;
+          &lt;li&gt;<span class="expr">#{c title}</span>: <span class="expr">#{status}</span>&lt;</span><span class="punct">/</span><span class="ident">li</span><span class="punct">&gt;</span>
+        <span class="punct">&lt;</span><span class="char">?r</span> <span class="keyword">end</span> <span class="char">?&gt;</span>
+      <span class="punct">&lt;/</span><span class="regex">ul&gt;
     &lt;?r end ?&gt;
-  &lt;/body&gt;
-&lt;/html&gt;
-</code></pre>
+  &lt;</span><span class="punct">/</span><span class="ident">body</span><span class="punct">&gt;</span>
+<span class="punct">&lt;/</span><span class="regex">html&gt;</span></code></pre>
 
 <p>The rest of the template can stay the same.</p>
 
-<p>Now, if you browse to http://localhost:7000/ again you will not notice any
-change, which is how it should be. The only change is that if there are no
-Tasks it will say so.</p>
+<p>Now, if you browse to http://localhost:7000/ again you will not notice any change, which is how it should be. The only change is that if there are no Tasks it will say so.</p>
 
 <p>Some things you should know:</p>
 
 <ul>
 <li>Instance-variables defined in the Controller are available in the View.</li>
+
 <li>The return-value of the Controller does not matter if a template is present.</li>
 </ul>
 
-<a name="Fifth_Step,_getting_dynamic"><h2>Fifth Step, getting dynamic</h2></a>
+<h2 id="fifth_step_getting_dynamic">Fifth Step, getting dynamic</h2>
 
-<p>We set out to build the ultimate to-do list, but there are still some things
-missing. First off, we want to add new tasks, so let's get that done.</p>
+<p>We set out to build the ultimate to-do list, but there are still some things missing. First off, we want to add new tasks, so let&#8217;s get that done.</p>
 
 <p>Add a link on the <code>view/index.xhtml</code> like this:</p>
 
 <pre><code>&lt;h1&gt;TodoList&lt;/h1&gt;
-&lt;a href="/new"&gt;New Task&lt;/a&gt;
-</code></pre>
+&lt;a href=&quot;/new&quot;&gt;New Task&lt;/a&gt;</code></pre>
 
 <p>Open a new file <code>view/new.xhtml</code> with a form to add a new task.</p>
 
@@ -273,160 +203,124 @@ missing. First off, we want to add new tasks, so let's get that done.</p>
   &lt;/head&gt;
   &lt;body&gt;
     &lt;h1&gt;New Task&lt;/h1&gt;
-    &lt;a href="/"&gt;Back to TodoList&lt;/a&gt;
-    &lt;form method="POST" action="create"&gt;
-      Task: &lt;input type="text" name="title" /&gt;&lt;br /&gt;
-      &lt;input type="submit" /&gt;
+    &lt;a href=&quot;/&quot;&gt;Back to TodoList&lt;/a&gt;
+    &lt;form method=&quot;POST&quot; action=&quot;create&quot;&gt;
+      Task: &lt;input type=&quot;text&quot; name=&quot;title&quot; /&gt;&lt;br /&gt;
+      &lt;input type=&quot;submit&quot; /&gt;
     &lt;/form&gt;
   &lt;/body&gt;
-&lt;/html&gt;
-</code></pre>
+&lt;/html&gt;</code></pre>
 
-<p>We will not need a method for this on our controller, in fact, actions can
-consist of either method and template or only one of them. The Controller
-can act as a View and the View can work like you may know it from PHP.</p>
+<p>We will not need a method for this on our controller, in fact, actions can consist of either method and template or only one of them. The Controller can act as a View and the View can work like you may know it from PHP.</p>
 
-<p>If you try to use this form you will notice that we have not yet defined a way
-to actually create the task.</p>
+<p>If you try to use this form you will notice that we have not yet defined a way to actually create the task.</p>
 
-<p>You will get the default Ramaze error-page instead. Please take your time to
-explore it and see how Ramaze reacted on the error.</p>
+<p>You will get the default Ramaze error-page instead. Please take your time to explore it and see how Ramaze reacted on the error.</p>
 
-<p>It will show you the back trace and what state the application is in at the
-moment, the request and response and the contents of the session. This is very
-useful for debugging and development, you can provide your own set of
-error-pages before going into production (or deactivate them fully) though.</p>
+<p>It will show you the back trace and what state the application is in at the moment, the request and response and the contents of the session. This is very useful for debugging and development, you can provide your own set of error-pages before going into production (or deactivate them fully) though.</p>
 
-<p>OK, let's implement the action for <code>#create</code>, all we want to do is take the
-requests parameters and create a new task for it, this looks like following on
-your MainController.</p>
+<p>OK, let&#8217;s implement the action for <code>#create</code>, all we want to do is take the requests parameters and create a new task for it, this looks like following on your MainController.</p>
 
-<pre><code>def create
-  title = request['title']
-  TodoList[title] = {:done =&gt; false}
-  redirect Rs()
-end
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="keyword">def </span><span class="method">create</span>
+  <span class="ident">title</span> <span class="punct">=</span> <span class="ident">request</span><span class="punct">[&#39;</span><span class="string">title</span><span class="punct">&#39;]</span>
+  <span class="constant">TodoList</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span> <span class="punct">=</span> <span class="punct">{</span><span class="symbol">:done</span> <span class="punct">=&gt;</span> <span class="constant">false</span><span class="punct">}</span>
+  <span class="ident">redirect</span> <span class="constant">Rs</span><span class="punct">()</span>
+<span class="keyword">end</span></code></pre>
 
-<p>That's all folks!</p>
+<p>That&#8217;s all folks!</p>
 
-<p>We get the title from the request-object, put it into our TodoList as undone
-and redirect back to the mapping of the current Controller ('/' in this case).</p>
+<p>We get the title from the request-object, put it into our TodoList as undone and redirect back to the mapping of the current Controller (&#8217;/&#8217; in this case).</p>
 
-<p>Now you can create as many tasks as you want, please don't get overworked ;)</p>
+<p>Now you can create as many tasks as you want, please don&#8217;t get overworked ;)</p>
 
-<a name="Sixth_Step,_open_and_close_tasks"><h2>Sixth Step, open and close tasks</h2></a>
+<h2 id="sixth_step_open_and_close_tasks">Sixth Step, open and close tasks</h2>
 
-<p>Since the nature of tasks is to be done eventually
-we will need some way to mark it as done or open tasks again.</p>
+<p>Since the nature of tasks is to be done eventually we will need some way to mark it as done or open tasks again.</p>
 
 <p>Jump into <code>view/index.xhtml</code> and do the following:</p>
 
-<pre><code>&lt;?r @tasks.each do |title, status, toggle| ?&gt;
-  &lt;li&gt;
-    #{c title}: #{status} - [ #{toggle} ]
-  &lt;/li&gt;
-&lt;?r end ?&gt;
-</code></pre>
-
-<p>We added a new element here, <code>toggle</code>, the Controller should give us
-a link to change the status corresponding to the status of the task, so off
-we go and change the index method on the controller once again:</p>
-
-<pre><code>def index
-  @tasks = []
-  TodoList.original.each do |title, value|
-    if value[:done]
-      status = 'done'
-      toggle = A('Open Task', :href =&gt; Rs(:open, title))
-    else
-      status = 'not done'
-      toggle = A('Close Task', :href =&gt; Rs(:close, title))
-    end
-    @tasks &lt;&lt; [title, status, toggle]
-  end
-  @tasks.sort!
-end
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="punct">&lt;</span><span class="char">?r</span> <span class="attribute">@tasks</span><span class="punct">.</span><span class="ident">each</span> <span class="keyword">do</span> <span class="punct">|</span><span class="ident">title</span><span class="punct">,</span> <span class="ident">status</span><span class="punct">,</span> <span class="ident">toggle</span><span class="punct">|</span> <span class="char">?&gt;</span>
+  <span class="punct">&lt;</span><span class="ident">li</span><span class="punct">&gt;</span>
+    <span class="comment">#{c title}: #{status} - [ #{toggle} ]</span>
+  <span class="punct">&lt;/</span><span class="regex">li&gt;
+&lt;?r end</span></code></pre>
+
+<p>We added a new element here, <code>toggle</code>, the Controller should give us a link to change the status corresponding to the status of the task, so off we go and change the index method on the controller once again:</p>
+
+<pre><code class="ruby" lang="ruby"><span class="keyword">def </span><span class="method">index</span>
+  <span class="attribute">@tasks</span> <span class="punct">=</span> <span class="punct">[]</span>
+  <span class="constant">TodoList</span><span class="punct">.</span><span class="ident">original</span><span class="punct">.</span><span class="ident">each</span> <span class="keyword">do</span> <span class="punct">|</span><span class="ident">title</span><span class="punct">,</span> <span class="ident">value</span><span class="punct">|</span>
+    <span class="keyword">if</span> <span class="ident">value</span><span class="punct">[</span><span class="symbol">:done</span><span class="punct">]</span>
+      <span class="ident">status</span> <span class="punct">=</span> <span class="punct">&#39;</span><span class="string">done</span><span class="punct">&#39;</span>
+      <span class="ident">toggle</span> <span class="punct">=</span> <span class="constant">A</span><span class="punct">(&#39;</span><span class="string">Open Task</span><span class="punct">&#39;,</span> <span class="symbol">:href</span> <span class="punct">=&gt;</span> <span class="constant">Rs</span><span class="punct">(</span><span class="symbol">:open</span><span class="punct">,</span> <span class="ident">title</span><span class="punct">))</span>
+    <span class="keyword">else</span>
+      <span class="ident">status</span> <span class="punct">=</span> <span class="punct">&#39;</span><span class="string">not done</span><span class="punct">&#39;</span>
+      <span class="ident">toggle</span> <span class="punct">=</span> <span class="constant">A</span><span class="punct">(&#39;</span><span class="string">Close Task</span><span class="punct">&#39;,</span> <span class="symbol">:href</span> <span class="punct">=&gt;</span> <span class="constant">Rs</span><span class="punct">(</span><span class="symbol">:close</span><span class="punct">,</span> <span class="ident">title</span><span class="punct">))</span>
+    <span class="keyword">end</span>
+    <span class="attribute">@tasks</span> <span class="punct">&lt;&lt;</span> <span class="punct">[</span><span class="ident">title</span><span class="punct">,</span> <span class="ident">status</span><span class="punct">,</span> <span class="ident">toggle</span><span class="punct">]</span>
+  <span class="keyword">end</span>
+  <span class="attribute">@tasks</span><span class="punct">.</span><span class="ident">sort!</span>
+<span class="keyword">end</span></code></pre>
 
 <p>Wow, quite some new stuff here. Let me explain that in detail.</p>
 
-<p>We first decide whether a task is done or not, then go on and provide a link to
-toggle the status, A and Rs are both methods that help you do that.
-The result will be something like:</p>
+<p>We first decide whether a task is done or not, then go on and provide a link to toggle the status, A and Rs are both methods that help you do that. The result will be something like:</p>
 
-<pre><code>&lt;a href="/open/Wash+dishes"&gt;Close Task&lt;/a&gt;
-</code></pre>
+<pre><code>&lt;a href=&quot;/open/Wash+dishes&quot;&gt;Close Task&lt;/a&gt;</code></pre>
 
-<p>Rs actually is responsible to build the links href, for more information please
-take a look at the RDoc for LinkHelper.</p>
+<p>Rs actually is responsible to build the links href, for more information please take a look at the RDoc for LinkHelper.</p>
 
-<p>Also, you might have noticed that the tasks were changing order on every reload,
-which is because we were using an Hash, which are per definition unsorted, so
-now we use an array to hold our tasks and sort it.</p>
+<p>Also, you might have noticed that the tasks were changing order on every reload, which is because we were using an Hash, which are per definition unsorted, so now we use an array to hold our tasks and sort it.</p>
 
-<p>As usual since the links for open and close don't lead anywhere, add the
-corresponding methods to the Controller:</p>
+<p>As usual since the links for open and close don&#8217;t lead anywhere, add the corresponding methods to the Controller:</p>
 
-<pre><code>def open title
-  task_status title, false
-  redirect Rs()
-end
+<pre><code class="ruby" lang="ruby"><span class="keyword">def </span><span class="method">open</span> <span class="ident">title</span>
+  <span class="ident">task_status</span> <span class="ident">title</span><span class="punct">,</span> <span class="constant">false</span>
+  <span class="ident">redirect</span> <span class="constant">Rs</span><span class="punct">()</span>
+<span class="keyword">end</span>
 
-def close title
-  task_status title, true
-  redirect Rs()
-end
+<span class="keyword">def </span><span class="method">close</span> <span class="ident">title</span>
+  <span class="ident">task_status</span> <span class="ident">title</span><span class="punct">,</span> <span class="constant">true</span>
+  <span class="ident">redirect</span> <span class="constant">Rs</span><span class="punct">()</span>
+<span class="keyword">end</span>
 
-private
+<span class="ident">private</span>
 
-def task_status title, status
-  task = TodoList[title]
-  task[:done] = status
-  TodoList[title] = task
-end
-</code></pre>
+<span class="keyword">def </span><span class="method">task_status</span> <span class="ident">title</span><span class="punct">,</span> <span class="ident">status</span>
+  <span class="ident">task</span> <span class="punct">=</span> <span class="constant">TodoList</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span>
+  <span class="ident">task</span><span class="punct">[</span><span class="symbol">:done</span><span class="punct">]</span> <span class="punct">=</span> <span class="ident">status</span>
+  <span class="constant">TodoList</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span> <span class="punct">=</span> <span class="ident">task</span>
+<span class="keyword">end</span></code></pre>
 
-<p>Oh, now what have we got here?
-<code>private</code> declares that methods from here on are only to be used within the
-Controller itself, we define an <code>#task_status</code> method that takes the title and
-status to be set so we don't have to repeat that code in <code>#open</code> and <code>#close</code>
-and follow the DRY (Don't repeat yourself) paradigm.</p>
+<p>Oh, now what have we got here? <code>private</code> declares that methods from here on are only to be used within the Controller itself, we define an <code>#task_status</code> method that takes the title and status to be set so we don&#8217;t have to repeat that code in <code>#open</code> and <code>#close</code> and follow the DRY (Don&#8217;t repeat yourself) paradigm.</p>
 
-<p>Another thing we have not encountered so far is that you can define your public
-methods to take parameters on their own, they will be calculated from requests.</p>
+<p>Another thing we have not encountered so far is that you can define your public methods to take parameters on their own, they will be calculated from requests.</p>
 
-<pre><code>'/open/Wash+dishes'
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="punct">&#39;</span><span class="string">/open/Wash+dishes</span><span class="punct">&#39;</span></code></pre>
 
 <p>will translate into:</p>
 
-<pre><code>open('Wash dishes')
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="ident">open</span><span class="punct">(&#39;</span><span class="string">Wash dishes</span><span class="punct">&#39;)</span></code></pre>
 
-<p>Which in turn will call <code>task_status('Wash dishes', false)</code></p>
+<p>Which in turn will call <code>task_status(&#39;Wash dishes&#39;, false)</code></p>
 
-<p>That's it, go on and try it :)</p>
+<p>That&#8217;s it, go on and try it :)</p>
 
-<a name="Seventh_Step,_delete_tasks"><h2>Seventh Step, delete tasks</h2></a>
+<h2 id="seventh_step_delete_tasks">Seventh Step, delete tasks</h2>
 
-<p>Well, creating, opening and closing work now, one of the things you will
-consider is to delete a task permanently.</p>
+<p>Well, creating, opening and closing work now, one of the things you will consider is to delete a task permanently.</p>
 
-<p>This is just two little changes away, so let's add the link for deletion in our
-Controller:</p>
+<p>This is just two little changes away, so let&#8217;s add the link for deletion in our Controller:</p>
 
-<pre><code>delete = A('Delete', :href =&gt; Rs(:delete, title))
-@tasks &lt;&lt; [title, status, toggle, delete]
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="ident">delete</span> <span class="punct">=</span> <span class="constant">A</span><span class="punct">(&#39;</span><span class="string">Delete</span><span class="punct">&#39;,</span> <span class="symbol">:href</span> <span class="punct">=&gt;</span> <span class="constant">Rs</span><span class="punct">(</span><span class="symbol">:delete</span><span class="punct">,</span> <span class="ident">title</span><span class="punct">))</span>
+<span class="attribute">@tasks</span> <span class="punct">&lt;&lt;</span> <span class="punct">[</span><span class="ident">title</span><span class="punct">,</span> <span class="ident">status</span><span class="punct">,</span> <span class="ident">toggle</span><span class="punct">,</span> <span class="ident">delete</span><span class="punct">]</span></code></pre>
 
-<p>and an corresponding method while we're at it:</p>
+<p>and an corresponding method while we&#8217;re at it:</p>
 
-<pre><code>def delete title
-  TodoList.delete title
-  redirect Rs()
-end
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="keyword">def </span><span class="method">delete</span> <span class="ident">title</span>
+  <span class="constant">TodoList</span><span class="punct">.</span><span class="ident">delete</span> <span class="ident">title</span>
+  <span class="ident">redirect</span> <span class="constant">Rs</span><span class="punct">()</span>
+<span class="keyword">end</span></code></pre>
 
 <p>Now jumping to <code>view/index.xhtml</code> again, change it so it shows the link:</p>
 
@@ -434,22 +328,17 @@ end
   &lt;li&gt;
     #{c title}: #{status} [ #{toggle} | #{delete} ]
   &lt;/li&gt;
-&lt;?r end ?&gt;
-</code></pre>
+&lt;?r end ?&gt;</code></pre>
 
 <p>Voilà, you now have acquired the Certificate of Ramazeness.</p>
 
-<p>Just kidding, but that really are the basics, in the next few steps I will
-explain some more advanced concepts of Ramaze and Ezamar.</p>
+<p>Just kidding, but that really are the basics, in the next few steps I will explain some more advanced concepts of Ramaze and Ezamar.</p>
 
-<a name="Eighth_Step,_Elements"><h2>Eighth Step, Elements</h2></a>
+<h2 id="eighth_step_elements">Eighth Step, Elements</h2>
 
-<pre><code>&lt;Page&gt;&lt;/Page&gt;
-</code></pre>
+<pre><code>&lt;Page&gt;&lt;/Page&gt;</code></pre>
 
-<p>This is called an Element, Ramaze will go and search for a class that matches
-the name Page and responds to <code>#render</code>. Then it will go and hand the content in
-between to that Element.</p>
+<p>This is called an Element, Ramaze will go and search for a class that matches the name Page and responds to <code>#render</code>. Then it will go and hand the content in between to that Element.</p>
 
 <p>Sounds weird?</p>
 
@@ -462,71 +351,63 @@ between to that Element.</p>
   &lt;body&gt;
     &lt;h1&gt;some title&lt;/h1&gt;
   &lt;/body&gt;
-&lt;/html&gt;
-</code></pre>
+&lt;/html&gt;</code></pre>
 
 <p>How about replacing that with something short and reusable:</p>
 
-<pre><code>&lt;Page title="TodoList"&gt;
+<pre><code>&lt;Page title=&quot;TodoList&quot;&gt;
   your other content
-&lt;/Page&gt;
-</code></pre>
+&lt;/Page&gt;</code></pre>
 
-<p>Would be nice of course, and when you start having more templates it makes an
-awful lot of sense being able to change the enclosing stuff in one place.</p>
+<p>Would be nice of course, and when you start having more templates it makes an awful lot of sense being able to change the enclosing stuff in one place.</p>
 
-<p>So let's apply DRY here as well.</p>
+<p>So let&#8217;s apply DRY here as well.</p>
 
 <p>Take a look at the <code>src/element/page.rb</code></p>
 
-<pre><code>class Page &lt; Ezamar::Element
-  def render
-    %{
+<pre><code class="ruby" lang="ruby"><span class="keyword">class </span><span class="class">Page</span> <span class="punct">&lt;</span> <span class="constant">Ezamar</span><span class="punct">::</span><span class="constant">Element</span>
+  <span class="keyword">def </span><span class="method">render</span>
+    <span class="punct">%{</span><span class="string">
     &lt;html&gt;
       &lt;head&gt;
         &lt;title&gt;Welcome to Ramaze&lt;/title&gt;
       &lt;/head&gt;
       &lt;body&gt;
-        #{content}
+        <span class="expr">#{content}</span>
       &lt;/body&gt;
     &lt;/html&gt;
-    }
-  end
-end
-</code></pre>
+    </span><span class="punct">}</span>
+  <span class="keyword">end</span>
+<span class="keyword">end</span></code></pre>
 
-<p>Alright, most things we need are in place already, the most important thing
-is the <code>#content</code> method that we call with <code>#{content}</code> inside the string in
-<code>#render</code>.</p>
+<p>Alright, most things we need are in place already, the most important thing is the <code>#content</code> method that we call with <code>#{content}</code> inside the string in <code>#render</code>.</p>
 
-<p>Just adopt it to your liking, I'll just use the things we had in our templates
-so far:</p>
+<p>Just adopt it to your liking, I&#8217;ll just use the things we had in our templates so far:</p>
 
-<pre><code>class Page &lt; Ezamar::Element
-  def render
-    %{
+<pre><code class="ruby" lang="ruby"><span class="keyword">class </span><span class="class">Page</span> <span class="punct">&lt;</span> <span class="constant">Ezamar</span><span class="punct">::</span><span class="constant">Element</span>
+  <span class="keyword">def </span><span class="method">render</span>
+    <span class="punct">%{</span><span class="string">
     &lt;html&gt;
       &lt;head&gt;
         &lt;title&gt;TodoList&lt;/title&gt;
       &lt;/head&gt;
       &lt;body&gt;
-        &lt;h1&gt;#{@title}&lt;/h1&gt;
-        #{content}
+        &lt;h1&gt;<span class="expr">#{@title}</span>&lt;/h1&gt;
+        <span class="expr">#{content}</span>
       &lt;/body&gt;
     &lt;/html&gt;
-    }
-  end
-end
-</code></pre>
+    </span><span class="punct">}</span>
+  <span class="keyword">end</span>
+<span class="keyword">end</span></code></pre>
 
 <p>Please note that instance variables reflecting the parameters are set.</p>
 
-<p>And let's change our templates as well.</p>
+<p>And let&#8217;s change our templates as well.</p>
 
 <p>First the <code>view/index.xhtml</code></p>
 
-<pre><code>&lt;Page title="TodoList"&gt;
-  &lt;a href="/new"&gt;New Task&lt;/a&gt;
+<pre><code>&lt;Page title=&quot;TodoList&quot;&gt;
+  &lt;a href=&quot;/new&quot;&gt;New Task&lt;/a&gt;
   &lt;?r if @tasks.empty? ?&gt;
     No Tasks
   &lt;?r else ?&gt;
@@ -538,27 +419,23 @@ end
       &lt;?r end ?&gt;
     &lt;/ul&gt;
   &lt;?r end ?&gt;
-&lt;/Page&gt;
-</code></pre>
+&lt;/Page&gt;</code></pre>
 
 <p>and the <code>view/new.xhtml</code></p>
 
-<pre><code>&lt;Page title="New Task"&gt;
-  &lt;a href="/"&gt;Back to TodoList&lt;/a&gt;
-  &lt;form method="POST" action="create"&gt;
-    Task: &lt;input type="text" name="title" /&gt;&lt;br /&gt;
-    &lt;input type="submit" /&gt;
+<pre><code>&lt;Page title=&quot;New Task&quot;&gt;
+  &lt;a href=&quot;/&quot;&gt;Back to TodoList&lt;/a&gt;
+  &lt;form method=&quot;POST&quot; action=&quot;create&quot;&gt;
+    Task: &lt;input type=&quot;text&quot; name=&quot;title&quot; /&gt;&lt;br /&gt;
+    &lt;input type=&quot;submit&quot; /&gt;
   &lt;/form&gt;
-&lt;/Page&gt;
-</code></pre>
+&lt;/Page&gt;</code></pre>
 
-<p>Alright, now just go and look at the result in the browser, try changing
-the things inside the Element and look at how it behaves.</p>
+<p>Alright, now just go and look at the result in the browser, try changing the things inside the Element and look at how it behaves.</p>
 
-<a name="Ninth_Step,_Prettify"><h2>Ninth Step, Prettify</h2></a>
+<h2 id="ninth_step_prettify">Ninth Step, Prettify</h2>
 
-<p>We structure the data inside the list a little bit, in this case into a table,
-to get it line up properly and look actually structured.</p>
+<p>We structure the data inside the list a little bit, in this case into a table, to get it line up properly and look actually structured.</p>
 
 <p>So, from what we have right now:</p>
 
@@ -568,25 +445,22 @@ to get it line up properly and look actually structured.</p>
       #{c title}: #{status} [ #{toggle} | #{delete} ]
     &lt;/li&gt;
   &lt;?r end ?&gt;
-&lt;/ul&gt;
-</code></pre>
+&lt;/ul&gt;</code></pre>
 
 <p>To something like this:</p>
 
 <pre><code>&lt;table&gt;
   &lt;?r @tasks.each do |title, status, toggle, delete| ?&gt;
     &lt;tr&gt;
-      &lt;td class="title"&gt;  #{c title}  &lt;/td&gt;
-      &lt;td class="status"&gt; #{status} &lt;/td&gt;
-      &lt;td class="toggle"&gt; #{toggle} &lt;/td&gt;
-      &lt;td class="delete"&gt; #{delete} &lt;/td&gt;
+      &lt;td class=&quot;title&quot;&gt;  #{c title}  &lt;/td&gt;
+      &lt;td class=&quot;status&quot;&gt; #{status} &lt;/td&gt;
+      &lt;td class=&quot;toggle&quot;&gt; #{toggle} &lt;/td&gt;
+      &lt;td class=&quot;delete&quot;&gt; #{delete} &lt;/td&gt;
     &lt;/tr&gt;
   &lt;?r end ?&gt;
-&lt;/table&gt;
-</code></pre>
+&lt;/table&gt;</code></pre>
 
-<p>And, since we have proper classes to address some style sheets, jump into the
-Page element and add some style sheet:</p>
+<p>And, since we have proper classes to address some style sheets, jump into the Page element and add some style sheet:</p>
 
 <pre><code>&lt;head&gt;
   &lt;title&gt;TodoList&lt;/title&gt;
@@ -598,219 +472,163 @@ Page element and add some style sheet:</p>
     td.status { margin:      1em;               }
     a         { color:       #3a3;              }
   &lt;/style&gt;
-&lt;/head&gt;
-</code></pre>
+&lt;/head&gt;</code></pre>
 
-<p>That looks quite a bit nicer, right?  And yes, if you don't like tables (though
-this is an entirely legit use in my opinion) you can just do it like you want,
-using nested lists or divs/spans, replacing the open/close and delete links with
-nice images and changing the style according to the status.</p>
+<p>That looks quite a bit nicer, right? And yes, if you don&#8217;t like tables (though this is an entirely legit use in my opinion) you can just do it like you want, using nested lists or divs/spans, replacing the open/close and delete links with nice images and changing the style according to the status.</p>
 
 <p>I will leave this as an exercise to the reader.</p>
 
-<a name="Tenth_Step,_Configuration"><h2>Tenth Step, Configuration</h2></a>
+<h2 id="tenth_step_configuration">Tenth Step, Configuration</h2>
 
-<p>To round up this tutorial a bit, let's introduce you to configuration in Ramaze.
-This will not go into full depth of possibilities or a total coverage of the
-options, since they are bound to change over time.</p>
+<p>To round up this tutorial a bit, let&#8217;s introduce you to configuration in Ramaze. This will not go into full depth of possibilities or a total coverage of the options, since they are bound to change over time.</p>
 
-<p>First of all, the default port Ramaze runs on is 7000, but to make it a usual
-webserver it has to run on port 80.  So, let's add following line in your
-start.rb right after the lines of require you added before:</p>
+<p>First of all, the default port Ramaze runs on is 7000, but to make it a usual webserver it has to run on port 80. So, let&#8217;s add following line in your start.rb right after the lines of require you added before:</p>
 
-<pre><code>Ramaze::Global.port = 80
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="constant">Ramaze</span><span class="punct">::</span><span class="constant">Global</span><span class="punct">.</span><span class="ident">port</span> <span class="punct">=</span> <span class="number">80</span></code></pre>
 
-<p>Alright, that wasn't that hard.
-Let's say now you also want to run Mongrel instead of WEBrick, to get nice a bit
-of performance:</p>
+<p>Alright, that wasn&#8217;t that hard. Let&#8217;s say now you also want to run Mongrel instead of WEBrick, to get nice a bit of performance:</p>
 
-<pre><code>Ramaze::Global.adapter = :mongrel
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="constant">Ramaze</span><span class="punct">::</span><span class="constant">Global</span><span class="punct">.</span><span class="ident">adapter</span> <span class="punct">=</span> <span class="symbol">:mongrel</span></code></pre>
 
 <p>To do this in a DRY way you could also do following:</p>
 
-<pre><code>Ramaze::Global.setup do |g|
-  g.port = 80
-  g.adapter = :mongrel
-end
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="constant">Ramaze</span><span class="punct">::</span><span class="constant">Global</span><span class="punct">.</span><span class="ident">setup</span> <span class="keyword">do</span> <span class="punct">|</span><span class="ident">g</span><span class="punct">|</span>
+  <span class="ident">g</span><span class="punct">.</span><span class="ident">port</span> <span class="punct">=</span> <span class="number">80</span>
+  <span class="ident">g</span><span class="punct">.</span><span class="ident">adapter</span> <span class="punct">=</span> <span class="symbol">:mongrel</span>
+<span class="keyword">end</span></code></pre>
 
-<p>It seems to be quite common to put this configuration into separate files so you
-can just require it on demand.  There are other, slightly stronger way to set
-options, which is either using flags on the ramaze executable, or like this:</p>
+<p>It seems to be quite common to put this configuration into separate files so you can just require it on demand. There are other, slightly stronger way to set options, which is either using flags on the ramaze executable, or like this:</p>
 
-<pre><code>Ramaze.start :port =&gt; 80, :adapter =&gt; :mongrel
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="constant">Ramaze</span><span class="punct">.</span><span class="ident">start</span> <span class="symbol">:port</span> <span class="punct">=&gt;</span> <span class="number">80</span><span class="punct">,</span> <span class="symbol">:adapter</span> <span class="punct">=&gt;</span> <span class="symbol">:mongrel</span></code></pre>
 
-<p>We haven't started Ramaze directly as of yet, but this allows you to ignore the
-ramaze executable and just run your application by <code>ruby start.rb</code>.</p>
+<p>We haven&#8217;t started Ramaze directly as of yet, but this allows you to ignore the ramaze executable and just run your application by <code>ruby start.rb</code>.</p>
 
-<a name="Eleventh_Step,_Refactor_with_AspectHelper"><h2>Eleventh Step, Refactor with AspectHelper</h2></a>
+<h2 id="eleventh_step_refactor_with_aspecthelper">Eleventh Step, Refactor with AspectHelper</h2>
 
 <p>Now, if you take a closer look at the Controller you will see:</p>
 
-<pre><code>def create
-  title = request['title']
-  TodoList[title] = {:done =&gt; false}
-  redirect R(self)
-end
+<pre><code class="ruby" lang="ruby"><span class="keyword">def </span><span class="method">create</span>
+  <span class="ident">title</span> <span class="punct">=</span> <span class="ident">request</span><span class="punct">[&#39;</span><span class="string">title</span><span class="punct">&#39;]</span>
+  <span class="constant">TodoList</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span> <span class="punct">=</span> <span class="punct">{</span><span class="symbol">:done</span> <span class="punct">=&gt;</span> <span class="constant">false</span><span class="punct">}</span>
+  <span class="ident">redirect</span> <span class="constant">R</span><span class="punct">(</span><span class="constant">self</span><span class="punct">)</span>
+<span class="keyword">end</span>
 
-def open title
-  task_status title, false
-  redirect R(self)
-end
+<span class="keyword">def </span><span class="method">open</span> <span class="ident">title</span>
+  <span class="ident">task_status</span> <span class="ident">title</span><span class="punct">,</span> <span class="constant">false</span>
+  <span class="ident">redirect</span> <span class="constant">R</span><span class="punct">(</span><span class="constant">self</span><span class="punct">)</span>
+<span class="keyword">end</span>
 
-def close title
-  task_status title, true
-  redirect R(self)
-end
+<span class="keyword">def </span><span class="method">close</span> <span class="ident">title</span>
+  <span class="ident">task_status</span> <span class="ident">title</span><span class="punct">,</span> <span class="constant">true</span>
+  <span class="ident">redirect</span> <span class="constant">R</span><span class="punct">(</span><span class="constant">self</span><span class="punct">)</span>
+<span class="keyword">end</span>
 
-def delete title
-  TodoList.delete title
-  redirect R(self)
-end
-</code></pre>
+<span class="keyword">def </span><span class="method">delete</span> <span class="ident">title</span>
+  <span class="constant">TodoList</span><span class="punct">.</span><span class="ident">delete</span> <span class="ident">title</span>
+  <span class="ident">redirect</span> <span class="constant">R</span><span class="punct">(</span><span class="constant">self</span><span class="punct">)</span>
+<span class="keyword">end</span></code></pre>
 
-<p>We did some refactoring before, by introducing <code>#task_status</code>, but here we have
-repetition again: <code>redirect Rs()</code> <em>after</em> each method did its job.</p>
+<p>We did some refactoring before, by introducing <code>#task_status</code>, but here we have repetition again: <code>redirect Rs()</code> <em>after</em> each method did its job.</p>
 
-<p>However, we can take advantage of one of the helpers Ramaze offers, the
-AspectHelper.
-It allows you to easily wrap actions in your controller with other methods</p>
+<p>However, we can take advantage of one of the helpers Ramaze offers, the AspectHelper. It allows you to easily wrap actions in your controller with other methods</p>
 
 <p>In your Controller, replace the previous chunk with following:</p>
 
-<pre><code>def create
-  title = request['title']
-  TodoList[title] = {:done =&gt; false}
-end
+<pre><code class="ruby" lang="ruby"><span class="keyword">def </span><span class="method">create</span>
+  <span class="ident">title</span> <span class="punct">=</span> <span class="ident">request</span><span class="punct">[&#39;</span><span class="string">title</span><span class="punct">&#39;]</span>
+  <span class="constant">TodoList</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span> <span class="punct">=</span> <span class="punct">{</span><span class="symbol">:done</span> <span class="punct">=&gt;</span> <span class="constant">false</span><span class="punct">}</span>
+<span class="keyword">end</span>
 
-def open title
-  task_status title, false
-end
+<span class="keyword">def </span><span class="method">open</span> <span class="ident">title</span>
+  <span class="ident">task_status</span> <span class="ident">title</span><span class="punct">,</span> <span class="constant">false</span>
+<span class="keyword">end</span>
 
-def close title
-  task_status title, true
-end
+<span class="keyword">def </span><span class="method">close</span> <span class="ident">title</span>
+  <span class="ident">task_status</span> <span class="ident">title</span><span class="punct">,</span> <span class="constant">true</span>
+<span class="keyword">end</span>
 
-def delete title
-  TodoList.delete title
-end
+<span class="keyword">def </span><span class="method">delete</span> <span class="ident">title</span>
+  <span class="constant">TodoList</span><span class="punct">.</span><span class="ident">delete</span> <span class="ident">title</span>
+<span class="keyword">end</span>
 
-helper :aspect
-after(:create, :open, :close, :delete){ redirect(Rs()) }
-</code></pre>
+<span class="ident">helper</span> <span class="symbol">:aspect</span>
+<span class="ident">after</span><span class="punct">(</span><span class="symbol">:create</span><span class="punct">,</span> <span class="symbol">:open</span><span class="punct">,</span> <span class="symbol">:close</span><span class="punct">,</span> <span class="symbol">:delete</span><span class="punct">){</span> <span class="ident">redirect</span><span class="punct">(</span><span class="constant">Rs</span><span class="punct">())</span> <span class="punct">}</span></code></pre>
 
 <p>Alright, that looks a lot nicer already and is definitely easier to maintain.</p>
 
-<p>There is a symmetrical <code>before</code> aspect that you could take advantage of as
-well, and in case you want to add required authentication for all actions of a
-Controller you could use <code>before_all</code> and <code>after_all</code> instead of a list of
-action-names.</p>
+<p>There is a symmetrical <code>before</code> aspect that you could take advantage of as well, and in case you want to add required authentication for all actions of a Controller you could use <code>before_all</code> and <code>after_all</code> instead of a list of action-names.</p>
 
-<a name="Twelfth_Step,_Validation_and_Errors"><h2>Twelfth Step, Validation and Errors</h2></a>
+<h2 id="twelfth_step_validation_and_errors">Twelfth Step, Validation and Errors</h2>
 
-<p>Right now, all kinds of things could still go wrong when you do things like
-creating tasks with no title at all or try to open/close a task that does not
-exist. So in this step we will add some little checks for these cases.</p>
+<p>Right now, all kinds of things could still go wrong when you do things like creating tasks with no title at all or try to open/close a task that does not exist. So in this step we will add some little checks for these cases.</p>
 
 <p>First we head over to the Controller again and take a look at <code>#create</code>:</p>
 
-<pre><code>def create
-  title = request['title']
-  TodoList[title] = {:done =&gt; false}
-end
-</code></pre>
-
-<p>Here we just create a new task, no matter what we get. Every seasoned
-web-developer would advise you to be suspicious about all the input you receive
-from your users, so let's apply this advice.</p>
-
-<pre><code>def create
-  if title = request['title']
-    title.strip!
-    if title.empty?
-      failed("Please enter a title")
-      redirect '/new'
-    end
-    TodoList[title] = {:done =&gt; false}
-  end
-end
-</code></pre>
-
-<p>First of all we check if we got a request with a value for 'title', if we get
-none we just let the aspect kick in that will redirect the browser to the index.
-Next we strip the title of all spaces around it so we can check if it is empty.
-We will talk about the specifics of our error-handling now.</p>
-
-<p>Ramaze has a helper called FlashHelper, that will keep a hash associated with
-the session for one request, afterwards the hash is thrown away. This is
-specifically useful for giving the user feedback while keeping a stateless
-approach.</p>
-
-<p>Let me show you our <code>#failed</code> method (it goes in the private section to
-<code>#task_status</code>):</p>
-
-<pre><code>def failed(message)
-  flash[:error] = message
-end
-</code></pre>
-
-<p>Duh, you may say, wouldn't that fit in the one line instead of the call to
-<code>#failed</code>?
-Indeed, it would, but let me remind you, we have no checks for changing the
-status of a task yet. We will need error-handling there as well, so we just keep
-our code DRY and maintainable by collecting shared behaviour in small pieces.</p>
+<pre><code class="ruby" lang="ruby"><span class="keyword">def </span><span class="method">create</span>
+  <span class="ident">title</span> <span class="punct">=</span> <span class="ident">request</span><span class="punct">[&#39;</span><span class="string">title</span><span class="punct">&#39;]</span>
+  <span class="constant">TodoList</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span> <span class="punct">=</span> <span class="punct">{</span><span class="symbol">:done</span> <span class="punct">=&gt;</span> <span class="constant">false</span><span class="punct">}</span>
+<span class="keyword">end</span></code></pre>
+
+<p>Here we just create a new task, no matter what we get. Every seasoned web-developer would advise you to be suspicious about all the input you receive from your users, so let&#8217;s apply this advice.</p>
+
+<pre><code class="ruby" lang="ruby"><span class="keyword">def </span><span class="method">create</span>
+  <span class="keyword">if</span> <span class="ident">title</span> <span class="punct">=</span> <span class="ident">request</span><span class="punct">[&#39;</span><span class="string">title</span><span class="punct">&#39;]</span>
+    <span class="ident">title</span><span class="punct">.</span><span class="ident">strip!</span>
+    <span class="keyword">if</span> <span class="ident">title</span><span class="punct">.</span><span class="ident">empty?</span>
+      <span class="ident">failed</span><span class="punct">(&quot;</span><span class="string">Please enter a title</span><span class="punct">&quot;)</span>
+      <span class="ident">redirect</span> <span class="punct">&#39;</span><span class="string">/new</span><span class="punct">&#39;</span>
+    <span class="keyword">end</span>
+    <span class="constant">TodoList</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span> <span class="punct">=</span> <span class="punct">{</span><span class="symbol">:done</span> <span class="punct">=&gt;</span> <span class="constant">false</span><span class="punct">}</span>
+  <span class="keyword">end</span>
+<span class="keyword">end</span></code></pre>
+
+<p>First of all we check if we got a request with a value for &#8216;title&#8217;, if we get none we just let the aspect kick in that will redirect the browser to the index. Next we strip the title of all spaces around it so we can check if it is empty. We will talk about the specifics of our error-handling now.</p>
+
+<p>Ramaze has a helper called FlashHelper, that will keep a hash associated with the session for one request, afterwards the hash is thrown away. This is specifically useful for giving the user feedback while keeping a stateless approach.</p>
+
+<p>Let me show you our <code>#failed</code> method (it goes in the private section to <code>#task_status</code>):</p>
+
+<pre><code class="ruby" lang="ruby"><span class="keyword">def </span><span class="method">failed</span><span class="punct">(</span><span class="ident">message</span><span class="punct">)</span>
+  <span class="ident">flash</span><span class="punct">[</span><span class="symbol">:error</span><span class="punct">]</span> <span class="punct">=</span> <span class="ident">message</span>
+<span class="keyword">end</span></code></pre>
+
+<p>Duh, you may say, wouldn&#8217;t that fit in the one line instead of the call to <code>#failed</code>? Indeed, it would, but let me remind you, we have no checks for changing the status of a task yet. We will need error-handling there as well, so we just keep our code DRY and maintainable by collecting shared behaviour in small pieces.</p>
 
 <p>Now on to the <code>#task_status</code>:</p>
 
-<pre><code>def task_status title, status
-  unless task = TodoList[title]
-    failed "No such Task: `#{title}'"
-    redirect_referer
-  end
+<pre><code class="ruby" lang="ruby"><span class="keyword">def </span><span class="method">task_status</span> <span class="ident">title</span><span class="punct">,</span> <span class="ident">status</span>
+  <span class="keyword">unless</span> <span class="ident">task</span> <span class="punct">=</span> <span class="constant">TodoList</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span>
+    <span class="ident">failed</span> <span class="punct">&quot;</span><span class="string">No such Task: `<span class="expr">#{title}</span>&#39;</span><span class="punct">&quot;</span>
+    <span class="ident">redirect_referer</span>
+  <span class="keyword">end</span>
 
-  task[:done] = status
-  TodoList[title] = task
-end
-</code></pre>
+  <span class="ident">task</span><span class="punct">[</span><span class="symbol">:done</span><span class="punct">]</span> <span class="punct">=</span> <span class="ident">status</span>
+  <span class="constant">TodoList</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span> <span class="punct">=</span> <span class="ident">task</span>
+<span class="keyword">end</span></code></pre>
 
 <p>That used to look like this:</p>
 
-<pre><code>def task_status title, status
-  task = TodoList[title]
-  task[:done] = status
-  TodoList[title] = task
-end
-</code></pre>
+<pre><code class="ruby" lang="ruby"><span class="keyword">def </span><span class="method">task_status</span> <span class="ident">title</span><span class="punct">,</span> <span class="ident">status</span>
+  <span class="ident">task</span> <span class="punct">=</span> <span class="constant">TodoList</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span>
+  <span class="ident">task</span><span class="punct">[</span><span class="symbol">:done</span><span class="punct">]</span> <span class="punct">=</span> <span class="ident">status</span>
+  <span class="constant">TodoList</span><span class="punct">[</span><span class="ident">title</span><span class="punct">]</span> <span class="punct">=</span> <span class="ident">task</span>
+<span class="keyword">end</span></code></pre>
 
-<p>So in fact all we added is a check whether a task already exists, set an
-error-message in case it doesn't and redirect to wherever the browser came from.</p>
+<p>So in fact all we added is a check whether a task already exists, set an error-message in case it doesn&#8217;t and redirect to wherever the browser came from.</p>
 
-<p>But what about actually showing the error-messages we so carefully set? Well,
-where do we change the view? Right, in the templates. But both templates we have
-so far (index and new) share this behaviour, so we head over to the Element
-and add in the right place:</p>
+<p>But what about actually showing the error-messages we so carefully set? Well, where do we change the view? Right, in the templates. But both templates we have so far (index and new) share this behaviour, so we head over to the Element and add in the right place:</p>
 
 <pre><code>&lt;body&gt;
   &lt;h1&gt;#{@title}&lt;/h1&gt;
   &lt;?r if flash[:error] ?&gt;
-    &lt;div class="error"&gt;
-      \#{flash[:error]}
+    &lt;div class=&quot;error&quot;&gt;
+      \\#{flash[:error]}
     &lt;/div&gt;
   &lt;?r end ?&gt;
   #{content}
-&lt;/body&gt;
-</code></pre>
-
-<p>The only thing special about it is the <code>\#{flash[:error]}</code>, we have to escape
-the <code>#</code> so it won't evaluate this immediately but wait until it is really
-rendered.
-As a note, If you read this as pure markaby, the double backslash is to output
-properly to HTML, just use one instead.
-Again, you can add some nifty style for that.</p>
-
-<p>To be continued...</p>
-    </body>
-  </html>
+&lt;/body&gt;</code></pre>
+
+<p>The only thing special about it is the <code>\\#{flash[:error]}</code>, we have to escape the <code>#</code> so it won&#8217;t evaluate this immediately but wait until it is really rendered. As a note, If you read this as pure markaby, the double backslash is to output properly to HTML, just use one instead. Again, you can add some nifty style for that.</p>
+
+<p>To be continued&#8230;</p>
+</body></html>