sws 0.4

data/doc/docbook/installation.docbook

@@ -0,0 +1,57 @@
+<chapter id="installation">
+	<title>Obtaining & installing SWS</title>
+
+	<sect1 id="installation-where-to-get">
+		<title>Where to get SWS?</title>
+
+		<para>You can get latest release of SWS from <ulink url="http://starware.one.pl/software/download/sws/sws-latest.tar.gz">http://starware.one.pl/software/download/sws/sws-latest.tar.gz</ulink>. The RubyGem for SWS can be obtained from <ulink url="http://starware.one.pl/software/download/sws/sws-latest.gem">http://starware.one.pl/software/download/sws/sws-latest.gem</ulink></para>
+
+	</sect1>
+
+	<sect1 id="installation-installation">
+		<title>Installation</title>
+
+		<para>The preferred way to install SWS is to use RubyGem. Just get the SWS gem and issue a command</para>
+		<programlisting>
+			gem -i sws-latest.gem
+		</programlisting>
+		<para>or install the gem remotely</para>
+		<programlisting>
+			gem -i sws
+		</programlisting>
+
+		<para>Alternatively you may just use setup.rb included in SWS tarball. Just run</para>
+		<programlisting>
+			ruby setup.rb config
+			ruby setup.rb setup
+			ruby setup.rb install
+		</programlisting>
+
+		<para>from the unpacked tarball directory.</para>
+
+		<important><para>
+				Remember - using RubyGem is now a preferred way to install SWS. Other ways of installation 
+				will be dropped in future versions.
+		</para></important>
+
+	</sect1>
+
+	<sect1 id="installation-upgrade">
+		<title>Upgrading from earlier version</title>
+
+		<sect2 id="installation-upgrade-0.2">
+			<title>From version 0.2.1 and above</title>
+			<para>
+				Just perform the installation as specified above.
+			</para>
+		</sect2>
+
+		<sect2 id="installation-upgrade-0.1">
+			<title>From versions 0.2 and below</title>
+			<para>You need to uninstall previous version - remove <replaceable>sws</replaceable> directory and <replaceable>sws.rb</replaceable> file from <replaceable>site_ruby</replaceable>. Remove <replaceable>data_dir/sws</replaceable> (usually <replaceable>/usr/share/sws</replaceable>) directory too. Then you can install the new version.</para>
+		</sect2>
+		
+	</sect1>
+
+</chapter>
+

data/doc/docbook/introduction.docbook

