nitro 0.20.0 → 0.21.0

data/doc/LICENSE

@@ -1,6 +1,6 @@
 The BSD License
 
-Copyright (c) 2004-2005, George 'tml' Moschovitis.
+Copyright (c) 2004-2005, George 'gmosx' Moschovitis. (http://www.gmosx.com)
 Copyright (c) 2004-2005, Navel Ltd. (http://www.navel.gr)
 All rights reserved.
 
@@ -10,11 +10,11 @@ met:
 
 * Redistributions of source code must retain the above copyright 
 notice, this list of conditions and the following disclaimer.
-	
+  
 * Redistributions in binary form must reproduce the above copyright 
 notice, this list of conditions and the following disclaimer in the 
 documentation and/or other materials provided with the distribution.
-	
+  
 * Neither the name of Navel nor the names of its contributors may be 
 used to endorse or promote products derived from this software 
 without specific prior written permission.

data/doc/MIGRATION

@@ -0,0 +1,28 @@
+= Migration
+
+Nitro and Og are under constant development. Some times we 
+really have to introduce features that break the compatibility 
+with older versions. This documents describes the required 
+steps to port your application to the latest Nitro version.
+
+For more help, send your question to the mailing list:
+
+http://rubyforge.org/mailman/listinfo/nitro-general
+
+== 0.21.0 <- 0.20.0
+
+1. The helper methods for starting the application and defining
+the compilation pipeline have changed. Have a look at 
+'examples/blog/run.rb' for an example.
+
+2. The conventions for the generated join table for many_to_many
+have changed, you may have to regenerate your schema.
+
+3. The builder functionality is provided by mixins now.
+
+4. The markup interpolators have changed. Instead of {{..}} use
+#(..) (sanitize) or #|..| (full markup). For details have a look
+at lib/nitro/compiler/markup.rb
+
+5. Actions no longer automatically redirect to the referer if the
+output buffer is empty. You have to manually redirect. There is an option to switch on the old behaviour though.

data/doc/RELEASES

@@ -1,4 +1,175 @@
-== Version 0.20.0
+== Version 0.21.0
+
+Nitro goes from strength to strength as the community gets bigger.
+Great new features were introduced and a lot of effort 
+was spend on cleaning up Nitro's implementation and polishing
+'little things'. Many patches were contributed by the community
+to make this is a release you will love!
+
+Some notable changes:
+
+* New compiler pipeline replaces the obscure shader mechanism. A
+  compiler object is responsible for transforming a controller action
+  and or the associated xhtml templates to a special ruby method
+  that will respond to given urls with the action output. Using
+  the aspect oriented features of Nitro or the specialized pipeline
+  setup method a developer can easily customize the compilation
+  stage to meet his needs. Here are some examples:
+  
+  Compiler.setup_template_transformation do |template|
+    template = Elements.transform(template)
+    template = Localization.transform(template)
+    template = Markup.transform(template)
+    template = Template.transform(template)
+  end
+
+  or 
+  
+  Compiler.before "puts 'Compiling'", :on => :compile
+  Compiler.after "puts 'Template processed'", :on => :transform_template
+  Compiler.wrap Benchmark, :on => compile
+  Compiler.before :my_method, :on => compile
+  
+  Special rendering effects where never easier. If you need run
+  time effects, just intercept the Render object.
+    
+* Integrated the new configuration system that was previewed in 
+  the last release. All the configuration settings are now accessible
+  either through the owner class or from the global Configuration
+  variable using Ruby's metaprogramming features.
+  
+  Moreover, Nitro now dynamically decides the configuration mode
+  (debug, stage, live/production) from environment variables or
+  command line arguments so depolying your application is easier
+  than ever: just run svn update on the live server, the application
+  will grab the correct configuration parameters automatically.
+  Of course you can use svn's advanced features to rollback to 
+  earlier versions if you experience problems. The mode specific
+  configuration settings are defined either on ruby files or
+  yaml files or both.
+  
+  Point your browser to http:://my.app.com/settings to browse
+  the settings for your application.
+
+* Og dynamic queries. You can inject caclulated or join attributes
+  to your objects. Here is an example:
+  
+  class Item
+    property :quantity, Fixnum
+    property :unit_price, Float
+    
+    def initialize(quantity, unit_price)
+      @quantity = quantity
+      @unit_price = unit_price
+    end
+  end
+  
+  Item.create 2, 3.0
+  item = Item.find_one :select => 'quantity*unit_price as total_price'
+  item.total_price # => 6.0
+  
+  Please note that total_price is a dynamically injected 
+  attribute. Now you can combine SQL's powerful query features
+  with the simplicity and elegance of Og.
+
+* Og customized join tables allows you to use any Ruby object
+  as the join relation between other objects. Here comes an 
+  example:
+  
+  class Category
+    property :title, String
+  end
+
+  class Article
+    property :title, String
+  end
+  
+  class ArticleToCategory
+    property :rate, Float
+    has_one Article
+    has_one Category
+  end
+  
+  c1 = Category.create
+  c2 = Category.create
+
+  a = Article.create
+  a.categories.add(c1, :rate => 2.3) 
+  a.categories.add(c2, :rate => 1.2) 
+
+  for c in a.categories
+    p a.category_join_data(c).rate
+  end
+  
+* Og collections size() is now optimized.
+
+* Og join code support refactoring. The new code is easier to read,
+  more customizable and generates more efficient code by default.
+
+* Nitro automatically assings reasonable template_roots on
+  Controllers based on mount points. Moreover, the template_root
+  overloading feature was improved. If you cant to reuse an
+  existing controller but customize the view rendering by using
+  different templates for some actions, just assign a different
+  template root for this controller, and put the custom templates
+  inside that dir. The custom templates 'override' the templates
+  of the parent controller (templates for non customized actions
+  come from the parent's controller template_root). Creating
+  a library of reusable controllers (parts) was never easier.
+  
+* Major cleanup of the nitro source code, removed many files.
+
+* Greatly improved Wee integration makes Nitro the premium 
+  container for Wee components. Have a look at the updated
+  wee example.
+  
+* Improved builder mechanism for programmatic rendering. The new
+  builder resuses the controller helper mixins thanks to extensive
+  refactoring of the implementation. Here is an example:
+  
+  class MyController
+    def index
+      build do 
+        labels = ['George', 'Stella', 'Renos']
+        html {
+          head {
+            title 'A simple test'
+          }
+          body {
+            10.times {
+              strong 'Hello World'
+              i 'Hello World222'
+            }
+            select(:id => 'names') {
+              options :labels => labels, :selected => 1
+            }
+          }
+        }
+      end
+    end
+    
+* Improved helper integration. Helpers are now accessed either
+  as mixins or through the builder mechanism.
+  
+  #{form entity}
+  #{options :labels => [..], :values => [..], :selected => 1}
+  
+  or
+  
+  #{emit :form entity}
+  #{emit :options :labels => [..] ...}
+
+* Reimplemented the markup mixin to make this more flexible. You
+  can easily customize the markup logic that is applied by the
+  markup macros.
+
+* Updated the documentation.
+    
+* Fixed all reported or discovered bugs, many smaller 
+  improvements.
+
+  
+== Version 0.20.0 was released on 12-07-2005
 
 Another superb release! State of the art AJAX/Javascript support,
 Wee components / programmatic renderer integration, a beginners
@@ -9,91 +180,91 @@ http://www.nitrohq.com
 Some notable changes:
 
 * Ajax is THE buzzword at the moment, and Nitro provides the 
-	best support you can find. Nitro fully separates the behaviour
-	from the template using the behaviour.js library and allowing
-	for dynamic injection of ajax functionality. The generated code
-	contains clean html and all the javascript organized in a
-	single <script> block. Here is an example:
-	
-	in the Controller:
-	
-	def index
-		# Inject functionality to the DOM elements of the template.
-		
-		behaviour '#alert', %{
-			el.onclick = function() {
-				alert('Hello world');
-			}		
-		}	
-		auto_complete :country # convert to autocomplete field
-		live :live # convert to async link!
-		draggable :dragger, :revert => false
-	end		
-
-	def a_simple_action
-		puts 'LIVE!'
-	end
-	
-	def country_auto_complete # data for auto complete.
-		%{
-		<ul>
-		  <li>Greece</li>
-		  <li>England</li>
-		  ...
-		</ul>
-		}
-	end
-	
-	in the Template:
-	
-	<label>Enter a country:</label>
-	<input type="text" id="country" />
-	<div id="country_auto_complete" class="auto_complete"> </div>
-	
-	Behaviour example:<br />
-	<button id="alert">Click to alert</button>
-
-	Drag and Drop example:<br />
-	<div id="dragger">DRAG ME</div>
-
-	Live/Asynchonous request (AJAX) example:<br />
-	Here comes a <a id="live" href="a_simple_action">live link</a>.<br />
-	(Check out the log to see the action called in the background!)
-
-	All you have to do is define id's for your DOM elements. Here
-	comes the generated code:
-	
-	<label>Enter a country:</label>
-	...
-	(Check out the log to see the action called in the background!)
-
-	<script type="text/javascript">
-			var _behaviours = {
-			'#alert': function(el) { 
-			el.onclick = function() {
-				alert('Hello world');
-			}		
-			},'#country': function(el) { 
-			el.autocomplete = 'off';
-		 
-		  },'#live': function(el) { 
-				el.onclick = function() {
-					new Ajax.Request(el.href, {});
-					return false;
-				}
-			 }
-			}
-			Behaviour.register(_behaviours);		
-				
-			new Ajax.Autocompleter('country', 'country_auto_complete', 'country_auto_complete');
-			new Draggable('dragger', {revert:false});
-	</script>
-	
-	See how a normal <a> tag is converted transparently to an Ajax request.
-	The prototype, scriptacoulous and behaviour js libraries are used.
-
-	The ajax support in this release is a PREVIEW. Stay tuned for
-	major improvements (and some surprises) in the next version.
+  best support you can find. Nitro fully separates the behaviour
+  from the template using the behaviour.js library and allowing
+  for dynamic injection of ajax functionality. The generated code
+  contains clean html and all the javascript organized in a
+  single <script> block. Here is an example:
+  
+  in the Controller:
+  
+  def index
+    # Inject functionality to the DOM elements of the template.
+    
+    behaviour '#alert', %{
+      el.onclick = function() {
+        alert('Hello world');
+      }    
+    }  
+    auto_complete :country # convert to autocomplete field
+    live :live # convert to async link!
+    draggable :dragger, :revert => false
+  end    
+
+  def a_simple_action
+    puts 'LIVE!'
+  end
+  
+  def country_auto_complete # data for auto complete.
+    %{
+    <ul>
+      <li>Greece</li>
+      <li>England</li>
+      ...
+    </ul>
+    }
+  end
+  
+  in the Template:
+  
+  <label>Enter a country:</label>
+  <input type="text" id="country" />
+  <div id="country_auto_complete" class="auto_complete"> </div>
+  
+  Behaviour example:<br />
+  <button id="alert">Click to alert</button>
+
+  Drag and Drop example:<br />
+  <div id="dragger">DRAG ME</div>
+
+  Live/Asynchonous request (AJAX) example:<br />
+  Here comes a <a id="live" href="a_simple_action">live link</a>.<br />
+  (Check out the log to see the action called in the background!)
+
+  All you have to do is define id's for your DOM elements. Here
+  comes the generated code:
+  
+  <label>Enter a country:</label>
+  ...
+  (Check out the log to see the action called in the background!)
+
+  <script type="text/javascript">
+      var _behaviours = {
+      '#alert': function(el) { 
+      el.onclick = function() {
+        alert('Hello world');
+      }    
+      },'#country': function(el) { 
+      el.autocomplete = 'off';
+     
+      },'#live': function(el) { 
+        el.onclick = function() {
+          new Ajax.Request(el.href, {});
+          return false;
+        }
+       }
+      }
+      Behaviour.register(_behaviours);    
+        
+      new Ajax.Autocompleter('country', 'country_auto_complete', 'country_auto_complete');
+      new Draggable('dragger', {revert:false});
+  </script>
+  
+  See how a normal <a> tag is converted transparently to an Ajax request.
+  The prototype, scriptacoulous and behaviour js libraries are used.
+
+  The ajax support in this release is a PREVIEW. Stay tuned for
+  major improvements (and some surprises) in the next version.
 
 * Wee Components integration. Nitro now transparently integrates
   Wee components. This is truly a win-win situation. Wee applications
@@ -115,7 +286,7 @@ Some notable changes:
   end
   
   module MyControlllerMixin
-  	# gets automatically mixed in
+    # gets automatically mixed in
   end
   
   This works just like Og Mixins.
@@ -126,11 +297,11 @@ Some notable changes:
   Here is an example:
   
   class Render
-  	setting :template_extension, :default => 'xhtml', :doc => 'The default template extension'
+    setting :template_extension, :default => 'xhtml', :doc => 'The default template extension'
   end
 
   class Session
-  	setting :store, :default => 'memory', :doc => 'The session store'
+    setting :store, :default => 'memory', :doc => 'The session store'
   end
   
   You can configure the Application using ruby code or yaml files:
@@ -141,10 +312,10 @@ Some notable changes:
   or
   
   Render:
-  	template_extension: xhtml
+    template_extension: xhtml
   Session:
-  	store: drb
-  	
+    store: drb
+    
   You can access all defined settings:
   
   Configuration.settings.each { |s| ... }
@@ -162,58 +333,58 @@ Some notable changes:
   
   class HelloWorld
     def index 
-    	print 'Hello World'
+      print 'Hello World'
     end
     
     def add(val)
-    	print "added: #{val + 2}"
+      print "added: #{val + 2}"
     end
-	end
-	
-	App.start(HelloWorld)
+  end
+  
+  App.start(HelloWorld)
     
-	Now, point your browser to localhost:/ or localhost/add?val=2
-	
-	If you need the advanced controller functionality just extend
-	your published object from the Controller base class. The normal
-	heuristics to decide which method is safe to publish are aplied.
+  Now, point your browser to localhost:/ or localhost/add?val=2
+  
+  If you need the advanced controller functionality just extend
+  your published object from the Controller base class. The normal
+  heuristics to decide which method is safe to publish are aplied.
 
 * CherryPy-style dispatcher configuration, provides another way
-	to define mounting points for Controllers and published objects.
-	Here is an example:
-	
-	server = Server.new
-	server.root = MainController							# /
-	server.root.fora = ForaController					# /fora
-	server.root.wiki = WikiController					# /wiki
-	server.root.really.deep = DeepController	# /really/deap
+  to define mounting points for Controllers and published objects.
+  Here is an example:
+  
+  server = Server.new
+  server.root = MainController              # /
+  server.root.fora = ForaController          # /fora
+  server.root.wiki = WikiController          # /wiki
+  server.root.really.deep = DeepController  # /really/deap
 
 * Improved pager interface. Thanks to the new PagerMixin, presenting
-	paged lists is easier (and as efficient) than ever:
-	
-	items, pager = paginate(Article, :per_page => 5, :order => 'date DESC')
-	
+  paged lists is easier (and as efficient) than ever:
+  
+  items, pager = paginate(Article, :per_page => 5, :order => 'date DESC')
+  
 * Added better sql injection protection in Og sql stores.
 
 * Fixed Mysql store reconnect bug.
 
 * Og falls back to pure ruby adapters for Mysql and Postgres, to 
-	make it easier to run out of the box. Please, don't forget to 
-	switch to the natively compiled adapters for production sites.
+  make it easier to run out of the box. Please, don't forget to 
+  switch to the natively compiled adapters for production sites.
 
 * This is surely the most request feature: Nitro Step by Step
-	by James Britt, a beginers guide to Nitro. Available in the
-	brand-new, Nitro-powered, www.nitrohq.com Community wiki.
+  by James Britt, a beginers guide to Nitro. Available in the
+  brand-new, Nitro-powered, www.nitrohq.com Community wiki.
 
 * New examples: The totaly recoded and ultra cool ajax example,
-	a Wee/Nitro example and the new Hello world example.
+  a Wee/Nitro example and the new Hello world example.
 
 * Cleaned up a lot of source files.
-	
+  
 * Many, many, many bug fixes and small improvements. This release
-	fixes all reported bugs in the spirit of out zero-bug tolerance
-	philosophy.
-	
+  fixes all reported bugs in the spirit of out zero-bug tolerance
+  philosophy.
+  
 
 == Version 0.19.0
 
@@ -224,141 +395,141 @@ fixes.
 Some notable changes:
 
 * Og polymorphic relations. A groundbreaking feature made possible
-	by Og's unique design and Ruby's power. Let's use an example 
-	to explain the concept:
-	
-	class Comment
-		...
-		belongs_to Object # polymorphic marker
-	end
-	
-	class User
-		...
-		has_many Comment
-	end
-	
-	class Article
-		...
-		has_many Comment
-	end
-	
-	u = User.new
-	u.comments << User::Comment('Hello')
-	
-	a = Article.new
-	a.comments << Article::Comment('Wow!')
-	
-	User::Comment and Article::Comment where automatically created
-	by Og and are serialized in different tables (also automatically
-	created by Og). This is the	next step in DRY!
+  by Og's unique design and Ruby's power. Let's use an example 
+  to explain the concept:
+  
+  class Comment
+    ...
+    belongs_to Object # polymorphic marker
+  end
+  
+  class User
+    ...
+    has_many Comment
+  end
+  
+  class Article
+    ...
+    has_many Comment
+  end
+  
+  u = User.new
+  u.comments << User::Comment('Hello')
+  
+  a = Article.new
+  a.comments << Article::Comment('Wow!')
+  
+  User::Comment and Article::Comment where automatically created
+  by Og and are serialized in different tables (also automatically
+  created by Og). This is the  next step in DRY!
 
 * Og now supports inheritance using the well known Single Table
-	Inheritance pattern. Thanks to Og's advanced design the pattern
-	is fully encapsulated:
-	
-	class Document
-		...
-		schema_inheritance
-	end
-	
-	class Article < Document
-		..
-	end
-	
-	class Photo < Document
-		..
-	end
-	
-	Document.all # => includes Articles and Photos
-	Article.all # => only Articles
-	
-	User.documents # => Articles and Photos
-	User.documents(:type => Photo) # => only photos.
-
-	Btw, this feature is orthogonal to the polymorphic relations
-	feature just described, giving the developer great 
-	flexibility.
+  Inheritance pattern. Thanks to Og's advanced design the pattern
+  is fully encapsulated:
+  
+  class Document
+    ...
+    schema_inheritance
+  end
+  
+  class Article < Document
+    ..
+  end
+  
+  class Photo < Document
+    ..
+  end
+  
+  Document.all # => includes Articles and Photos
+  Article.all # => only Articles
+  
+  User.documents # => Articles and Photos
+  User.documents(:type => Photo) # => only photos.
+
+  Btw, this feature is orthogonal to the polymorphic relations
+  feature just described, giving the developer great 
+  flexibility.
 
 * Added SUPERB support for auto reloading, the new system 
-	can detect source changes everywhere! Based on original
-	code by Michael Neumann.
-		
+  can detect source changes everywhere! Based on original
+  code by Michael Neumann.
+    
 * Introduced the concept of Flash, a temporal store where
-	objects that should be kept alive for the next request are
-	saved.
+  objects that should be kept alive for the next request are
+  saved.
 
 * Recoded the Blog example to use the Elements system for 
-	shading instead of XSLT. The new code runs easier under Windows
-	(so the no_xsl_blog example is now removed). Here comes an 
-	example:
-	
-	<Page>
-		<Box>
-			Please login as an author by entering the blog password.
-			<br />
-			The password is: <b>#{Blog.password}</b>.
-		</Box>
-		
-		<Error>#@error</Error>
-		...
-	</Page>
-
-	The <Page> tag is supported by the Page Ruby class to do the
-	programmatic rendering of templates or logic code:
-	
-	class Page
-		def render
-			...
-		end
-	end
-
-	This system can be used to create a library of useful 
-	components to abstract common tasks.
-	
+  shading instead of XSLT. The new code runs easier under Windows
+  (so the no_xsl_blog example is now removed). Here comes an 
+  example:
+  
+  <Page>
+    <Box>
+      Please login as an author by entering the blog password.
+      <br />
+      The password is: <b>#{Blog.password}</b>.
+    </Box>
+    
+    <Error>#@error</Error>
+    ...
+  </Page>
+
+  The <Page> tag is supported by the Page Ruby class to do the
+  programmatic rendering of templates or logic code:
+  
+  class Page
+    def render
+      ...
+    end
+  end
+
+  This system can be used to create a library of useful 
+  components to abstract common tasks.
+  
 * The updated Blog example demonstrates how easy it is to write
-	webservices using Nitro and the experimental Service feature.
-	The code is so short, so lets paste it here:
-	
-	module BloggerApi
-		SBlog = Struct.new(:url, :blogid, :blogName)
-
-		def blogger__getUsersBlogs(appkey, username, password)
-			Blog.all.collect { |b| SBlog.new('http://www.gmosx.com', b.oid, b.title) }		
-		end
-	end
-
-	module MetaWeblogApi
-		def metaWeblog__newPost(blogid, username, password, content, publish)
-			entry = BlogEntry.new(content['title'], content['description'])
-			entry.blog = Blog[blogid]
-			entry.save
-			entry.oid
-		end	
-	end
-
-	module MovableTypeApi
-		SCategory = Struct.new(:categoryId, :categoryName)
-
-		def mt__getCategoryList(blogid, username, password)
-			blog = Blog[blogid]
-			blog.categories.collect { |c| SCategory.new(c.oid, c.title) }
-		end
-
-		def mt__setPostCategories(postid, username, password, categories)
-			cid = categories.first['categoryId']
-			BlogEntry.update(postid, "category_oid=#{cid}")
-			true
-		end
-	end
-	
-	class ApiController < Nitro::XmlRpcService
-		include BloggerApi
-		include MovableTypeApi
-		include MetaWeblogApi
-	end
-
-	That's all!
-	
+  webservices using Nitro and the experimental Service feature.
+  The code is so short, so lets paste it here:
+  
+  module BloggerApi
+    SBlog = Struct.new(:url, :blogid, :blogName)
+
+    def blogger__getUsersBlogs(appkey, username, password)
+      Blog.all.collect { |b| SBlog.new('http://www.gmosx.com', b.oid, b.title) }    
+    end
+  end
+
+  module MetaWeblogApi
+    def metaWeblog__newPost(blogid, username, password, content, publish)
+      entry = BlogEntry.new(content['title'], content['description'])
+      entry.blog = Blog[blogid]
+      entry.save
+      entry.oid
+    end  
+  end
+
+  module MovableTypeApi
+    SCategory = Struct.new(:categoryId, :categoryName)
+
+    def mt__getCategoryList(blogid, username, password)
+      blog = Blog[blogid]
+      blog.categories.collect { |c| SCategory.new(c.oid, c.title) }
+    end
+
+    def mt__setPostCategories(postid, username, password, categories)
+      cid = categories.first['categoryId']
+      BlogEntry.update(postid, "category_oid=#{cid}")
+      true
+    end
+  end
+  
+  class ApiController < Nitro::XmlRpcService
+    include BloggerApi
+    include MovableTypeApi
+    include MetaWeblogApi
+  end
+
+  That's all!
+  
 * Integrated an SQLite3 patch by Ghislain Mary.
 
 * Integrated PostgreSQL binary data patch by Michael Neumann.
@@ -377,41 +548,41 @@ patches.
 Some notable changes:
 
 * Some changes to make Webrick a valid solution for powering
-	a production server. The full page output caching was improved 
-	and support for daemonizing the server was added. Support
-	for running as a proxy target (behind an apache server) was also
-	added. 
-	
+  a production server. The full page output caching was improved 
+  and support for daemonizing the server was added. Support
+  for running as a proxy target (behind an apache server) was also
+  added. 
+  
 * Thread safe mode was added again in Og. This works nice with
-	the Webrick server.
-	
+  the Webrick server.
+  
 * New order macro in Og to set default ordering for each
-	entity. The has_many collections respects the order setting.
-	
+  entity. The has_many collections respects the order setting.
+  
 * Improved error reporting.
 
 * Support for template_root overloading. Lets say you have
-	the following Controller hierarchy:
-	
-	Controller > MyController > SpecificController.
-	
-	The template roots of the 3 controller are searched in reverse
-	order. So by adding a template file in the SpecificController
-	template root you can override a default action in the base
-	Controller. For convienience the base Controller points to
-	the Proto directory. This is experimental.
+  the following Controller hierarchy:
+  
+  Controller > MyController > SpecificController.
+  
+  The template roots of the 3 controller are searched in reverse
+  order. So by adding a template file in the SpecificController
+  template root you can override a default action in the base
+  Controller. For convienience the base Controller points to
+  the Proto directory. This is experimental.
 
 * Provide the examples as a separate distribution to make it
-	easier for Ruby newbies to find them.
+  easier for Ruby newbies to find them.
 
 * Bug fixes in the Elements system.
 
 * Improved the nitrogen generator command. Just run
 
-	nitrogen app ~/the/target/path
-	
-	to create a skeleton application.
-	
+  nitrogen app ~/the/target/path
+  
+  to create a skeleton application.
+  
 * Cleaned up some source files.
 
 
@@ -427,132 +598,132 @@ list for ideas and suggestions that made this version possible.
 Most notable Og additions:
 
 * Extremely clean source code. Better names are used thorougout.
-	Extra care was taken to make all features more orthogonal.
-	
+  Extra care was taken to make all features more orthogonal.
+  
 * Brand new relation mechanism. The 'enchanting' of entities 
-	(managed classes) happens in multiple passes to be more
-	flexible. Totaly separated graph/metadata creation and serialization
-	code generation. The Graph metadata can be used for advanced
-	scaffolding, testing and more.
+  (managed classes) happens in multiple passes to be more
+  flexible. Totaly separated graph/metadata creation and serialization
+  code generation. The Graph metadata can be used for advanced
+  scaffolding, testing and more.
 
 * Support for fully customizable primary keys. You are no longer
-	forced to use xxx_oid primary keys. Appart from the extra 
-	flexibility this feature provides, this is an essential step
-	towards the planed 'reverse engineering' mode that will allow the
-	use of existing schemas with Og.
-	
+  forced to use xxx_oid primary keys. Appart from the extra 
+  flexibility this feature provides, this is an essential step
+  towards the planed 'reverse engineering' mode that will allow the
+  use of existing schemas with Og.
+  
 * More elegant inspection mechanism. Example:
 
-	Article.relation(:user) # => Og::BelongsTo(...)
-	Article.relations # => [...]
-	Article.properties # => [...]
+  Article.relation(:user) # => Og::BelongsTo(...)
+  Article.relations # => [...]
+  Article.properties # => [...]
 
 * Joins_many relation, as an alias for one way, join table relations.
 
 * Support for 'active' collections. Active collection are
-	synchronized with the backend Store and provide a more elegant
-	interface and the opportunity for 'session' caching:
-	
-	article.comments << Comment.new
-	
-	instead of 
-	
-	article.add_comment(Comment.new) # this is also allowed though.
-	
-	p article.comments
-	p article.comments.size # the results of the first query is cached
+  synchronized with the backend Store and provide a more elegant
+  interface and the opportunity for 'session' caching:
+  
+  article.comments << Comment.new
+  
+  instead of 
+  
+  article.add_comment(Comment.new) # this is also allowed though.
+  
+  p article.comments
+  p article.comments.size # the results of the first query is cached
 
 * Eager relations.
 
-	comments = Article.comments(:include => User)
+  comments = Article.comments(:include => User)
 
-	for comment in comments
-		p comment.user.name
-	end
-	
-	Elegantly solves the N+1 query problem by using one join
-	query.
+  for comment in comments
+    p comment.user.name
+  end
+  
+  Elegantly solves the N+1 query problem by using one join
+  query.
 
 * No need for forward references when defining relations. Now,
-	the following code magically works:
-	
-	class User
-	  has_many Comment # works even though Comment is not defined!
-	end
-	
-	class Comment
-		belongs_to User
-	end
-	 
+  the following code magically works:
+  
+  class User
+    has_many Comment # works even though Comment is not defined!
+  end
+  
+  class Comment
+    belongs_to User
+  end
+   
 * Use inflection where possible to infer missing configuration
-	options. For example
-	
-	class Article
-		belongs_to User # infects relation name :user
-		...
-		
+  options. For example
+  
+  class Article
+    belongs_to User # infects relation name :user
+    ...
+    
 * New, lean and mean Store interface. The code needed to teach 
-	Og how to  serialize objects to backend store is dramatically
-	reduced. The new interface is SQL agnostic, so non SQL-RDBM's 
-	stores are possible.
-	
+  Og how to  serialize objects to backend store is dramatically
+  reduced. The new interface is SQL agnostic, so non SQL-RDBM's 
+  stores are possible.
+  
 * SQL agnostic querying interface, compatible with non-sql 
-	Stores. Here is an example:
-	
-	Article.find(
-		:condition => 'hits > 2 AND rate > 3', 
-		:order => 'title',
-		:offset => 30,
-		:limit => 10
-	)
+  Stores. Here is an example:
+  
+  Article.find(
+    :condition => 'hits > 2 AND rate > 3', 
+    :order => 'title',
+    :offset => 30,
+    :limit => 10
+  )
 
 * More elegant (and non-sql store compatible) way for selective 
-	updates:
+  updates:
 
-	article.title = 'Changed'
-	article.hits += 1
-	article.update(:title, :hits)
+  article.title = 'Changed'
+  article.hits += 1
+  article.update(:title, :hits)
 
 * New, in-memory store that support all features. This is a pure
-	ruby solution useful for experimentation. It will also serve
-	as the base for the forthcoming madeleine Store implementation.
+  ruby solution useful for experimentation. It will also serve
+  as the base for the forthcoming madeleine Store implementation.
 
 * Allow for multiple stores in one application. A great example,
-	mysql_to_psql is provided. This example uses Og's powerfull
-	features to automatically convert a Mysql database to a 
-	PostgreSQL database. Database migration was never easier.
-	
+  mysql_to_psql is provided. This example uses Og's powerfull
+  features to automatically convert a Mysql database to a 
+  PostgreSQL database. Database migration was never easier.
+  
 * Uses the excellent Facets utility collection to further
-	clenup and minimize the code.
+  clenup and minimize the code.
 
 * Managed classes or Entities should include the EntityMixin
-	or extend the Entity class. Example:
-	
-	class Article < Entity
-		..
-	end
-	
-	class Article 
-		include EntityMixin
-	end
-	
-	This is done to avoid the Module module like in earlier
-	versions of Og. However, Og is can infer the need to include
-	the Managed mixin in typical cases:
-	
-	class Article
-		property :title, String 
-		# when a property is defined Og automatically converts the
-		# class to an Entity
-	end
-	
-	class Article < AnExistingManagedEntity
-		# also includes the mixin
-		...
-		
-	class Article
-		include AModuleThatDefinesProperties
-		...
+  or extend the Entity class. Example:
+  
+  class Article < Entity
+    ..
+  end
+  
+  class Article 
+    include EntityMixin
+  end
+  
+  This is done to avoid the Module module like in earlier
+  versions of Og. However, Og is can infer the need to include
+  the Managed mixin in typical cases:
+  
+  class Article
+    property :title, String 
+    # when a property is defined Og automatically converts the
+    # class to an Entity
+  end
+  
+  class Article < AnExistingManagedEntity
+    # also includes the mixin
+    ...
+    
+  class Article
+    include AModuleThatDefinesProperties
+    ...
 
 * Improved support for og_delete interception.
 
@@ -564,35 +735,35 @@ the new features.
 And some Nitro additions:
 
 * Integrated the Facets library, and started donating some Glue
-	code to this project.
-	
+  code to this project.
+  
 * Integrated the Prototype object oriented javascript library.
 
 * Included a preview implementation of the new tag library 
-	system, called Elements. This is based on an original idea
-	by Dan Yoder. This feature is expected to change substantially
-	in the next version. In the meantime here is an example:
-	
-	<Page>
-	  Here is a <b>nice</b> page.
-	  <br />
-	  <Box>
-		  This is #{variable}.
-		  <?r if admin ?>
-		  	hello admin
-		  <?r end ?>
-		</Box>
-	</Page>
-	
-	The tags <Page> and <Box> automatically instantiate objects
-	of class Page and Box that handle the rendering. This is an
-	alternative to the XSLT templating system and can also be used
-	to implement some reusable components. The hierarchical structure
-	of the elements is available to each object to facilitate 
-	advanced rendering tricks. Just like the XSLT shader the Elements
-	transformation is preapplied to the page to avoid the overhead
-	at runtime.
-	
+  system, called Elements. This is based on an original idea
+  by Dan Yoder. This feature is expected to change substantially
+  in the next version. In the meantime here is an example:
+  
+  <Page>
+    Here is a <b>nice</b> page.
+    <br />
+    <Box>
+      This is #{variable}.
+      <?r if admin ?>
+        hello admin
+      <?r end ?>
+    </Box>
+  </Page>
+  
+  The tags <Page> and <Box> automatically instantiate objects
+  of class Page and Box that handle the rendering. This is an
+  alternative to the XSLT templating system and can also be used
+  to implement some reusable components. The hierarchical structure
+  of the elements is available to each object to facilitate 
+  advanced rendering tricks. Just like the XSLT shader the Elements
+  transformation is preapplied to the page to avoid the overhead
+  at runtime.
+  
 * Fixed many reported bugs.
 
 
@@ -605,45 +776,45 @@ James Britt for significantly contributing to this release.
 Most notable additions:
 
 * Aspect Oriented Programming support. This new system
-	is used to reimplement features such as Controller filters,
-	Og callbacks and Og observers. By using this unified
-	system you can now add Observers to controllers and use
-	a metalanguage for wraping Og object callbacks:
-
-	class Controller
- 		pre :force_login, :where => :prepend
- 		wrap Benchmark, :on => :index
- 		post :taraa, :on => login
-	end
+  is used to reimplement features such as Controller filters,
+  Og callbacks and Og observers. By using this unified
+  system you can now add Observers to controllers and use
+  a metalanguage for wraping Og object callbacks:
+
+  class Controller
+     pre :force_login, :where => :prepend
+     wrap Benchmark, :on => :index
+     post :taraa, :on => login
+  end
  
-	module Timestamped
- 		pre :on => :og_insert { |this| this.create_time = Time.now }
-		pre :on => :og_update { |this| this.update_time = Time.now }
-		pre :on => [:og_insert, :og_update] { |this| this.create_time = Time.now }
-	end
+  module Timestamped
+     pre :on => :og_insert { |this| this.create_time = Time.now }
+    pre :on => :og_update { |this| this.update_time = Time.now }
+    pre :on => [:og_insert, :og_update] { |this| this.create_time = Time.now }
+  end
 
-	This feature will be used extensivelly  in future versions
-	to improve logging, the shaders and more.
+  This feature will be used extensivelly  in future versions
+  to improve logging, the shaders and more.
 
 * Added support for Test Driven Development. Many helpers
-	and utility methods are added to the standard TestCase
-	class, more will come in a future version:
-
-	handle(
-		'/login', 
-		request = { 'password' => Blog.password }
-	)
-	assert_redirect
-	assert_session_has(:owner)
-	assert_session_equal(:username, 'George Moschovitis')
-	assert_has_cookie('nauth')
-	assert_has_no_cookie('wow')
-	assert_cookie_equal('nauth', 'just an example, not used :)')
+  and utility methods are added to the standard TestCase
+  class, more will come in a future version:
+
+  handle(
+    '/login', 
+    request = { 'password' => Blog.password }
+  )
+  assert_redirect
+  assert_session_has(:owner)
+  assert_session_equal(:username, 'George Moschovitis')
+  assert_has_cookie('nauth')
+  assert_has_no_cookie('wow')
+  assert_cookie_equal('nauth', 'just an example, not used :)')
 
 * CGI adapter (by James Britt)
 
 * Major cleanup of the source. Converted the N namespace to
-	Nitro, to be more compatible with other Ruby projects. 
+  Nitro, to be more compatible with other Ruby projects. 
 
 * Add Og Timestamped mixin.
 
@@ -668,17 +839,17 @@ Most notable additions:
 
 * Advanced localization support:
 
-	locale_en = {
-		'See you' => 'See you',
-		:long_paragraph => 'The best new books, up to 30% reduced price',
-		:price => 'Price: %d %s',
-		:proc_price => proc { |value, cur| "Price: #{value} #{cur}" }
-	}
+  locale_en = {
+    'See you' => 'See you',
+    :long_paragraph => 'The best new books, up to 30% reduced price',
+    :price => 'Price: %d %s',
+    :proc_price => proc { |value, cur| "Price: #{value} #{cur}" }
+  }
 
-	locale_de = {
-		'See you' => 'Auf wieder sehen',
-		...
-	}
+  locale_de = {
+    'See you' => 'Auf wieder sehen',
+    ...
+  }
 
   lc = Localization.get
   lc['See you'] -> See you
@@ -688,8 +859,8 @@ Most notable additions:
  
   Using the LocalizationShader you can have templates like this:
 
-	<h1>[[This is a localized]] String</h1>
-	<p>
+  <h1>[[This is a localized]] String</h1>
+  <p>
      do you [[:like]] this?
   </p>
 
@@ -698,12 +869,12 @@ Most notable additions:
   blog example.
 
 * Dynamic/Parametrised mixins. A great extension to Ruby's mixin
-	feature. The Og::list implementation is replaced with the new
+  feature. The Og::list implementation is replaced with the new
   Orderable dynamic mixin, here is an example:
 
   class Comment
     property :body, String
-		belongs_to :article, Article
+    belongs_to :article, Article
     include Orderable, :scope => article
   end
 
@@ -716,22 +887,22 @@ Most notable additions:
 * NestedSets mixin:
 
   class Comment
-		include NestedSets
-	end
+    include NestedSets
+  end
 
-	or
+  or
 
-	class Comment
-		include Hierarchical, :method => :nested_sets
-	end
+  class Comment
+    include Hierarchical, :method => :nested_sets
+  end
 
-	c.add_comment(child_comment)
-	c.full_children
-	c.direct_children
-	c.children
+  c.add_comment(child_comment)
+  c.full_children
+  c.direct_children
+  c.children
  
-	this is a reimplementation of the SqlTraversable mixin
-	available in older versions.
+  this is a reimplementation of the SqlTraversable mixin
+  available in older versions.
 
 * Improved templating system. Now allows <% %> intrerpolators
   and provides a number of html morphing effects:
@@ -742,9 +913,9 @@ Most notable additions:
 
   <ul>
     <li each="u in @users">#{u.first_name} #{u.last_name}
-	</ul>
+  </ul>
 
-	and more...
+  and more...
 
 * Og provides an SqlServer adapter out of the box.
 
@@ -770,65 +941,65 @@ Most notable additions:
   whole pages (output caching), actions and fine-grained
   fragments. 
 
-	class MyController < Controller
-		cache_output :my_action
+  class MyController < Controller
+    cache_output :my_action
 
-		def my_action
-		end
-	end
+    def my_action
+    end
+  end
 
-	Stores the whole page created by the my_action method
-	to the disk to be displayed by the web server thus completely 
-	Nitro and Ruby.
+  Stores the whole page created by the my_action method
+  to the disk to be displayed by the web server thus completely 
+  Nitro and Ruby.
 
-	or 
+  or 
 
-	<strong>Here is some cached code</strong>
-	<cache>
-		<ul>
-		<?r for a in Article.all ?>
-			<li>#{a.title}: #{a.body}</li>
-		<?r end ?>
-		</ul>
-	</cache>
+  <strong>Here is some cached code</strong>
+  <cache>
+    <ul>
+    <?r for a in Article.all ?>
+      <li>#{a.title}: #{a.body}</li>
+    <?r end ?>
+    </ul>
+  </cache>
 
-	or
+  or
 
-	<strong>Another one</strong>
-	<?r cache('variant', :admin => session[:admin]) do ?>
-		...
-	<?r end ?>
+  <strong>Another one</strong>
+  <?r cache('variant', :admin => session[:admin]) do ?>
+    ...
+  <?r end ?>
 
-	Cached fragments can be stored in memory, filesystem.
+  Cached fragments can be stored in memory, filesystem.
 
-	While this feature is fully operational, the API will be finalised in 
-	the next version.
+  While this feature is fully operational, the API will be finalised in 
+  the next version.
 
 * Introduced support for Og mixins. In this version a List
-	mixin is provided:
+  mixin is provided:
 
   class Article
-		has_many :comments, Comment, :order => 'position DESC'
-	end
+    has_many :comments, Comment, :order => 'position DESC'
+  end
 
-	class Comment
-		belongs_to :article, Article
-		acts_as_list :scope => :article
-	end
+  class Comment
+    belongs_to :article, Article
+    acts_as_list :scope => :article
+  end
 
-	An AR compatible API is provided. An alternative
-	API is planned for the near future to give you more choice.
+  An AR compatible API is provided. An alternative
+  API is planned for the near future to give you more choice.
 
 * Reimplemented filtering infrastructure, allows
   for inheritance, conditional application of filters
   (:only/:except) modifiers, more performant Filters
-	as Strings and more.
+  as Strings and more.
 
 * Fixed multipart support in fastcgi, added file upload
   example (tiny example).
 
 * The webrick adapter reuses the fastcgi infrastructure, making
-	the adapters more compatible with each other.
+  the adapters more compatible with each other.
 
 * Added many useful Og enchant methods.
 
@@ -850,35 +1021,35 @@ and an AJAX example are also included.
 
 * Introduced Mailer subsystem:
 
-	class MyMailer < Mailer
-		def registration_email(to, username, password)
-			@from = 'system@navel.gr'
-			@to = to
-			@subject = 'Registration information'
-			@body.username = username
-			@body.password = password
-		end
-	end
+  class MyMailer < Mailer
+    def registration_email(to, username, password)
+      @from = 'system@navel.gr'
+      @to = to
+      @subject = 'Registration information'
+      @body.username = username
+      @body.password = password
+    end
+  end
 
   the tempate (registration_email.xhtml):
 
-	Hello #{username}
+  Hello #{username}
 
   Thanks for registering, your password is '#{password}'
 
-	Then use it like this:
+  Then use it like this:
 
-	MyMailer.deliver_registration_email('gmosx@navel.gr', 'gmosx', 'rulez')
+  MyMailer.deliver_registration_email('gmosx@navel.gr', 'gmosx', 'rulez')
 
-	For more information, check out the updated blog example.
+  For more information, check out the updated blog example.
 
 * AJAX example, demonstrates how to use ajax techniques with 
-	Nitro. A simple Google Suggest style UI is implemented.
+  Nitro. A simple Google Suggest style UI is implemented.
 
 * Use a Rails compatible directory structure. Check out
-	the updated blog example. Please note that Nitro does not
-	force a directory structure (see an alternative structure
-	in the no_xsl_blog example).
+  the updated blog example. Please note that Nitro does not
+  force a directory structure (see an alternative structure
+  in the no_xsl_blog example).
 
 * Optional separate template_root/public_root for extra security.
 
@@ -894,82 +1065,82 @@ fixed aswell.
 Most notable additions:
 
 * Nitro allows the definition of metadata for each action.
-	Routing (rewrite) rules, parameter constrains, hierarchy information
-	and custom data can easily be attached to actions:
+  Routing (rewrite) rules, parameter constrains, hierarchy information
+  and custom data can easily be attached to actions:
 
-	def view
-		@entry = Article[@oid]
-	end
-	action :view, :route => /view\/(.*)/, 'oid' => 1
+  def view
+    @entry = Article[@oid]
+  end
+  action :view, :route => /view\/(.*)/, 'oid' => 1
 
-	just browse
+  just browse
 
-	view/1
+  view/1
 
-	and @oid is automatically initialized with request['oid']
+  and @oid is automatically initialized with request['oid']
 
-	Browse the source to see how to add additional constrains,
-	more is comming in the next version. This feature replaces 
-	the non portable ParseTree implementation. The scaffolder
-	is updated to generate routings for nice urls.
+  Browse the source to see how to add additional constrains,
+  more is comming in the next version. This feature replaces 
+  the non portable ParseTree implementation. The scaffolder
+  is updated to generate routings for nice urls.
 
 * Og automatically generates finders for all properties, for
-	even easier (and portable) querying:
+  even easier (and portable) querying:
 
-	class Article
-		property :title, :body, String
-		property :hits, Fixnum
-		property :create_time, Time
-	end
+  class Article
+    property :title, :body, String
+    property :hits, Fixnum
+    property :create_time, Time
+  end
 
-	you get the finders:
+  you get the finders:
 
-	Article.find_by_title
-	Article.find_by_body
-	Article.find_by_hits
-	Article.find_by_create_time
+  Article.find_by_title
+  Article.find_by_body
+  Article.find_by_hits
+  Article.find_by_create_time
 
-	The finders take into account the unique constrain, to return
-	an array or just an object as needed.
+  The finders take into account the unique constrain, to return
+  an array or just an object as needed.
 
 * Og introduces lifecycle observers to avoid 'poluting' the model
-	objects with excess functionality. You can use every object
-	as observer (duck typing) or extend from an AR style Observer
-	class. The observer callbacks are precompiled in the lifecycle
-	methods only if defined, so the perfomance is not affected
-	in the general case.
+  objects with excess functionality. You can use every object
+  as observer (duck typing) or extend from an AR style Observer
+  class. The observer callbacks are precompiled in the lifecycle
+  methods only if defined, so the perfomance is not affected
+  in the general case.
 
 * Factored out templating engine, can now be used in stand-alone
-	mode. Usefull for example to render email templates etc:
+  mode. Usefull for example to render email templates etc:
 
-		template = %q{
-			Hello #{user}
+    template = %q{
+      Hello #{user}
 
-			dont forget the following facts:
-			
-			<?r for item in items ?>
-				<li>#{item}</li>
-			<?r end ?>
-		}
+      dont forget the following facts:
+      
+      <?r for item in items ?>
+        <li>#{item}</li>
+      <?r end ?>
+    }
 
-		user = 'gmosx'
-		items = %w{ nitro is really great }
-		out = '' # the rendered template comes here.
+    user = 'gmosx'
+    items = %w{ nitro is really great }
+    out = '' # the rendered template comes here.
 
-		Template.process(template, :out, binding)
+    Template.process(template, :out, binding)
 
 * New options in the default runner: 
-	
-	--render crawls a web application and renders all pages
-	as static html files. Allows you to leverage Nitro's 
-	advanced templating features to generate static sites.
+  
+  --render crawls a web application and renders all pages
+  as static html files. Allows you to leverage Nitro's 
+  advanced templating features to generate static sites.
 
-	--crawl spiders the application, useful for testing.
+  --crawl spiders the application, useful for testing.
 
 * Better error page, with more information (see blog example).
 
 * Fixed Og bug: multiple many_to_many relations with the
-	same target class.
+  same target class.
 
 * further code cleanup, improved examples and more.
 
@@ -988,73 +1159,73 @@ Most notable additions:
 * Configuration files for Apache/FastCGI.
 
 * Og documentation (doc/og_tutorial.txt, doc/og_config.txt)
-	
+  
 * Actions with parameters:
 
   def list(username, oid)
-		...
-	end
+    ...
+  end
 
-	http://www.mysite.com/list?username=tml;oid=2
+  http://www.mysite.com/list?username=tml;oid=2
 
   calls list() with the correct parameters, no need to 
-	use request['oid'], just use oid.
+  use request['oid'], just use oid.
 
-	def list(username, oid)
-		puts oid # oid == request['oid']
-	end
+  def list(username, oid)
+    puts oid # oid == request['oid']
+  end
 
-	WARNING: this feature requires the ParseTree library which
-	is not compatible with Windows. For the moment, this feature 
-	is dissabled by default. To enable this feature, set 
-	Nitro.resolve_action_arguments = true.
+  WARNING: this feature requires the ParseTree library which
+  is not compatible with Windows. For the moment, this feature 
+  is dissabled by default. To enable this feature, set 
+  Nitro.resolve_action_arguments = true.
 
 * New session store system, DRb sessions (stored in an independent
-	DRb server) are reimplemented.
+  DRb server) are reimplemented.
 
-	Session.store_type = :drb
+  Session.store_type = :drb
 
 * TableBuilder helps in creating html tables.
 
 * Integrated builders with the programmatic render. For example:
 
-	<div class="mytable">
-		#{o.build_table(:id => 'my_tab', :headers => headers, :values => values)
-	</div>
+  <div class="mytable">
+    #{o.build_table(:id => 'my_tab', :headers => headers, :values => values)
+  </div>
 
-	or
-	
-	<p>
-		<b>Object Form</b>
-		#{o.build_form(obj)}
-	</p>
+  or
+  
+  <p>
+    <b>Object Form</b>
+    #{o.build_form(obj)}
+  </p>
 
 * Og Oracle adapter.
 
 * Og provides advanced metadata for the managed objects
 
-	class Article
-		property :title, String
-		property :body, String
-		has_many :comments, Comment
-	end
+  class Article
+    property :title, String
+    property :body, String
+    has_many :comments, Comment
+  end
 
-	par = Article.properties_and_relations
-	=> [Property(:title), Property(:body), Og::HasMany(:comments)]
+  par = Article.properties_and_relations
+  => [Property(:title), Property(:body), Og::HasMany(:comments)]
 
-	par[2].klass
-	=> Comment
+  par[2].klass
+  => Comment
 
-	par[2].meta[:linkback]
-	=> :article_oid
+  par[2].meta[:linkback]
+  => :article_oid
 
 * Og Typemacros, here is an example:
 
-	def VarChar(size)
-		return String, :sql => "NOT NULL VARCHAR(#{size})"
-	end
+  def VarChar(size)
+    return String, :sql => "NOT NULL VARCHAR(#{size})"
+  end
 
-	property :title, VarChar(30)
+  property :title, VarChar(30)
 
 * Option for faster startup, skip schema check.
 
@@ -1083,31 +1254,31 @@ Most notable additions:
   adapter subsystem.
 
 * New SQLite3 Og adapter, improvements in MySQL and PostgreSQL 
-	adapters (WARNING: needs version 1.1.0 of Sqlite3-Ruby).
+  adapters (WARNING: needs version 1.1.0 of Sqlite3-Ruby).
 
 * Added install.rb for easier installation of the tar.gz distribution.
 
 * Better GemSpec for easier installation by RubyGems.
 
 * Action/template/xsl auto-reloading system in debug mode,
-	new implementation, works again.
+  new implementation, works again.
 
 * New Nitro configuration system, with rational default
-	parameters.
+  parameters.
 
 * --console option attaches an irb session to a running
-	instace of an application (works again).
+  instace of an application (works again).
 
 * Og supports optional typechecking by using property metadata.
 
 * request alias for context to be compatible with older
-	versions of nitro and Webrick/jsp and other frameworks.
+  versions of nitro and Webrick/jsp and other frameworks.
 
 * Improved the examples, cleaner code, work from any
-	directory.
+  directory.
  
 * Removed more obsolete code and improved directory
-	structure.
+  structure.
 
 * and many more smaller fixes.
 
@@ -1150,27 +1321,27 @@ Most notable additions:
 * Drastically improved source code readability.
 
 * New abstract rendering pipeline. Benefits:
-	
-	* multiple adaptors.
-	* better unit tests.
-	* optimized memory allocation.
-	* more modular desing.
+  
+  * multiple adaptors.
+  * better unit tests.
+  * optimized memory allocation.
+  * more modular desing.
 
 * FastCGI support (tested with Lighttpd).
 
 * no_xsl_blog example.
 
-	This new example is easier to setup, even on Windows.
-	This also demonstrates that Nitro does NOT force
-	the use of XSLT.
+  This new example is easier to setup, even on Windows.
+  This also demonstrates that Nitro does NOT force
+  the use of XSLT.
 
 * No global variables used for nitro configuration.
 
 * Updated the docs to better reflect the rappidly
-	evolving codebase.
+  evolving codebase.
 
 * Og metalanguage relations insert metadata into 
-	the target class, useful for advanced scaffolders.
+  the target class, useful for advanced scaffolders.
 
 * Og refer_to meta-language command. 
 
@@ -1190,43 +1361,43 @@ Most notable additions:
 
 * New automatic validation system:
 
-	class User
-		prop_accessor :name, :password, String
-		validate_confirmation :password
-		validate_length :name, :range => 2..12
-	end
-
-	u = User.new(...)
-	unless u.valid?
-		p u.errors.on(:name)
-		p u.errors[:password]
-	end
-	
+  class User
+    prop_accessor :name, :password, String
+    validate_confirmation :password
+    validate_length :name, :range => 2..12
+  end
+
+  u = User.new(...)
+  unless u.valid?
+    p u.errors.on(:name)
+    p u.errors[:password]
+  end
+  
 * Programmatic xhtml rendering. This is an alternative
-	method of rendering that is usefull in building 
-	components and helpers. This is a preview implementation.
+  method of rendering that is usefull in building 
+  components and helpers. This is a preview implementation.
 
-	options = ['Male', 'Female']
-	o.select(:name => 'sex') { 
-		o.options(options, selected = 1) 
-	}
+  options = ['Male', 'Female']
+  o.select(:name => 'sex') { 
+    o.options(options, selected = 1) 
+  }
 
-	options = { 'Male' => 'm', 'Female' => 'f' }
-	o.select(:name => 'sex') { 
-		o.options(options, selected = 1) 
-	}
+  options = { 'Male' => 'm', 'Female' => 'f' }
+  o.select(:name => 'sex') { 
+    o.options(options, selected = 1) 
+  }
 
-	o.html {
-		o.p(:class => 'header') { o.b('Hello') }
-	}
+  o.html {
+    o.p(:class => 'header') { o.b('Hello') }
+  }
 
 * No global variables in Og. 
 
 * Recoded Og to allow for future support of multiple databases 
-	(even on different RDBMS systems) on a single application.
+  (even on different RDBMS systems) on a single application.
 
 * Improved Blog example demonstrates latest advancements.
-	(You have to drop the database of earlier versions!)
+  (You have to drop the database of earlier versions!)
 
 * More unit tests.
 
@@ -1238,7 +1409,7 @@ Most notable additions:
 
 * And many IMPORTANT bug fixes.
 
-	
+  
 == Version 0.7 was released on 27/12/2004.
 
 A snapshot of the latest code. Many fixes and new features result
@@ -1252,7 +1423,7 @@ Most notable additions:
 * Totaly recoded prop_accessor mechanism, avoids polution of the Module
   class.
 * prop_accessors for Modules, allows synthesizing of managed objects
-	from Mixins.
+  from Mixins.
 * new automatically generated methods in Og.
 * MockDatabase leverages the FlexMock object for easier unit testing.
 * Integrated the cool Breakpointer library by Florian Gross.