@@ -0,0 +1,130 @@
+<chapter id="introduction">
+	<title>Introduction</title>
+
+	<sect1 id="what-is-sws">
+		<title>What is SWS?</title>
+		
+		<para>SWS is a web development library for <ulink url="http://www.ruby-lang.org">Ruby programming language</ulink>. Its major design goal is to follow the Model-View-Controller pattern, to take the burden of parsing HTTP parameters and keeping the session information out of developer shoulders and to make web applications easier to write by using reusable components. It enables rapid development and easy maintaining of even complex web applications, such as database ones (together with database access library - <ulink url="http://www.starware.one.pl/software/sds/">SDS</ulink>.</para>
+		<para>SWS is modeled after Apple excellent <ulink url="http://www.apple.com/webobjects">WebObjects</ulink> web development environment. There is another Ruby library modelled after it - <ulink url="http://www.spice-of-life.net/download/cgikit/index_en.html">CGIKit</ulink> - you may want to check it out.</para>
+
+	</sect1>
+
+	<sect1 id="why-write-sws">
+		<title>Why another web development library?</title>
+		<itemizedlist>
+			<listitem><para>SWS is modelled after WebObjects, which still (despite its age) is one of the best designed and most developer-friendly web development library</para></listitem>
+			<listitem><para>SWS is designed to be used in cooperation with <ulink url="http://www.starware.one.pl/software/sds/">SDS</ulink> - a powerful database access and object persistence library, so it provides the major components you need to develop serious business applications</para></listitem>
+			<listitem><para>SWS follows strictly the Model-View-Controller pattern, so the code is clear and can be easy maintained</para></listitem>
+			<listitem><para>Session handling has some very powerful features and is performed with no additional work for the developer</para></listitem>
+			<listitem><para>With SWS you no longer need to parse HTTP parameters - they are automatically parsed and bound to appropiate variables</para></listitem>
+			<listitem><para>The pages in SWS are created in object-oriented manner. SWS introduces the concept of <wordasword>component</wordasword> - a reusable and configurable element of HTML code</para></listitem>
+		</itemizedlist>
+
+		<para>I'm a web developer and have used a lot of different web development libraries. 
+			IMHO WebObjects is superior to all of them - there is so little code you need to write and it's so easy to maintain... 
+			Reading comp.lang.ruby newsgroup I see a lot of posts complaining about lack of enterprise-level application development libraries. 
+			Ruby is my language of choice since I first started learning it, so I thought I could learn something by implementing library similar to WebObjects and maybe somebody could benefit from my work. 
+			After all, this is what OpenSource is all about, isn't it? I know there is a lot of work before SWS could be used in business applications, but I am looking forward for the challenge :)
+		</para>
+
+	</sect1>			
+
+	<sect1 id="introduction-whats-new">
+		<title>What's new in this version</title>
+
+		<itemizedlist>
+
+			<listitem><para>Implemented parent (^) bindings.</para></listitem>
+
+			<listitem><para>Hack for favicon.ico to avoid unnecessary requests.</para></listitem>
+
+			<listitem><para>Much better backtrack handling (still not perfect yet) -
+					now a few last components are kept and restored when a request to one
+					of them comes by.</para></listitem>
+
+			<listitem><para>SessionCleaner - old sessions are now removed after
+					defined time. No more ever-increasing memory usage.</para></listitem>
+
+			<listitem><para>Improved handling of action components.</para></listitem>
+
+			<listitem><para>Created JSMenu component.</para></listitem>
+
+			<listitem><para>Added some slots to exisiting components.</para></listitem>
+
+			<listitem><para>Fixed a couple of bugs, two especially nasty - memory leak
+					and one in component tree creation on Content nested in
+					Content.</para></listitem>
+
+	</itemizedlist>
+	</sect1>
+	
+	<sect1 id="license">
+		<title>License</title>
+
+		<para>SWS is licensed under the Ruby license.</para>
+
+		<orderedlist>
+			
+			<listitem><para>You may make and give away verbatim copies of the source form of the
+     software without restriction, provided that you duplicate all of the
+		 original copyright notices and associated disclaimers.</para></listitem>
+
+ 			<listitem><para>You may modify your copy of the software in any way, provided that
+					you do at least ONE of the following:</para>
+
+				<orderedlist>
+					<listitem><para>place your modifications in the Public Domain or otherwise
+          make them Freely Available, such as by posting said
+				  modifications to Usenet or an equivalent medium, or by allowing
+					the author to include your modifications in the software.</para></listitem>
+
+					<listitem><para>use the modified software only within your corporation or
+          organization.</para></listitem>
+
+					<listitem><para>rename any non-standard executables so the names do not conflict
+					  with standard executables, which must also be provided.</para></listitem>
+
+					<listitem><para>make other distribution arrangements with the author.</para></listitem>
+				</orderedlist>
+			
+			</listitem>
+ 		
+			<listitem><para>You may distribute the software in object code or executable
+					form, provided that you do at least ONE of the following:</para>
+
+				<orderedlist>
+					<listitem><para>distribute the executables and library files of the software,
+					  together with instructions (in the manual page or equivalent)
+						on where to get the original distribution.</para></listitem>
+
+					<listitem><para>accompany the distribution with the machine-readable source of
+					  the software.</para></listitem>
+
+					<listitem><para>give non-standard executables non-standard names, with
+          instructions on where to get the original software distribution.</para></listitem>
+
+					<listitem><para>make other distribution arrangements with the author.</para></listitem>
+
+				</orderedlist>
+			</listitem>
+
+			<listitem><para>You may modify and include the part of the software into any other
+					software (possibly commercial).</para></listitem>
+
+			<listitem><para>The scripts and library files supplied as input to or produced as 
+		     output from the software do not automatically fall under the
+    		 copyright of the software, but belong to whomever generated them, 
+		     and may be sold commercially, and may be aggregated with this
+		     software.</para></listitem>
+
+		 	<listitem><para>THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
+		     IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
+    		 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+		     PURPOSE.</para></listitem>
+ 				
+		 </orderedlist>
+	</sect1>
+
+
+</chapter>
+

data/doc/docbook/sws_manual.docbook

@@ -0,0 +1,35 @@
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.2//EN" [
+	<!ENTITY introduction SYSTEM "introduction.docbook">
+	<!ENTITY installation SYSTEM "installation.docbook">
+	<!ENTITY concepts SYSTEM "concepts.docbook">
+	<!ENTITY tutorial SYSTEM "tutorial.docbook">
+	<!ENTITY todo SYSTEM "todo.docbook">
+]>
+<book>
+
+	<bookinfo>
+		
+		<title>The SWS User Guide</title>
+		
+		<authorgroup>
+			<author>
+				<firstname>Marek</firstname>
+				<surname>Janukowicz</surname>
+			</author>
+		</authorgroup>
+
+		<date>17.02.2006</date>
+		<releaseinfo>0.4</releaseinfo>
+
+		<abstract>
+			<para>This document describes architecture, concepts and the usage of <application>Starware Web System</application> (<application>SWS</application> for short) - the sophisticated web application development library for <ulink url="http://www.ruby-lang.org">Ruby programming language</ulink>. Current version describes the 0.4 version of SWS.</para>
+		</abstract>
+	</bookinfo>
+
+	&introduction;
+	&installation;
+	&concepts;
+	&tutorial;
+	&todo;
+	
+</book>

data/doc/docbook/todo.docbook

@@ -0,0 +1,38 @@
+<chapter id="todo">
+	<title>Bugs & future versions</title>
+
+	<sect1 id="todo-bugs">
+		<title>Known bugs & limitations</title>
+		<itemizedlist>
+			<listitem><para>Application must be started from the directory it is in</para></listitem>
+			<listitem><para>Multiple selection list components (CheckBoxList and Select) do not work properly when something is selected, submitted, all selections removed and submitted again</para></listitem>
+			<listitem><para>RadioButton component isn't of much use (but probably you would rather like to use RadioButtonList)</para></listitem>
+		</itemizedlist>
+	</sect1>
+
+	<sect1 id="todo-list">
+		<title>TODO list</title>
+		<itemizedlist>
+			<listitem><para>GUI tools (based on KDevelop and Quanta?)</para></listitem>
+			<listitem><para>GET requests</para></listitem>
+			<listitem><para>Allow the same instance of component to appear more than once of one page</para></listitem>
+			<listitem><para>Keep-alive</para></listitem>
+			<listitem><para>Concurrent request handling (probably thread-based, but current Ruby thread implementation sucks :/</para></listitem>
+			<listitem><para>Framework dependencies</para></listitem>
+			<listitem><para>Keeping session ids in URL</para></listitem>
+			<listitem><para>Multipart/mixed type form handling</para></listitem>
+			<listitem><para>Access control to resources</para></listitem>
+		</itemizedlist>
+	</sect1>
+
+	<sect1 id="final-word">
+		<title>Final word</title>
+
+		<para>Even a good library sucks without proper documentation, so I spent a lot of time trying to write this document and the examples. If you are a developer who was ever forced to wrote any documentation you can imagine how painful it was for me :) 
+			The documentation is surely lacking at some points, so if you see any room for improvement PLEASE <ulink url="mailto:marek@janukowicz.net">contact me</ulink>. 
+			I would really love to hear from you with any questions, suggestions, praises or blames you may have. If you like SWS, you can easily help me improving it just by dropping me an email.
+			If you don't like it, please let me know so I can stop wasting my time :)</para>
+	</sect1>
+
+</chapter>
+				

data/doc/docbook/tutorial.docbook

@@ -0,0 +1,594 @@
+<chapter id="tutorial">
+	<title>Tutorial</title>
+
+	<sect1 id="tutorial-intro">
+		<title>Introduction</title>
+		
+		<para>The information given in previous chapters may be a bit scarying, so better let's try to write a simple application to convince ourselves that SWS is in fact easy and friendly :) We will write a trivial addressbook application - it will be by no means complete, but should give an overview of writing SWS applications.</para>
+		<para>
+			Our application will show a set of address cards. The cards will be stored in a YAML file - a hash of address cards per user. The user will first have to log in (only username, no password) and then he will have his cards presented. He will have choice to add, edit, delete cards and show cards details.
+		</para>
+		
+	</sect1>
+
+	
+	<sect1 id="tutorial-create-application">
+		<title>Create the Addressbook application</title>
+
+		<sect2 id="tutorial-application-config">
+			<title>Application config file</title>
+
+		<para>
+			First, create <replaceable>addressbook</replaceable> directory - this will be the main application directory. Enter it and create application config file named <replaceable>application.yaml</replaceable>. 
+			The listing below presents the contents of the file - let me explain it a bit. First, we declare components (2 of them) - first one is called <replaceable>LoginPage</replaceable> and will be placed in <replaceable>Login</replaceable> dir, second one - called <replaceable>CardBrowse</replaceable> will be placed in <replaceable>CardBrowse</replaceable> dir. 
+			Then we load the Core framework, containing standard SWS components (like form elements etc.). Our application is a standalone one, so we set the <replaceable>adaptor_class</replaceable> to <replaceable>SWS::Adaptor::Standalone</replaceable> (in fact, this is the default). 
+			We will use our custom session class (named Session), so we declare it here. New sessions should start on LoginPage page, so we set <replaceable>default_component_class</replaceable> to LoginPage.
+		</para>
+		
+		<para>
+			Important note: remember the YAML file should be intended using spaces, not tabs! If you will use tabs (or let your editor use it) you will get parsing error.
+		</para>
+		
+		<figure>
+		<title>application.yaml file</title>
+			<programlisting>
+<![CDATA[
+components:
+  LoginPage: Login
+  CardBrowse: CardBrowse
+frameworks:
+  Core: SYSTEM/sws/Core
+adaptor_class: SWS::Adaptor::Standalone
+session_class: Session
+default_component_class: LoginPage
+]]>
+			</programlisting>
+		</figure>
+
+	</sect2>
+
+	<sect2 id="tutorial-application-rb-file">
+		<title>Application Ruby file</title>
+		
+		<para>Now we will create main application Ruby file. Create file <replaceable>addressbook.rb</replaceable> with the contents presented below. 
+			Let me explain it a bit - after the obvious <replaceable>require</replaceable> clause we define our custom <replaceable>Application</replaceable> class (we don't need it at this point - <replaceable>SWS::Application</replaceable> would be enough) and custom <replaceable>Session</replaceable> class (we will add some methods and attributes later). Then we create Application instance and start it.
+		</para>
+		
+		<figure>
+		<title>addressbook.rb file</title>
+			<programlisting>
+<![CDATA[
+#!/usr/bin/env ruby
+
+require 'sws'
+
+class Application < SWS::Application
+end
+
+class Session < SWS::Session
+end
+
+Application.new.run()
+]]>
+			</programlisting>
+		</figure>
+
+		<para>
+			Now we can start the application. Just run "ruby addressbook.rb" and point your WWW browser to <ulink url="http://localhost:1234/">http://localhost:1234/</ulink> (1234 is the default port of SWS applications). We don't have all files necessary to run the application yet, so you'll get an exception page with "RuntimeError: Cannot find component files for component LoginPage" message. 
+		</para>
+		
+	</sect2>
+
+	<sect2 id="tutorial-first-component">
+		<title>First component</title>
+
+		<para>
+			The time has come to create first component. Create <replaceable>Login</replaceable> directory, create a <replaceable>LoginPage.html</replaceable> file inside and open it in your favorite editor. 
+			The file contains HTML template for the component. This is our login page, so we'll create a trivial HTML form. All form elements (<replaceable>login_form</replaceable>, <replaceable>login_textfield</replaceable> and <replaceable>login_submit</replaceable>) are SWS components (note the <replaceable>sws</replaceable> attribute).
+		</para>
+
+		<figure>
+			<title>LoginPage.html file</title>
+			<programlisting>
+<![CDATA[
+<html>
+	<head><title>Login page</title></head>
+	<body>
+		<center><h2>Please, log in</h2></center>
+		<form sws="login_form">
+			<table align="center">
+				<tr><td><input type="text" sws="login_textfield"></td></tr>
+				<tr><td><input type="submit" sws="login_submit"></td></tr>
+			</table>
+		</form>
+	</body>
+</html>
+]]>
+			</programlisting>
+		</figure>
+
+		<para>
+			Now, create <replaceable>LoginPage.rb</replaceable> file in the same directory. This file contains Ruby class for the component. We need writeable attribute for login name (named - surprise, surprise - <replaceable>login_name</replaceable>) and a method we will call on login attempt (<replaceable>perform_login</replaceable>). The method needs to return a component - for now it returns <replaceable>self</replaceable>, as we do not have other components yet.
+		</para>
+		
+		<figure>
+			<title>LoginPage.rb file</title>
+			<programlisting>
+<![CDATA[
+class LoginPage < SWS::Component
+
+	attr_accessor :login_name
+
+	def perform_login ()
+		
+		puts( "Login name entered: #{@login_name}" )
+		@login_name = "try again"
+		return self
+
+	end
+
+end
+]]>
+			</programlisting>
+		</figure>
+
+		<para>
+			The next step is to create <replaceable>LoginPage.sws</replaceable> file. The file contains subcomponents bindings - defines how the component Ruby object attributes map to slots of the components present on the template. We connect <replaceable>login_name</replaceable> attribute to <replaceable>value</replaceable> slot of <replaceable>login_textfield</replaceable> subcomponent, <replaceable>perform_login</replaceable> method to <replaceable>action</replaceable> slot of <replaceable>login_submit</replaceable> subcomponent and use a literal string "Log in" as <replaceable>value</replaceable> of the same subcomponent.
+		</para>
+
+		<figure>
+			<title>LoginPage.sws file</title>
+			<programlisting>
+<![CDATA[
+login_form:
+  _class: SWS::Form
+
+login_textfield:
+  _class: SWS::TextField
+  value: login_name
+
+login_submit:
+  _class: SWS::SubmitButton
+  action: perform_login
+  value: "'Log in'" 
+]]>
+			</programlisting>
+		</figure>
+
+		<para>
+			Now we are ready to run the application again. This time you should be presented a simple login page. Try entering any text into textfield and check the console for messages. Congratulations, you now have a simple, but running, SWS application!.
+		</para>
+	</sect2>
+
+	</sect1>
+
+	<sect1 id="tutorial-logic">
+		<title>Business logic</title>
+
+		<para>
+			We will now take care of application business logic. Regular applications usually use a relational database for this purpose, so a O-R mapping library like <ulink url="http://www.starware.one.pl/software/sds/">SDS</ulink> can be very helpful. But for now we'll stick to a simple YAML file. We need several steps to introduce business logic to our application.
+		</para>
+
+		<para>
+			First, add reading and/or creating the address cards "database"  to application constructor. Also implement a method to access the database. Note we don't need to <replaceable>require</replaceable> YAML, as SWS uses it internally, so it is already loaded. We also create method to save the database abck to the file.
+		</para>
+
+		<figure>
+			<title>Additions to Application class - address cards database</title>
+			<programlisting>
+<![CDATA[
+class Application < SWS::Application
+
+	attr_reader :db
+
+	def initialize ( *args )
+		
+		super( *args )
+		if ( File.exist?( "db.yaml" ) )
+			@db = YAML.load( File.open( "db.yaml" ) )
+		else
+			@db = Hash.new
+		end
+
+	end
+	
+	
+	def save_db ()
+		File.open( "db.yaml","w" ) { |file|	file.write( @db.to_yaml ) }
+	end
+
+end
+]]>
+			</programlisting>
+		</figure>
+
+		<para>
+			We need to store user name and his address cards in a session object, so that we can easily access it on every page the user access. The <replaceable>entries()</replaceable> method retrieves user entries from database stored in Application instance, or creates an empty table if no entries found. We also implement custom writer for the <replaceable>username</replaceable> attribute, so the entries table is reset when the username is set (this can useful when the user changes, eg. when he logs out and in again).
+		</para>
+		
+		<figure>
+			<title>Additions to Session class - username and entries</title>
+			<programlisting>
+				
+<![CDATA[
+class Session < SWS::Session
+
+	attr_reader :username
+
+	def entries ()
+		
+		if ( @entries )
+			return @entries
+		else
+			
+			@entries = Application.instance.db[@username]
+			unless ( @entries )
+				@entries = Array.new
+				Application.instance.db[@username] = @entries
+			end
+			return @entries
+			
+		end
+
+	end
+
+
+	def username= ( username )
+		
+		@entries = nil
+		@username = username
+		
+	end
+	
+
+end
+]]>
+			</programlisting>
+		</figure>
+		
+		<para>
+			We will also need a custom Struct subclass for keeping address card info. We can just add it to the addressbook.rb file.
+		</para>
+		<figure>
+			<title>AddressCard struct</title>
+			<programlisting>
+<![CDATA[
+AddressCard = Struct.new( :first_name, :last_name, :phone, :address )
+]]>
+			</programlisting>
+		</figure>
+
+		<para>
+			Now we have all we need to handle business logic for our simple application.
+		</para>
+	</sect1>
+	
+	<sect1 id="tutorial-login-show-cards">
+		<title>Login and show user address cards</title>
+
+		<sect2 id="tutorial-real-login">
+			<title>Real login</title>
+			<para>
+			We will now change our fake login into a real one. We need some changes to the LoginPage component - we will check if user entered any username. If yes, we will go to the CardBrowse page, otherwise we will present a message.
+			</para>
+			<para>
+			Note we don't have to close the <![CDATA[<SPAN>]]> tag for <replaceable>login_message</replaceable> component, but we do it for the sake of HTML validity.
+			</para>
+			<figure>
+				<title>Enhanced LoginPage.html file</title>
+				<programlisting>
+<![CDATA[
+...				
+	<body>
+		<center><h2><span sws="login_message"></span></h2></center>
+		<form sws="login_form">
+]]>
+				</programlisting>		
+			</figure>
+
+			<figure>
+				<title>Enhanced LoginPage.sws file</title>
+				<programlisting>
+<![CDATA[
+[add at the end of file]
+					
+login_message:
+  _class: SWS::String
+  value: login_message
+	]]>
+				</programlisting>
+			</figure>
+
+			<figure>
+				<title>Enhanced LoginPage.rb file</title>
+				<programlisting>
+<![CDATA[
+class LoginPage < SWS::Component
+
+	attr_accessor :login_name
+	attr_reader :login_message
+
+	def perform_login ()
+		
+		unless ( @login_name )
+			@login_message = "Please enter a username"
+			return self
+		else
+			return Component.create( "CardBrowse", @request )
+		end
+
+	end
+
+end
+
+	]]>
+				</programlisting>
+			</figure>
+			
+		</sect2>
+
+		<sect2 id="tutorial-card-browse">
+			<title>CardBrowse component</title>
+
+			<para>
+				We will now create CardBrowse component (we just created a reference to it in LoginPage.rb).
+				This component will display all cards of the logged in user. It will also contain links and buttons to perform basic operations (add,edit,delete) on the cards.
+			</para>
+
+			<para>
+				Create CardBrowse directory in main application directory. Create CardBrowse.html file inside - contents of the file is presented below. It a bit complicated, so let's try to clear it out a bit. 
+				After the common header we see a username and than a table displaying all AddressCards for the user (using a new component - repetition - that renders its contents multiple times, each time using next element from its <replaceable>list</replaceable> slot) - each entry contains first and last name and a couple of buttons - <wordasword>Edit</wordasword> and <wordasword>Add</wordasword>. 
+				First name is linked and clicking it will show full card details.Next table will appear only if a card was selected for edition or a new one is being added and the last table - only if a first name was clicked.
+			</para>
+			<para>
+				Note the <replaceable>type</replaceable> attributes of <![CDATA[<INPUT>]]> tags are completely optional - SWS ignores them and renders the component depending only of bindings defined in .api file.
+			</para>
+			<figure>
+				<title>CardBrowse.html file</title>
+				<programlisting>
+<![CDATA[
+<html>
+	<head><title>Address card browsing</title></head>
+	<body>
+		<center><h2>User <span sws="username"></span></h2></center>
+		<form sws="browse_form">
+			<table border=1>
+				<tr><th>First name</th><th>Last name</th><th>Actions</th></tr>
+				<span sws="entries_repetition">
+					<tr>
+						<td><a sws="show_details_link"><span sws="cursor_first_name_string"></span></a></td>
+						<td><span sws="cursor_last_name_string"></span></td>
+						<td><input type="submit" sws="edit_card_button"><input type="submit" sws="delete_card_button"></td>
+					</tr>
+				</span>
+				<tr><td colspan=3><input type="submit" sws="add_card_button"></td></tr>
+				<tr><td colspan=3><input type="submit" sws="save_changes_button"></td></tr>
+			</table>
+		</form>
+
+		<div sws="show_edit_conditional">
+			<form sws="edit_form">
+			<table border=1>
+				<tr><th>First name</th><td><input type="text" sws="edit_first_name_textfield"></td></tr>
+				<tr><th>Last name</th><td><input type="text" sws="edit_last_name_textfield"></td></tr>
+				<tr><th>Address</th><td><input type="text" sws="edit_address_textfield"></td></tr>
+				<tr><th>Phone</th><td><input type="text" sws="edit_phone_textfield"></td></tr>
+				<tr><td colspan=2><input type="submit" sws="commit_button"></td></tr>
+			</table>
+			</form>			
+		</div>
+
+		<div sws="show_details_conditional">
+			<table border=1>
+				<tr><th>First name</th><td><span sws="details_first_name_string"></span></td></tr>
+				<tr><th>Last name</th><td><span sws="details_last_name_string"></span></td></tr>
+				<tr><th>Address</th><td><span sws="details_address_string"></span></td></tr>
+				<tr><th>Phone</th><td><span sws="details_phone_string"></span></td></tr>
+			</table>
+				
+		</div>
+
+	</body>
+</html>
+	]]>
+				</programlisting>
+			</figure>
+
+			<para>
+				Then create CardBrowse.sws file. There are bindings defined for all components present on this page. 
+			</para>
+			
+			<figure>
+				<title>CardBrowse.sws file</title>
+				<programlisting>
+<![CDATA[
+username:
+  _class: SWS::String
+  value: session.username
+
+browse_form:
+  _class: SWS::Form
+
+entries_repetition:
+  _class: SWS::Repetition
+  list: session.entries
+  item: card_cursor
+
+show_details_link:
+  _class: SWS::Hyperlink
+  action: show_details
+
+cursor_first_name_string:
+  _class: SWS::String
+  value: card_cursor.first_name
+
+cursor_last_name_string:
+  _class: SWS::String
+  value: card_cursor.last_name
+
+edit_card_button:
+  _class: SWS::SubmitButton
+  value: "'Edit'"
+  action: edit_card
+
+delete_card_button:
+  _class: SWS::SubmitButton
+  value: "'Delete'"
+  action: delete_card
+
+add_card_button:
+  _class: SWS::SubmitButton
+  value: "'Add card'"
+  action: add_card
+
+save_changes_button:
+  _class: SWS::SubmitButton
+  value: "'Save changes'"
+  action: save_changes
+
+show_edit_conditional:
+  _class: SWS::Conditional
+  condition: edited_card
+
+edit_form:
+  _class: SWS::Form
+
+edit_first_name_textfield:
+  _class: SWS::TextField
+  value: edited_card.first_name
+
+edit_last_name_textfield:
+  _class: SWS::TextField
+  value: edited_card.last_name
+
+edit_address_textfield:
+  _class: SWS::TextField
+  value: edited_card.address
+
+edit_phone_textfield:
+  _class: SWS::TextField
+  value: edited_card.phone
+
+commit_button:
+  _class: SWS::SubmitButton
+  value: "'Commit'"
+	action: commit_card
+
+show_details_conditional:
+  _class: SWS::Conditional
+  condition: selected_card
+
+details_first_name_string:
+  _class: SWS::String
+  value: selected_card.first_name
+
+details_last_name_string:
+  _class: SWS::String
+  value: selected_card.last_name
+
+details_address_string:
+  _class: SWS::String
+  value: selected_card.address
+
+details_phone_string:
+  _class: SWS::String
+  value: selected_card.phone
+]]>
+				</programlisting>
+			</figure>
+
+			<para>
+				Next, create the CardBrowse.rb file. It contains a simple CardBrowse class, having a instance variable for repetition cursor, 2 variables for selected and edited card and a bunch of methods to call on button and link clicks.
+			</para>
+
+			<figure>
+				<title>CardBrowse.rb file</title>
+
+				<programlisting>
+<![CDATA[
+class CardBrowse < SWS::Component
+
+	attr_accessor :card_cursor
+	attr_reader :selected_card, :edited_card
+
+	def delete_card ()
+		
+		session.entries.delete( @card_cursor )
+		@selected_card = nil
+		@edited_card = nil
+
+		return self
+
+	end
+
+
+	def add_card ()
+
+		@edited_card = AddressCard.new
+		session.entries << @edited_card
+		@selected_card = nil
+
+		return self
+		
+	end
+
+
+	def edit_card ()
+
+		@edited_card = @card_cursor
+		@selected_card = nil
+
+		return self
+		
+	end
+
+
+	def show_details ()
+
+		@selected_card = @card_cursor
+		@edited_card = nil
+
+		return self
+
+	end
+
+
+	def commit_card ()
+
+		@selected_card = nil
+		@edited_card = nil
+
+		return self
+		
+	end
+
+
+	def save_changes ()
+
+		app.save_db()
+		return self
+
+	end
+
+end
+]]>
+				</programlisting>
+			</figure>
+		</sect2>
+		
+	</sect1>
+
+	<sect1 id="tutorial-summary">
+		<title>Summary</title>
+
+		<para>
+			We have now a simple, but running and complete SWS application. You can now mess around a bit and check if it works correctly.
+		</para>
+
+		<para>
+			The code for this tutorial can be found in examples/addressbook directory of SWS source tree.
+		</para>
+	</sect1>
+	
+</chapter>
+