<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" 
	"/usr/share/sgml/docbook/dtd/xml/4.1.2/docbookx.dtd" [
	<!ENTITY legal SYSTEM "legal.xml">
<!ENTITY appversion "0.14.0">
<!ENTITY manrevision "0.0.4">
<!ENTITY date  "May 03, 2005">
<!ENTITY app "<application>Screem</application>">

<!-- Information about the entities
	The legal.xml file contains legal information, there is no need to edit the file.
	Use the appversion entity to specify the version of the application.
	Use the manrevision entity to specify the revision number of this manual. 
	Use the date entity to specify the release date of this manual.
	Use the app entity to specify the name of the application. -->

]>

<!--
	(Do not remove this comment block.)
	Version: 0.0.4
	Last modified: May 05, 2005
	Maintainers:
	David A Knight <david@screem.org>
	
	Translators:
	(translators put your name and email here)
	-->


<!-- =============Document Header ============================= -->

<book id="index" lang="en">
	<!-- please do not change the id; for translations, change lang -->
	<bookinfo>                                      
		<title>Screem User Manual &manrevision;</title>
		<copyright>
			<year>2000</year>	
			<year>2001</year>
			<year>2002</year>
			<year>2003</year>
			<year>2004</year>
			<year>2005</year>
			<holder>David A Knight</holder>
		</copyright>
		<copyright>
			<year>2000</year>
			<year>2001</year>
			<holder>Matthew Colyer</holder>
		</copyright>
		
		<!-- translators: uncomment this:
			
			<copyright>
			<year>2002</year>
			<holder>ME-THE-TRANSLATOR (Latin translation)</holder>
		</copyright>
			
			-->
		
		<publisher>
			<publishername> SCREEM Development Team </publishername>
		</publisher>
		
		<authorgroup>
			<author>
				<firstname>David</firstname>
				<othername>A</othername>
				<surname>Knight</surname>
				<affiliation>
					<address><email>david@screem.org</email></address>
				</affiliation>
			</author>
		</authorgroup>
		
		<releaseinfo>
			This manual describes version &appversion; of &app;
		</releaseinfo>
		
	</bookinfo>
	<index>
		<indexterm zone="index">
			<primary>Screem</primary>
		</indexterm>
		<indexterm zone="index">
			<primary>screem</primary>
		</indexterm>
		<indexterm zone="index">
			<primary>HTML Editor</primary>
		</indexterm>
	</index>
	<!-- ============= Document Body ============================= -->
	<!-- ============= Introduction =================================== -->
	<preface id="preface">
		<title>Preface</title>
		&legal; <!-- This file contains link to license for the
			documentation (GNU FDL), and other legal stuff such as "NO
			WARRANTY" statement. Please do not change any of this. -->
	</preface>
	
	<part id="introduction">
		<title>Introduction</title>
		<chapter id="about">
			<title>About &app;</title>
			<para>
				<acronym>&app;</acronym> is a web site development environment.
				It's purpose is to increase productivity when constructing a site,
				by providing quick access to commonly used features. While it is
				written for use with the <ulink url="http://www.gnome.org">
					<acronym>GNOME</acronym></ulink>
				desktop environment in mind it does not specifically require you
				to be running it, just have the libraries installed.
			</para>
			<para>
				Development of &app; began in April 1999 with the initial
				goal of being a simple to use HTML editor.
				Since then it has continued to grow thanks to input from
				early and current users so that it provides a feature base
				unparalleled by it&apos;s Free Software / Open Source
				competitors.  We hope that as a user you will help us improve
				&app; even further by providing feedback, both good and bad
				experiences / suggestions contribute equally well.
				If you are a developer and wish to help by coding, or a
				translator / documenter then your contributions on those
				fronts will also be welcomed gratefully.
			</para>
			<para>
				Visit <ulink url="http://www.screem.org/news.php">www.screem.org</ulink>
				for the latest news about screem.
			</para>
		</chapter>
		<chapter id="requirements">
			<title>Requirements</title>
			<sect1 id="SystemRecs">
				<title>System Recommendations</title>
				<para>
					These specifications are just guidelines and 
					<application>&app;</application> will run on lower spec 
					systems.
				</para>
				<itemizedlist>
					<listitem>
						<para>1024x768 screen resolution</para>
					</listitem>
					<listitem>
						<para>128 Meg memory</para>
					</listitem>
				</itemizedlist>
			</sect1>
			<sect1 id="LibraryRequirements">
				<title>Library Requirements</title>
				<para>
					Unlike the system recommendations library requirements are
					mandatory and <application>&app;</application> will
					not run without them installed on your system.
				</para>
				<itemizedlist>
					<listitem><para>glib 2.6 or higher</para></listitem>
					<listitem><para>gtk+ 2.6 or higher</para></listitem>
					<listitem><para>libgnome 2.2.0 or higher</para></listitem>
					<listitem><para>libgnomeui 2.6.0 or higher</para></listitem>
					<listitem><para>libxml 2.4.3 or higher</para></listitem>	
					<listitem><para>libglade 2.3.0 or higher</para></listitem>
					<listitem><para>gconf 2.2.0 or higher</para></listitem>
					<listitem><para>gnome-vfs 2.8.0 or higher</para></listitem>
					<listitem><para>libgtkhtml-2.0 2.2.0 or higher</para></listitem>
					<listitem><para>libgnomeprint-2.2 2.2.0 or higher</para></listitem>
					<listitem><para>libgnomeprintui-2.2 2.2.0 or higher</para></listitem>
					<listitem><para>gtksourceview 1.1.90 or higher</para></listitem>
					<listitem><para>dbus 0.22 or higher (optional at build time)</para></listitem>
					<listitem><para>dbus-glib 0.22 or higher (optional at build time)</para></listitem>
					<listitem><para>enchant 1.1.6 or higher (optional at build time)</para></listitem>
				</itemizedlist>
			</sect1>
		</chapter>
	</part>
	
	<part id="usage">
		<title>Getting Started with Screem</title>
		<!-- ============= Getting Started ================================ -->
		<chapter id="starting">
			<title>Getting Started</title>
			<sect1 id="start-screem">
				<title>To start &app;</title>
				
				<para>
					You can start &app; in the following ways:
				</para>
				<variablelist>
					<varlistentry>
						<term>
							<guimenu>Applications</guimenu> menu</term>
						<listitem>
							<para>
								Choose 
								<menuchoice>
									<guisubmenu>
										Programming
									</guisubmenu>
									<guimenuitem>
										&app; Website Editor
									</guimenuitem>
								</menuchoice>
							</para>
						</listitem>
					</varlistentry>
					<varlistentry>
						<term>Command line</term>
						<listitem>
							<para>
								Type <command>screem</command>, then press
								<keycap>Return</keycap>.
							</para>
						</listitem>
					</varlistentry>
				</variablelist>
			</sect1>
			
			<sect1 id="quick-start">
				<title>To start editing html pages straight away</title>
				
				<para>
					Upon starting &app; for the first time a blank HTML
					document will be presented.  You can start editing this
					straight away, and save it to wherever you like.
				</para>
				<para>
					You can preview the results within &app; without having
					to start up a web browser by using the
					<guimenu>View</guimenu> menu.  Choose the
					<menuchoice>
						<guimenuitem>Preview</guimenuitem>
					</menuchoice> menu item..
				</para>
				<para>
					Of course the real power of &app; comes not when working
					on individual files, but on complete projects, which
					&app; refers to as a site.
				</para>
			</sect1>
			
		</chapter>
		
		<chapter id="create-pages">
			<title>Creating new pages</title>
			<para>
				There are two different ways of creating new pages / documents
				with &app;
			</para>
			<variablelist>
				<varlistentry>
					<term>From 
						<menuchoice>
							<guimenu>File</guimenu> 
							<guisubmenu>New</guisubmenu>
							<guimenuitem>New Document</guimenuitem>
						</menuchoice>. 
					</term>
					<listitem>
						<figure>
							<graphic fileref="figures/newdoc.png"  align="center" format="PNG"/>
						</figure>
						<para>
							This method will present you with the new
							page druid, and will guide you through providing
							the information needed for a new <acronym>HTML</acronym>
							page.
						</para>
						<para>
							After the druid closes the page will be created,
							if you provided a filename, the file will now
							exist, and be added to the current site if you
							are working on one.
						</para>
					</listitem>
				</varlistentry>
				<varlistentry>
					<term>From 
						<menuchoice>
							<guimenu>File</guimenu> 
							<guisubmenu>New</guisubmenu>
							<guimenuitem>New Blank Document</guimenuitem>
						</menuchoice>. 
					</term>
					<listitem>
						<figure>
							<graphic fileref="figures/newblankdoc.png"  align="center" format="PNG"/>
						</figure>
						<para>
							Sometimes you may not want to go through the
							page druid, especially when you don't want an
							<acronym>HTML</acronym> file, but a Javascript
							file, or <acronym>CSS</acronym> file.  For these
							occasions you can create a new blank document.
						</para>
						<para>
							No file will be created when you do this, and
							so you will need to provide a filename when you
							save the document.  The Document will be
							included in any site wide operations if you are
							working on one.
						</para>
					</listitem>
				</varlistentry>
				
			</variablelist>
		</chapter>
		
		<chapter id="create-site">
			<title>Working with Sites</title>
			<para>
				As mentioned in the &quot;Getting Started&quot; section the real
				power of &app; comes when you are working on a project rather than
				individual files.  So just how do you go about creating a project?
			</para>
			<sect1 id="new-site">
				<title>To create a new Site</title>
				<variablelist>
					<varlistentry>
						<term>From
							<menuchoice>
								<guimenu>Site</guimenu> 
								<guimenuitem>New Site</guimenuitem>
							</menuchoice> 
						</term>
						<listitem>
							<figure>
								<graphic fileref="figures/newsite1.png"  align="center" format="PNG"/>
							</figure>
							<para>
								The Site Druid window will then be displayed, and
								guide you through the necessary steps to create a
								new site. 
							</para>
						</listitem>
					</varlistentry>
					<varlistentry>
						<term>From 
							<menuchoice>
								<guimenu>File</guimenu>
								<guisubmenu>New</guisubmenu> 
								<guimenuitem>New Site</guimenuitem>
							</menuchoice> 
						</term>
						<listitem>
							<figure>
								<graphic fileref="figures/newsite2.png"  align="center" format="PNG"/>
							</figure>
							<para>  
								This will have the same effect as if
								you had used the <guimenu>Site</guimenu>
								menu.
							</para>
						</listitem>
					</varlistentry>
					<varlistentry>
						<term>Opening an existing folder</term>
						<listitem>
							<para>
								You can open any existing folder and
								&app; will create a site from this.
								see the following section on 
								<link linkend="open-site">Opening an existing site</link>
							</para>
						</listitem>
					</varlistentry>
					
				</variablelist>
			</sect1>
			
			<sect1 id="open-site">
				<title>Opening an existing site</title>
				<variablelist>
					<varlistentry>
						<term>From
							<menuchoice>
								<guimenu>Site</guimenu>
								<guimenuitem>Open</guimenuitem>
							</menuchoice>  
						</term>
						<listitem>
							<figure>
								<graphic fileref="figures/opensite1.png"  align="center" format="PNG"/>
							</figure>
							<para>
								This method will display the file 
								selector allowing you to choose a folder.
								This folder will then be opened as a site.
							</para>
						</listitem>
					</varlistentry>
					<varlistentry>
						<term>From 
							<menuchoice>
								<guimenu>Site</guimenu>
								<guimenuitem>Open Location</guimenuitem>
							</menuchoice>  
						</term>
						<listitem>
							<figure>
								<graphic fileref="figures/opensite2.png"  align="center" format="PNG"/>
							</figure>
							<para>
								This method will display a dialog allowing
								you to enter a <acronym>URL</acronym>
								to where the site is located.  This could
								be and <acronym>FTP</acronym> site, a
								WebDAV share, an <acronym>SFTP</acronym>
								connect, or any other method that is
								supported by <acronym>GNOME</acronym>
								<figure><graphic fileref="figures/opensitelocation.png"  align="center" format="PNG"/></figure>
							</para>
						</listitem>
					</varlistentry>
				</variablelist>
				<para>
					As mention previously if there is no
					&app; project file to be found in the
					folder the site settings dialog will
					be displayed for initial options to be
					specified.
				</para>
			</sect1>
		</chapter>
	</part>
	
	<part id="user-interface">
		<title>The Main Window</title>
		<partintro>
			<para>
				The following chapters will go into detail about
				each part of the user interface of &app; and provide
				information on the features available there in.
			</para>
		</partintro>
		<chapter id="editing-views">
			<title>Document Views</title>
			
			<para>
				&app; provides a number of methods of viewing the
				document currently being worked on.
			</para>
			
			<sect1 id="editor">
				<title>The Editor View</title>
				<para>
					From the <guimenu>View</guimenu> menu.  Choose the
					<menuchoice>
						<guimenuitem>Editor</guimenuitem>
					</menuchoice> menu item.
				</para>
				<figure>
					<graphic fileref="figures/editor.png"  align="center" format="PNG" scalefit="1"/>
				</figure>
				<para>
					The text editor based view is the main authoring section of &app;.
					It has all the usual features you find in <application>gedit</application>, the default <acronym>GNOME</acronym> text editor.  There are of
					course a number of extra features geared towards editing
					<acronym>HTML</acronym> / <acronym>XML</acronym> documents.
				</para>
				<sect2 id="editor-features">
					<title>Editor features</title>
					<variablelist>
						<varlistentry>
							<term>Context menu</term>
							<listitem>
								<para>
									In addition to the usual right click popup
									menu &app; adds options to save and close
									the current document.
								</para>
								<para>
									When working on <acronym>HTML</acronym> /
									<acronym>XML</acronym> documents an extra
									item is added at the top of the menu if the
									click occurs inside a tag.  This submenu will
									provide you with a method of inserting any
									valid attribute for the tag, along with a
									value.  The actual inserted value may just be
									the type of data the attribute requires rather 
									than any specific, e.g. CDATA.
								</para>
								<figure>
									<graphic fileref="figures/editor-context-menu.png"  align="center" format="PNG"/>
								</figure>
								<para>
									If a wizard has been loaded that supports an
									<acronym>HTML</acronym> / <acronym>XML</acronym>
									tag that has been clicked on, then an option
									to edit the tag in the wizard will also be
									provided.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Enhanced copy / paste support</term>
							<listitem>
								<para>
									As well as supporting copy / pasting of text,
									the editor also supports html that may be
									in the clipboard.  This means you could for
									instance select part of a page you are viewing
									in <application>Epiphany</application> and
									paste it directly into &app; without having
									to search through the source of the page you
									are viewing.  Other applications such as
									<application>Abiword</application> and
									<application>Gnumeric</application> can provide
									html when pasted into &app;
								</para>
								<para>
									The editor also has a special paste mode,
									which will encode the relevant characters
									as entities, so actual <acronym>HTML</acronym>
									can be shown in the page.
								</para>
								<para>
									These pasting features are available by selecting the following menu items:
								</para>
								<itemizedlist>
									<listitem>
										<para>
											<menuchoice>
												<guimenu>Edit</guimenu>
												<guimenuitem>Paste</guimenuitem>
											</menuchoice>
										</para>
									</listitem>
									<listitem>
										<para>
											<menuchoice>
												<guimenu>Edit</guimenu>
												<guimenuitem>Paste Encoded</guimenuitem>
											</menuchoice>
										</para>
									</listitem>
									<listitem>
										<para>
											<menuchoice>
												<guimenu>Edit</guimenu>
												<guimenuitem>Paste Unformatted</guimenuitem>
											</menuchoice>
										</para>
									</listitem>
								</itemizedlist>
								<figure>
									<graphic fileref="figures/editor-pasting.png"  align="center" format="PNG"/>
								</figure>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Select Context</term>
							<listitem>
								<para>
									When dealing with markup it can be useful to
									select the entire element block you are
									working on, for instance a complete row of
									a table.  For this reason the editor has the
									ability to select the current element context,
									based on the cursor location.  Doing this
									multiple times will select the parent element.
								</para>
								<para>
									This feature is available by selecting
									<menuchoice>
										<guimenu>Edit</guimenu>
										<guimenuitem>Select Context</guimenuitem>
									</menuchoice>
									from the main menu.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Select Element Content</term>
							<listitem>
								<para>
									Similar to select context you may just
									like to select the content of the current
									element, rather than selecting the open
									and close tags as well. 
								</para>
								<para>
									This feature is available by selecting
									<menuchoice>
										<guimenu>Edit</guimenu>
										<guimenuitem>Select Element Content</guimenuitem>
									</menuchoice>
									from the main menu.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Goto Context Start / End</term>
							<listitem>
								<para>
									After making changes to some text it can
									be useful to move to the start of the
									element block you are in, or perhaps then
									end, &app; provides support for doing
									just that.
								</para>
								<para>
									These are available from the
									<menuchoice>
										<guimenu>Search</guimenu>
										<guimenuitem>Goto Context Start</guimenuitem>
									</menuchoice>
									and
									<menuchoice>
										<guimenu>Search</guimenu>
										<guimenuitem>Goto Context End</guimenuitem>
									</menuchoice>
									menu items.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Goto Parent Element</term>
							<listitem>
								<para>
									As well as support for jumping to the
									start and end of the current element you
									can also jump up to the start of the
									parent element.
								</para>
								<para>
									This is available from the
									<menuchoice>
										<guimenu>Search</guimenu>
										<guimenuitem>Goto Parent Element</guimenuitem>
									</menuchoice>
									menu item.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Special Block Operations</term>
							<listitem>
								<para>
									A number of block operations are supported,
									that will operate on the whole document,
									or the selected text.  
								</para>
								<itemizedlist>
									<listitem>
										<para>
											Auto indent, which will indent the
											block based on the document structure
										</para>
									</listitem>
									<listitem>
										<para>
											Indent / Unindent, which will change
											the indentation taking no account
											of the document structure,
										</para>
									</listitem>
									<listitem>
										<para>
											Encode as Entities, which will
											convert any necessary characters to
											<acronym>HTML</acronym> / 
											<acronym>XML</acronym> entities
										</para>
									</listitem>
									<listitem>
										<para>
											URI Encode, changes all characters
											to their URI encoded equivalent. e.g.
											a space becomes %20
										</para>
									</listitem>
									<listitem>
										<para>
											Convert between upper / lower case
											for tag names.
										</para>
									</listitem>
								</itemizedlist>
								<para>
									All of these operations are available
									under the
									<menuchoice>
										<guimenu>Edit</guimenu>
										<guisubmenu>Block Operations</guisubmenu>
									</menuchoice>
									submenu.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Spell Checking</term>
							<listitem>
								<para>
									A markup aware spell checker is included,
									that will ignore tags, and only check their
									content.
								</para>
								<para>
									This is accessible from the
									<menuchoice>
										<guimenu>Tools</guimenu>
										<guimenuitem>Spell Check</guimenuitem>
									</menuchoice>
									menu item.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Document structure based auto indentation</term>
							<listitem>
								<para>
									This is the same automatic indentation that
									is available as a block operation, but can
									be enabled to operate while editing, e.g.
									pressing <keycap>Return</keycap> or
									<keycap>Tab</keycap> will indent the next, or
									current line based on the document structure.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Intelligent tag closing</term>
							<listitem>
								<para>
									Using this feature &gt; will be automatically
									inserted when a &lt; is entered.  In addition
									if a / is typed between &lt;&gt; the correct
									closing tag will be automatically filled in.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Auto completion</term>
							<listitem>
								<para>
									Based on &app; tag trees and reference files,
									and the type of document being edited,
									autocompletion may be provided.
								</para>
								<para>
									Auto completion is always provided for
									markup based documents after a &lt; has been
									typed, providing a list of all tag names.
								</para>
								<figure>
									<graphic fileref="figures/editor-autocomplete1.png"  align="center" format="PNG"/>
								</figure>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Tooltips</term>
							<listitem>
								<para>
									Tooltips are also provided based off tag
									trees and reference files.  These
									are displayed when hovering keywords
									with the mouse, or in the case of
									function calls, when the cursor is
									within the function call itself.
								</para>
								<figure>
									<graphic fileref="figures/editor-tooltips.png"  align="center" format="PNG"/>
								</figure>
							</listitem>
						</varlistentry>
						
						<varlistentry>
							<term>Inline tagging</term>
							<listitem>
								<para>
									Inline tagging occurs when you press space
									inside a tag, and presume you are about to
									enter a new attribute.  As such a popup is
									provided listing all valid attributes for that
									tag, based on the doctype in use.
								</para>
								<figure>
									<graphic fileref="figures/editor-inline-tagging.png"  align="center" format="PNG"/>
								</figure>
								
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Automatic entity insertion</term>
							<listitem>
								<para>
									Some characters are forbidden in
									<acronym>HTML</acronym> / <acronym>XML</acronym>
									documents, such as  &lt; and &gt;.  As such
									the editor helps ease the use of the correct
									entity.  Typing an &amp; will auto insert the
									trailing ; character, then pressing the key for
									the character you want will insert the correct
									entity.  Depending on what mode the entity
									insertion is in, when keys are pressed even
									not inside a &amp;; an entity will be inserted.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Enhanced Drag and Drop support</term>
							<listitem>
								<para>
									The editor has extensive drag and drop support.
									As well as dropping text into the editor you
									can drag html from your browser window, or
									a color from <application>The Gimp</application>, or a URI / file. 
								</para>
								<para>
									Pressing <keycap>Alt</keycap> or middle
									button dragging an item onto the editor will
									also provide a popup menu of how to insert
									the drop.  URIs / files for example can
									have their full pathname inserted, or
									a relative pathname, or even an appropriate
									tag based on what the file type is.  For
									text based URIs / files you can even insert
									their contents directly.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Error highlighting</term>
							<listitem>
								<para>
									The editor has the option to highlight invalid
									markup in <acronym>HTML</acronym> /
									<acronym>XML</acronym> documents, if such a
									section is right clicked on a &quot;Learn More&quot;
									item will appear in the context menu.
								</para>
								<para>
									The &quot;Learn More&quot; feature will
									open your web browser to a page hosted
									at <ulink url="http://www.screem.org/">www.screem.org</ulink>,
									although no help pages are currently
									available.
								</para>
								<figure>
									<graphic fileref="figures/editor-error.png"  align="center" format="PNG"/>
								</figure>
							</listitem>
						</varlistentry>
					</variablelist>
				</sect2>
			</sect1>		
			
			<sect1 id="preview">
				<title>The Preview View</title>
				<para>
					From the <guimenu>View</guimenu> menu.  Choose the
					<menuchoice>
						<guimenuitem>Preview</guimenuitem>
					</menuchoice> menu item.
				</para>
				<figure>
					<graphic fileref="figures/preview.png"  align="center" format="PNG" scalefit="1"/>
				</figure>
				<para>
					The preview provides a quick way of checking how your 
					<acronym>HTML</acronym> pages
					may look in web browsers.  It has rudimentary <acronym>CSS</acronym>
					support, and no support for scripting.
				</para>
			</sect1>
			
			<sect1 id="link">
				<title>The Link View</title>
				<para>
					From the <guimenu>View</guimenu> menu.  Choose the
					<menuchoice>
						<guimenuitem>Link View</guimenuitem>
					</menuchoice> menu item.
				</para>
				<para>
					The link view provides an overview of all the links contained
					documents, centered upon the current one, and going to a
					choosable depth.  It will show which files need to be
					uploaded to a remote site, and can also check all links
					to see if any are broken or not.
				</para>
			</sect1>
			
			<sect1 id="tree">
				<title>The Tree View</title>
				<para>
					From the <guimenu>View</guimenu> menu.  Choose the
					<menuchoice>
						<guimenuitem>Tree View</guimenuitem>
					</menuchoice> menu item.
				</para>
				<figure>
					<graphic fileref="figures/tree.png"  align="center" format="PNG" scalefit="1"/>
				</figure>
				
				<para>
					Currently the tree view only shows you the document structure
					of the file you are working on.  This can be used to help you
					spot missing closing tags, tags in the wrong place etc.
				</para>
				<para>
					Future versions of &app; will allow you to edit from within this
					view
				</para>
			</sect1>
			
		</chapter>
		
		<chapter id="sidebars">
			<title>Sidebars</title>
			<para>
				All sidebars can be detached from the main window, or rearranged as
				you see fit by dragging their title bar.  You can also hide / show
				them by using the
				<menuchoice>
					<guimenu>View</guimenu>
					<guisubmenu>Dock items</guisubmenu>
				</menuchoice> 
				submenu or the close button on their individual title bars.
			</para>
			<sect1 id="files-bar">
				<title>Files</title>
				<para>
					The files sidebar display will depend on if you are
					working on individual files, or a site.  As can be expected
					you can copy / move files and folders in the normal fashion.
					A file properties dialog is available for renaming and
					changing permissions / ownership, and can be accessed via
					a right click context menu.
				</para>
				<sect2 id="files-indi-bar">
					<title>When working on single files</title>
					<para>
						When working on single files you will be presented with a 
						tree view of the local system.
					</para>
					<figure float="1"><graphic fileref="figures/sidebar-files1.png" format="PNG"  align="center"/></figure>
				</sect2>
				<sect2 id="files-site-bar">
					<title>When working on a site</title>
					<para>
						When working on a site however only files in the site will
						be displayed.  The view will show two separate columns.
						The first being the folders / files in the site, showing
						the site name in the column heading.  The second shows the
						upload settings for those files.
					</para>
					<figure float="1"><graphic fileref="figures/sidebar-files2.png" format="PNG"   align="center"/></figure>
					<tip>
						<para>
							As well as listing all files in a site you can quickly
							access specific file types without having to expand all the
							folders to get at the file.  These specific types are
						</para>
						<itemizedlist>
							<listitem>
							<para>Images</para>
							</listitem>
							<listitem>
								<para>Scripts</para>
							</listitem>
							<listitem>
								<para>Stylesheets</para>
							</listitem>
							
						</itemizedlist>
					</tip>
					<para>
						In addition to supporting drag and drop file copying
						when working on a site, &app; will automatically update
						links to files / folders that you move to a new
						location, or rename.  
					</para>
					<note>
						<para>
							Link updating is only supported for 
							<acronym>HTML</acronym> and <acronym>XML</acronym>
							documents where the doctype in use specifies which
							attributes contain URIs, and for <acronym>CSS</acronym>
							files.
						</para>
					</note>
					<para>
						The three upload flags are also togglable when working
						on a site, they can either be set from the file properties
						dialog, or directly in the context menu.
					</para>
				</sect2>
			</sect1>
			
			<sect1 id="tree-bar">
				<title>Tree</title>
				<para>
					The tree bar provides a mini tree view of the current document
					structure.  It only provides two columns, unlike the main
					tree view.  These columns show the element type, and if
					the element is valid at that location in the document.
				</para>
				<para>
					This is currently an informational display only, no
					editing can take place here.
				</para>
				<figure float="1"><graphic fileref="figures/sidebar-tree.png" format="PNG"   align="center"/></figure>
				
			</sect1>
			
			<sect1 id="attributes-bar">
				<title>Attributes</title>
				<para>
					When working on an <acronym>HTML</acronym> /
					<acronym>XML</acronym> document the attributes sidebar
					becomes sensitive based on if the editor view cursor is within 
					a tag.  It actually provides three different
					pieces of information.
				</para>
				<para>
					Selecting a row in the tree view main view will
					have the same effect as if you had placed the
					cursor at that position in the document in the 
					editor.					
				</para>
				<variablelist>
					<varlistentry>
						<term>Attributes</term>
						<listitem>
							<para>
								This will list all the valid attributes for
								the tag, and allow you to change any of them.
							</para>
							<para>
								Any attributes that the tag is required to have
								will be displayed in bold.
							</para>
							<figure float="1"><graphic fileref="figures/sidebar-attributes1.png" format="PNG"   align="center"/></figure>
							
						</listitem>
					</varlistentry>
					<varlistentry>
						<term>Applied Styles</term>
						<listitem>
							<para>
								This will list any CSS rules that will be
								applied to the tag.  It will base this on
								any &lt;link&gt; based stylesheet in the
								document, any &lt;style&gt; tags, and any
								style attribute that may be present.
							</para>
							<para>
								Double clicking on an item in this list
								will take you to the file that contains
								the rule definition.
							</para>
							<figure float="1"><graphic fileref="figures/sidebar-attributes2.png" format="PNG"   align="center"/></figure>
						</listitem>
					</varlistentry>
					<varlistentry>
						<term>Description</term>
						<listitem>
							<para>
								Provides a description of the tag if one
								could be extracted from the dtd.
							</para>
							<figure float="1"><graphic fileref="figures/sidebar-attributes3.png" format="PNG"   align="center"/></figure>
						</listitem>
					</varlistentry>
				</variablelist>
			</sect1>
			
			<sect1 id="resources-bar">
				<title>Resources</title>
				<para>
					This sidebar provides access to screem's tag trees and
					reference files.  These provide documentation on a
					variety of subjects, as well as being able to insert
					markup / code for items they contain.  They are also
					used as the source for auto completion in the editor view.
				</para>
				<para>
					A number of tag trees are provided by default with screem,
					these are:
				</para>
				<itemizedlist>
					<listitem>
					<para>Apache</para>
					</listitem>
					<listitem>
					<para>CSS 2.0</para>
					</listitem>
					<listitem>
					<para>HTML 4.0</para>
					</listitem>
					<listitem>
					<para>PHP</para>
					</listitem>
					<listitem>
					<para>Python</para>
					</listitem>
					<listitem>
						<para>Screem Javascript Library</para>
					</listitem>
					<listitem>
					<para>TEI Lite</para>
					</listitem>
				</itemizedlist>
				<figure float="1"><graphic fileref="figures/sidebar-resources1.png" format="PNG"   align="center"/></figure>
				<para>
					In addition to these tag trees a special entry is added
					here for the current doctype in use.
				</para>
				<figure float="1"><graphic fileref="figures/sidebar-resources2.png" format="PNG"   align="center"/></figure>
				<para>
					As tag trees can be quite large, a search facility is
					present for searching individual trees.  This is available
					from the toolbar beneath the resources list.
					<figure float="1"><graphic fileref="figures/sidebar-resources3.png" format="PNG"   align="center"/></figure>
				</para>
			</sect1>
			
			<sect1 id="symbols">
				<title>Symbols</title>
				<para>
					The symbols sidebar only comes into play when working on a
					site.  If a <application>ctags</application> file is
					present in the site directory, or the site settings specify
					to create one, all symbols found will be displayed here,
					double clicking on them will jump to the document that
					contains them and highlight that section in the editor view.
				</para>
				<para>
					This relies on <application>ctags</application> being
					present on your system, and the site being worked on also
					being local rather than on a remote system.
				</para>
				<figure float="1"><graphic fileref="figures/sidebar-symbols.png" format="PNG"   align="center"/></figure>
			</sect1>
			
			<sect1 id="messages-bar">
				<title>Messages and Errors</title>
				<para>
					These two sidebars provide feedback messages, and errors.
					Any multiline messages will be shown here rather than the
					status bar.
				</para>
				<para>
					Helper applications may also output to these sidebars so
					results can be seen, or the reason for any errors determined.
				</para>
				<figure float="1"><graphic fileref="figures/sidebar-messages.png" format="PNG"   align="center"/></figure>
				<figure float="1"><graphic fileref="figures/sidebar-errors.png" format="PNG"   align="center"/></figure>
				
			</sect1>
			
		</chapter>
		
	</part>	
	
	<part id="wizards">
		<title>Wizards</title>
		<partintro>
			<para>
				&app; supports plugins for providing wizards to perform
				common tasks more easily.  All wizards are reachable from
				the
				<menuchoice>
					<guimenu>Insert</guimenu>
					<guisubmenu>Wizards</guisubmenu>
				</menuchoice>
				submenu, and may possibly add an icon to the wizards toolbar.
			</para>
		</partintro>
		<chapter id="provided-wizards">
			<title>Provided Wizards</title>
			
			<sect1 id="color-wizard">
				<title>Color Wizard</title>
				<figure>
					<graphic fileref="figures/color-wizard.png"  align="center" format="PNG"/>
				</figure>
				<para>
					The color wizard provides a simple color selection
					dialog, which allows you to insert a color code either
					via the <guibutton>Apply</guibutton> or <guibutton>ok</guibutton>
					buttons, or by dragging a color to the editor window.
				</para>
				<para>
					An eye-dropper button is also available which allows a
					color to be chosen from anywhere on the screen, you can
					then insert that using one of the methods mentioned
					above.
				</para>
			</sect1>
			
			<sect1 id="css-wizard">
				<title>CSS Selector Wizard</title>
				<figure>
					<graphic fileref="figures/css-wizard1.png"  align="center" format="PNG"/>
				</figure>
				<para>
					Relieving you of having to remember the different
					selectors for <acronym>CSS</acronym> rules, this
					wizard provides a simple, straight forward method
					of saying what you want a rule to match.  Once the
					full selector has been setup clicking the
					<guibutton>Insert</guibutton> button will insert
					it into the editor.
				</para>
				<figure>
					<graphic fileref="figures/css-wizard2.png"  align="center" format="PNG"/>
				</figure>
				<para>
					As well as allowing you to define the selector you
					can also set specific style properties.  Click
					the <guibutton>Styles</guibutton> button to jump
					to the properties page.  This will present you with
					a grouped display of <acronym>CSS</acronym> properties.
					Clicking the <guibutton>Match</guibutton> button will
					take you back to the selector page.
				</para>
			</sect1>
			
			<sect1 id="entity-wizard">
				<title>Entity Wizard</title>
				<figure>
					<graphic fileref="figures/entity-wizard.png"  align="center" format="PNG"/>
				</figure>
				<para>
					<acronym>HTML</acronym> has a predefined set of
					character entities, these are characters that shouldn't
					be typed directly into a document, but the entity
					should be used instead.
				</para>
				<para>
					This wizard shows these character entities, along with
					the character they are for.  Double clicking on the one
					you wish to use will insert it into the editor.
				</para>
			</sect1>
			
			<sect1 id="form-wizard">
				<title>Form Wizard</title>
				<figure>
					<graphic fileref="figures/form-wizard.png"  align="center" format="PNG"/>
				</figure>
				<para>
					The form wizard provides a simple method of setting up
					the submission details for a &lt;form&gt;.  As well as
					the usual setting of the method, and action a selection
					of encoding types are provided for you to choose from.
					The default type in html is application/x-www-form-urlencoded
				</para>
			</sect1>
			
			<sect1 id="image-wizard">			
				<title>Image Wizard</title>
				<figure>
					<graphic fileref="figures/image-wizard.png"  align="center" format="PNG"/>
				</figure>
				<para>
					The image wizard allows you to insert an &lt;img&gt;
					tag into your <acronym>HTML</acronym> documents.  It also supports
					creating thumbnailed links to images if they are too
					large to include inline in the page.
				</para>				
			</sect1>
			
			<sect1 id="object-wizard">
				<title>Object Wizard</title>
				<figure>
					<graphic fileref="figures/object-wizard.png"  align="center" format="PNG"/>
				</figure>
				<para>
					The object wizard is very similar to the image wizard,
					but deals with the &lt;object&gt; tag in
					<acronym>HTML</acronym> documents.  As such it can also
					be used to insert images that way. 
				</para>
				<para>
					The thumbnailing feature from the image wizard is
					also available here, but not just for image files.
					Thumbnailed links can be created to any type of file
					that the <acronym>GNOME</acronym> desktop can thumbnail,
					such as movie files.
				</para>
			</sect1>
			
			<sect1 id="link-wizard">
				<title>Link Wizard</title>
				<figure>
					<graphic fileref="figures/link-wizard1.png"  align="center" format="PNG"/>
				</figure>
				<para>
					This wizard will insert links to other documents
					in your site, or on external sites.
				</para>
				<figure>
					<graphic fileref="figures/link-wizard2.png"  align="center" format="PNG"/>
				</figure>
				<para>
					The <guibutton>Edit pop-up</guibutton> button also
					allows you to have the link open a new popup window.
					You can control whether the new window will have a menubar,
					toolbar etc. as well as the size and position.  A
					new window will still be opened with the link even
					without Javascript support in the browser, except
					it will not have the size/position etc. that you defined.
				</para>
			</sect1>
			
			<sect1 id="ssi-wizard">
				<title>Server Side Include Wizard</title>
				<figure>
					<graphic fileref="figures/ssi-wizard.png"  align="center" format="PNG"/>
				</figure>
				<para>
					Although less commonly used with sites now this
					wizard allows you to insert the different 
					server side include directives into your page. 
				</para>
			</sect1>
			
			<sect1 id="table-wizard">
				<title>Table Wizard</title>
				<figure>
					<graphic fileref="figures/table-wizard.png"  align="center" format="PNG"/>
				</figure>
				<para>
					Tables are commonly used for layout purposes in
					<acronym>HTML</acronym> documents.  Creating the
					table with the correct columns, rows etc. can be a slow
					dull task, so this wizard will do all that for you,
					along with setting the appearance of the table.
				</para>
			</sect1>
		</chapter>
	</part>
	<part id="templates">
		<title>Using Templates</title>
		<partintro>
			<para>
				&app; supports a templating system similar to that used
				in Macromedia Dreamweaver, and will infact support those
				used by Dreamweaver, so any templates you have purchased
				for use there can still be used with &app; <emphasis>(if not prohibited
				by the template's license)</emphasis>
			</para>
		</partintro>
		<chapter id="creating-templates">
			<title>Creating Templates</title>
			<note>
				<para>
					Templates can only be created when working on a site,
					not when working on individual files
				</para>
			</note>
			<para>
				Creating a template is no different to creating a normal
				document.  The difference comes when you save it.  From the
				<guimenu>File</guimenu> menu choose,
				<menuchoice>
					<guimenuitem>Save As Template</guimenuitem>
				</menuchoice>.
			</para>
			<para>
				Saving the template will create a Templates folder at the
				root of your site, and the template will be added there.
				(unless you choose a different folder to save into)
			</para>
			<note>
				<para>
					All referenced files should be either absolute paths,
					or relative from the folder the template is in.
					Relative paths will automatically be corrected in
					documents which use the template to point to the
					correct file.
				</para>
			</note>
		</chapter>
		<chapter id="editable-regions">
			<title>Adding Editable Regions</title>
			<para>
				Editable regions allow you to define areas of your template
				that can be modified by pages which use it.  These areas
				will remain intact when the rest of the page updates to
				follow changes in the template.
			</para>
			<para>
				To add an editable region choose
				<menuchoice>
					<guisubmenu>Editable Regions</guisubmenu>
					<guimenuitem>Create Editable Region...</guimenuitem>
				</menuchoice>
				from the <guimenu>Edit</guimenu> menu.
			</para>
			<para>
				You will then be prompted to provide a name for the region,
				this can be anything you like.  The editable region will then
				be added.  The region is delimited by the comment tags.
			</para>
		</chapter>
		<chapter id="modify-template">
			<title>Modifying a Template</title>
			<para>
				Templates can still be edited just like a normal document,
				saving them just like a normal document.  Any other documents
				in the site which use the template will be automatically
				updated to reflect the changes, they will not be
				automatically saved so you will need to do this manually.
			</para>
			<para>
				If there are areas of a document you want to stay intact
				after a template has updated look into using
				<link linkend="editable-regions">editable regions</link>
			</para>
		</chapter>
	</part>
	<part id="helpers">
		<title>Helper Applications</title>
		<partintro>
			<para>
				Adding, editing, and removing helpers is all done
				via the edit helpers dialog.  This is under the
				<menuchoice><guimenu>Tools</guimenu></menuchoice> menu as
				<menuchoice>
					<guimenu>Helpers</guimenu>
					<guimenuitem>Edit Helpers</guimenuitem>
				</menuchoice>	
			</para>
		</partintro>
		<chapter id="adding-helpers">
			<title>Adding Helpers</title>
			<para>
				All you need to do to add a helper application is
				fill in the name field with what you want to call the
				helper (this will be used as the menu label), and
				enter the command to run in the command box.
			</para>
			<para>
				Then you need to tell &app; what input/output mode
				to use.  By default the current document is fed to the
				helper (via stdin) and when the helper is finished it
				replaces the document contents with its output.
				<itemizedlist>
					<title><guilabel>Input:</guilabel></title>
					<listitem>
						<para>
							<guibutton>Page text</guibutton>
							This mode will feed the current document
							to the helper when it is used.
						</para>
						<note>
							<para>
								If you only want part of the document
								to be processed simply select it in 
								the editor view.
							</para>
						</note>
					</listitem>
					<listitem>
						<para>
							<guibutton>Used defined</guibutton>
							This mode will lets you provide different
							content each time you run the helper, with
							an option to use the selected
							content of the current document.
						</para>
					</listitem>
					<listitem>
						<para>
							<guibutton>None</guibutton>
							As the name would suggest, no input will be
							given to the helper.
						</para>
					</listitem>
				</itemizedlist>
				<itemizedlist>
					<title><guilabel>Output:</guilabel></title>
					<listitem>
						<para>
							<guibutton>Replaces Page</guibutton>
							This mode will replace the current document
							with the output (on stdout) of the helper.
						</para>
						<note>
							<para>
								If you only want part of the document
								to be processed simply select it in 
								the editor view.
							</para>
						</note>
					</listitem>
					<listitem>
						<para>
							<guibutton>Inserted into page</guibutton>
							This mode will insert the helper output
							(on stdout) at the current cursor position.
						</para>
						<note>
							<para>Not implemented yet</para>
						</note>
					</listitem>
					<listitem>
						<para>
							<guibutton>Shown as messages</guibutton>
							The output of the helper (on stdout) will be
							displayed in the messages window.
						</para>
					</listitem>
				</itemizedlist>	
			</para>
			<para>
				The final option that can be chosen is whether the
				helper should be automatically run when you save a document.
				To do this click the 
				<guibutton>Execute helper when saving documents</guibutton>
				checkbox, and then select the type of file you want the
				helper to be used for.
			</para>
			<para>
				After you have filled in all the details click the
				<guibutton>Add</guibutton> button and the helper
				will be added to the list, and appear in the menu with
				any others you have already created.
			</para>
		</chapter>
		<chapter id="editing-helpers">
			<title>Editing Helpers</title>
			<para>
				Should you wish to change the command that a helper uses
				you can do this quite easily.  Choose the helper you want
				to edit from the list shown in the edit helpers dialog,
				make any changes you want, and click the <guibutton>refresh</guibutton>
				button.
			</para>
		</chapter>
		<chapter id="removing-helpers">
			<title>Removing Helpers</title>
			<para>
				Choose the helper you want to remove from the list
				shown in the edit helpers dialog, and then click the
				<guibutton>Remove</guibutton> button.
			</para>
		</chapter>
		<chapter id="system-wide-helpers">
			<title>System Wide Helpers</title>
			<para>
				Helpers can be added on a system wide basis so all
				users have them automatically available.  To do this
				add a helper as normal.  This will create a .desktop file
				in .screem/helpers located in your home directory.  Copy
				this file to <filename>&lt;prefix&gt;/share/screem</filename>
				where &lt;prefix&gt; is the path &app; is installed to.
				(this will generally be <filename>/usr</filename> if you
				are using a packaged version.)
			</para>
			<para>
				You can organized <filename>&lt;prefix&gt;/share/screem</filename>
				by placing related helpers in subfolders if you choose to.
			</para>
		</chapter>
		<chapter id="helper-arguments">
			<title>Passing extra information to helpers</title>
			<para>
				You may find that you need to provide extra information
				to a helper application, such as the pathname to the
				site you are working on, or the current folder that the
				document you are using is in etc.  The following special
				flags are available for this purpose:
				<table>
					<title>Special flags</title>
					<tgroup>
						<thead>
							<row>
								<entry><para>Flag</para></entry>
								<entry><para>Purpose</para></entry>
							</row>
						</thead>
						<tbody>
							<row>
								<entry><para>%f</para></entry>
								<entry><para>current document filename, including directory</para></entry>
							</row>
							<row>
								<entry><para>%U</para></entry>
								<entry><para>current document uri</para></entry>
							</row>
							<row>
								<entry><para>%d</para></entry>
								<entry><para>current document directory</para></entry>
							</row>
							<row>
								<entry><para>%S</para></entry>
								<entry><para>current site directory</para></entry>
							</row>
							<row>
								<entry><para>%p</para></entry>
								<entry><para>uri the published site can be viewed at.</para></entry>
							</row>
							<row>
								<entry><para>%%</para></entry>
								<entry><para>a normal % character, should you need one</para></entry>
							</row>
						</tbody>
					</tgroup>
				</table>
			</para>
		</chapter>
		<chapter id="included-helpers">
			<title>Preincluded Helpers</title>
			<para>
				&app; comes with some predefined helpers for the following
				purposes:
				<table>
					<title>Predefined Helpers</title>
					<tgroup>
						<thead>
							<row>
								<entry><para>Name</para></entry>
								<entry><para>Purpose</para></entry>
							</row>
						</thead>
						<tbody>
							<row>
								<entry><para>Tidy (HTML)</para></entry>
								<entry><para>This helper runs <ulink url="http://tidy.sourceforge.net/">HTML Tidy</ulink> on the current
								document, indenting it, and replacing
								the document with the tidied HTML</para></entry>
							</row>
							<row>
								<entry><para>Tidy (XML)</para></entry>
								<entry><para>Like Tidy (HTML) this helper runs <ulink url="http://tidy.sourceforge.net/">HTML Tidy</ulink> on the current
								document the only difference being it is
								meant for use with XML documents instead of
								HTML</para></entry>
							</row>
						</tbody>
					</tgroup>
				</table>
				If any of the mentioned helpers do not appear to be active
				on your system it will be because you do not have the
				necessary application installed.
			</para>
		</chapter>
		
		<!-- <chapter id="helper-packs">
			<title>Helper packs</title>
		</chapter> -->
	</part>
	<part id="configuring">
		<title>Configuring &app;</title>
		<partintro>
			<para>
				From the <guimenu>Edit</guimenu> menu.  Choose the
				<menuchoice>
					<guimenuitem>Preferences</guimenuitem>
				</menuchoice> menu item for the main <link linkend="prefs-dialog">preferences dialog</link>
			</para>
		</partintro>
		<chapter id="prefs-dialog">
			<title>Preferences Dialog</title>
			<para>
				The preferences dialog is split into six sections.
				<itemizedlist>
					<listitem><para><link linkend="prefs-misc">Misc</link></para></listitem>
					<listitem><para><link linkend="prefs-font-colors">Fonts &amp; Colors</link></para></listitem>
					<listitem><para><link linkend="prefs-editor">Editor</link></para></listitem>
					<listitem><para><link linkend="prefs-doctypes">Doctypes</link></para></listitem>
					<listitem><para><link linkend="prefs-tag-trees">Tag Trees</link></para></listitem>
				</itemizedlist>
			</para>
			<sect1 id="prefs-misc">
				<title>Misc</title>
				<figure>
					<graphic fileref="figures/prefs-misc.png"  align="center" format="PNG"/>
				</figure>
				<para>
					There are four items provided in the defaults section of
					this tab.
					<variablelist>
						<varlistentry>
							<term>Page Filename</term>
							<listitem>
								<para>
									This defines the filename that will
									be created as an initial file when
									creating a new site.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Character Set</term>
							<listitem>
								<para>
									The default character set to use in
									documents if one isn't specified by the
									document itself.  The default is UTF-8
								</para>
								<para>
									HTML / XML documents are the only types
									of document that the character set can
									be detected from.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Doctype</term>
							<listitem>
								<para>
									The default markup document type to use
									for pages that don't specify one.
								</para>
								<para>
									The doctype is used in building up the
									tree view of the document, and providing
									the current doctype tag tree in the
									<link linkend="resources-bar">resources sidebar</link>
									and providing autocompletion.  The default
									is transitional HTML 4.01.
								</para>
							</listitem>
						</varlistentry>
						<varlistentry>
							<term>Blank document type</term>
							<listitem>
								<para>
									The type of document that will be
									created when creating a new blank document.
									This defaults to an HTML document.
								</para>
							</listitem>
						</varlistentry>
					</variablelist>
				</para>
			</sect1>
			<sect1 id="prefs-fonts-colors">
				<title>Fonts &amp; Colors</title>
				<figure>
					<graphic fileref="figures/prefs-fonts-colors.png"  align="center" format="PNG"/>
				</figure>
				<para>
					The font and colors that are used in the editor view
					can be configured here.  You can choose to use whatever
					your current theme uses by default, or specify your own
					colors and font.
				</para>
				<tip>
					<para>
						Currently GTK doesn't handle dark backgrounds very
						well as the cursor color cannot be changed, as such
						you probably want to avoid black as the background
						color.
					</para>
				</tip>			
				</sect1>
			<sect1 id="prefs-editor">
				<title>Editor</title>
				<figure>
					<graphic fileref="figures/prefs-editor.png"  align="center" format="PNG"/>
				</figure>
				<para>
					The editor tab is split into two sections.
					<itemizedlist>
						<listitem>
							<para>
								Appearance
								<variablelist>
									<varlistentry>
										<term>Syntax Highlighting</term>
										<listitem>
											<para>
												Use syntax highlighting
												where available
											</para>
										</listitem>
									</varlistentry>
									<varlistentry>
										<term>Error Highlighting</term>
										<listitem>
											<para>
												When working with markup
												class documents like HTML and
												XML &app; can highlight
												where the doctype is not
												being followed if this
												option is enabled.
											</para>
											<para>
												A Learn More option is also
												added to the popup menu
												in the editor when clicking
												on a highlighted section.
											</para>
										</listitem>
									</varlistentry>
									<varlistentry>
										<term>Wrap lines</term>
										<listitem>
											<para>
												Controls if long lines wrap,
												or if a horizontal scrollbar
												will be used instead.
											</para>
										</listitem>
									</varlistentry>
									<varlistentry>
										<term>Tab Width</term>
										<listitem>
											<para>
												controls how wide tabs are.
											</para>
										</listitem>
									</varlistentry>
									<varlistentry>
										<term>Right column margin</term>
										<listitem>
											<para>
												A margin can be placed on
												the right hand side of the
												editor to mark a specific
												column.  This can be useful
												when working on source code
												files, such as PHP where
												your coding style guidelines
												indicate a maximum line
												width.
											</para>
										</listitem>
									</varlistentry>
								</variablelist>
							</para>
						</listitem>
						<listitem>
							<para>
								Features
								<variablelist>
									<varlistentry>
										<term>Inline Tagging</term>
										<listitem>
											<para>
												Enables the inline tagging
												feature, where pressing space
												inside a tag presents the
												autocompletion popup with a
												list of all valid attributes.
											</para>
										</listitem>
									</varlistentry>
									<varlistentry>
										<term>Auto Indent</term>
										<listitem>
											<para>
												This option controls if
												document tree based auto
												indentation should be used
												rather than normal indentation
												based on the type of document
												being edited.
											</para>
										</listitem>
									</varlistentry>
									<varlistentry>
										<term>Intelligent tag closing</term>
										<listitem>
											<para>
												When typing <userinput>&lt;/</userinput>
												&app; can automatically
												fill in the correct closing
												tag name with this option
												enabled.
											</para>
										</listitem>
									</varlistentry>
									<varlistentry>
										<term>Auto complete from tag trees</term>
										<listitem>
											<para>
												Tag trees which specify
												the type of document they are
												for can be used to provide
												autocompletion with this feature
												enabled.
											</para>
											<para>
												Along side the PHP tag tree
												this provides &app; with
												autocompletion for all
												PHP4 functions.
											</para>
										</listitem>
									</varlistentry>
									<varlistentry>
										<term>Show function definition tooltips</term>
										<listitem>
											<para>
												As well as using tag trees for
												autocompletion, this option
												will show tooltips for
												functions contained within
												a tag tree.
											</para>
											<para>
												Using the PHP tag tree as
												and example again this will
												provide tooltips showing
												the definition of all PHP4
												functions.
											</para>
										</listitem>
									</varlistentry>
									<varlistentry>
										<term>Insert spaces instead of tabs</term>
										<listitem>
											<para>
												Use the equivalent number of
												spaces instead of tab characters.
											</para>
										</listitem>
									</varlistentry>
									<varlistentry>
										<term>Auto entity insertion</term>
										<listitem>
											<para>
												This controls if &app; will
												insert character entities in
												markup class documents if the
												typed character should be
												encoded.
											</para>
											<para>
												If set to On then this will
												happen all the time.  If
												set to be performed by character
												set then it will only occur for
												reserved characters rather
												than all non ascii characters.
											</para>
										</listitem>
									</varlistentry>
								</variablelist>
							</para>
						</listitem>
					</itemizedlist>
				</para>
			</sect1>
			<sect1 id="prefs-doctypes">
				<title>Doctypes</title>
				<figure>
					<graphic fileref="figures/prefs-doctypes.png"  align="center" format="PNG"/>
				</figure>
				<para>
					All <acronym>DTD</acronym>s available to &app;
					will be listed here. (most will be hidden by default)
					to avoid clutter.
				</para>
				<para>
					You can tell screem which documents to apply specific
					doctypes to here.  Simply click the doctype, then
					select the type of document to apply it as the default for.
					You can also specify to use the selected doctype as the
					default if the root element of the current document
					matches.  With this you can setup multiple doctypes
					for XML Documents.
				</para>
				<para>
					&app; attempts to guess the root element for a given
					<acronym>DTD</acronym> but may not always get this
					correct.  Selecting the <guibutton>Override Root Element</guibutton>
					checkbox allows you to specify what the element is for
					the selected doctype.
				</para>
				<para>
					As well as overriding the root element you can set up
					a different url to be inserted as the system id.  A
					reason for doing so may be that the url is file: based
					and so only relevant for your machine, so tools such
					as the <acronym>W3C</acronym>
					<ulink url="http://validator.w3.org">HTML validator</ulink>
					won't be able to validate against the <acronym>DTD</acronym>
					correctly.
				</para>
			</sect1>
			<sect1 id="prefs-tag-trees">
				<title>Tag Trees</title>
				<figure>
					<graphic fileref="figures/prefs-tag-trees.png"  align="center" format="PNG"/>
				</figure>
				<para>
					This tab displays a list of all tag tree files that
					are available, and where they are stored.
				</para>
				<para>
					If you do not want specific tree files to be loaded you
					can simply click the checkbox in the Active column of
					the list.
				</para>
				<para>
					Additional files can be added from any location you like
					by clicking <guibutton>Add</guibutton>.  Any tag trees
					added like this can also be removed by selecting them
					in the list, and clicking <guibutton>Remove</guibutton>.
				</para>
				<para>
					If a tag tree file changes, you can force &app; to reload
					it, by selecting it in the list and clicking
					<guibutton>Refresh</guibutton>.
				</para>
			</sect1>
			
		</chapter>
		<chapter id="config-toolbars">
			<title>Toolbars</title>
			<sect1 id="config-toolbars-display">
				<title>Displaying</title>
				<para>
					From the <guimenu>View</guimenu> menu you can show / hide
					both the main toolbars and the wizard toolbar.  
				</para>
				<para>
					Choose the
					<menuchoice>
						<guimenuitem>Main Toolbar</guimenuitem>
					</menuchoice>
					toggle button to hide/show the main toolbar, and any
					additional toolbars you add.
				</para>
				<para>
					Choose the
					<menuchoice>
						<guimenuitem>Wizard Toolbar</guimenuitem>
					</menuchoice>
					toggle button to hide/show the wizard toolbar.	
				</para>
			</sect1>
			<sect1 id="config-toolbars-appearance">
				<title>Appearance</title>
				<para>
					The toolbars will follow the default appearance of your
					desktop, should you wish to change this, so they display
					<itemizedlist>
						<listitem><para><guimenuitem>Icons only</guimenuitem></para></listitem>
						<listitem><para><guimenuitem>Text only</guimenuitem></para></listitem>
						<listitem><para><guimenuitem>Text for all icons</guimenuitem></para></listitem>
						<listitem><para><guimenuitem>Text for important icons</guimenuitem></para></listitem>
					</itemizedlist>
					or revert back to <guimenuitem>Desktop default</guimenuitem>
					then choose the appropriate item from the 
					<guimenu>View</guimenu><guisubmenu>Toolbar Appearance</guisubmenu>
					menu.
				</para>
			</sect1>
			<sect1>
				<title>Changing toolbar buttons</title>
				<para>
					&app; only displays a very basic toolbar by default, along
					with the wizards toolbar.  While you can not edit the wizard
					bar you can alter the main one, or even add additional bars.
				</para>
				<itemizedlist>
					<listitem>
						<para>
							To add or remove buttons from your toolbar, select
							<menuchoice>
								<guimenu>Edit</guimenu>
								<guimenuitem>Toolbars</guimenuitem>
							</menuchoice>
						</para>
					</listitem>
					<listitem>
						<para>
							To add a new toolbar, click <guibutton>Add Toolbar</guibutton>
							in the toolbar editor.
						</para>
					</listitem>
					<listitem>
						<para>
							To remove a toolbar, remove all items from it.  The
							toolbar will then automatically be removed.
						</para>
					</listitem>
					<listitem>
						<para>
							Drag buttons, to rearrange them either on the same 
							toolbar or between different toolbars.
						</para>
					</listitem>
				</itemizedlist>
			</sect1>
		</chapter>
	</part>				
	
	<appendix id="shortcuts">
		<title>Shortcuts</title>
		<sect1 id="keyboard-shortcuts">
			<title>Keyboard Shortcuts</title>
			<table id="file-menu-shortcuts" frame="topbot">
				<title>File menu</title>
				<tgroup cols="2" colsep="0" rowsep="0">
					<thead>
						<row>
							<entry><para>Shortcut</para></entry>
							<entry><para>Description</para></entry>
						</row>
					</thead>
					<tbody>
						<row>
							<entry><para>Ctrl+N</para></entry>
							<entry><para>New Document</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+O</para></entry>
							<entry><para>Open</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+L</para></entry>
							<entry><para>Open Location</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+S</para></entry>
							<entry><para>Save Document</para></entry>
						</row>
						<row>
							<entry><para>Shift+Ctrl+S</para></entry>
							<entry><para>Save Document as</para></entry>
						</row>
						<row>
							<entry><para>Shift+Ctrl+P</para></entry>
							<entry><para>Print Preview</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+P</para></entry>
							<entry><para>Print</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+W</para></entry>
							<entry><para>Close Document</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+Q</para></entry>
							<entry><para>Quit &app;</para></entry>
						</row>
					</tbody>
				</tgroup>
			</table>
			<table id="edit-menu-shortcuts" frame="topbot">
				<title>Edit menu</title>
				<tgroup cols="2" colsep="0" rowsep="0">
					<thead>
						<row>
							<entry><para>Shortcut</para></entry>
							<entry><para>Description</para></entry>
						</row>
					</thead>
					<tbody>
						<row>
							<entry><para>Ctrl+Z</para></entry>
							<entry><para>Undo</para></entry>
						</row>
						<row>
							<entry><para>Shift+Ctrl+Z</para></entry>
							<entry><para>Redo</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+X</para></entry>
							<entry><para>Cut</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+C</para></entry>
							<entry><para>Copy</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+V</para></entry>
							<entry><para>Paste</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+A</para></entry>
							<entry><para>Select All</para></entry>
						</row>
						<row>
							<entry><para>Shift+Ctrl+A</para></entry>
							<entry><para>Select current context</para></entry>
						</row>
						<row>
							<entry><para>Shift+Ctrl+C</para></entry>
							<entry><para>Select current element content</para></entry>
						</row>
						<row>
							<entry><para>Shift+Ctrl+I</para></entry>
							<entry><para>Indent</para></entry>
						</row>
						<row>
							<entry><para>Shift+Ctrl+U</para></entry>
							<entry><para>Unindent</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+B</para></entry>
							<entry><para>Bookmarks</para></entry>
						</row>
					</tbody>
				</tgroup>
			</table>
			<table id="view-menu-shortcuts" frame="topbot">
				<title>View menu</title>
				<tgroup cols="2" colsep="0" rowsep="0">
					<thead>
						<row>
							<entry><para>Shortcut</para></entry>
							<entry><para>Description</para></entry>
						</row>
					</thead>
					<tbody>
						<row>
							<entry><para>Ctrl+F1</para></entry>
							<entry><para>Show/Hide message window</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+F2</para></entry>
							<entry><para>Show/Hide error window</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+F4</para></entry>
							<entry><para>Show/Hide File browser</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+F5</para></entry>
							<entry><para>Show/Hide Resources</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+F6</para></entry>
							<entry><para>Show/Hide document structure tree</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+F7</para></entry>
							<entry><para>Show/Hide attributes</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+F8</para></entry>
							<entry><para>Show/Hide Symbol browser</para></entry>
						</row>
						<row>
							<entry><para>Shift+Ctrl+T</para></entry>
							<entry><para>Show/Hide Main Toolbar</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+1</para></entry>
							<entry><para>Switch to editor view</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+2</para></entry>
							<entry><para>Switch to internal preview view</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+3</para></entry>
							<entry><para>Switch to link view</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+4</para></entry>
							<entry><para>Switch to tree view</para></entry>
						</row>
					</tbody>
				</tgroup>
			</table>
			<table id="search-menu-shortcuts" frame="topbot">
				<title>Search menu</title>
				<tgroup cols="2" colsep="0" rowsep="0">
					<thead>
						<row>
							<entry><para>Shortcut</para></entry>
							<entry><para>Description</para></entry>
						</row>
					</thead>
					<tbody>
						<row>
							<entry><para>Ctrl+F</para></entry>
							<entry><para>Find</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+G</para></entry>
							<entry><para>Find Again</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+H</para></entry>
							<entry><para>Find/Replace</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+I</para></entry>
							<entry><para>Goto Line</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+[</para></entry>
							<entry><para>Goto Context Start</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+]</para></entry>
							<entry><para>Goto Context End</para></entry>
						</row>
						<row>
							<entry><para>Alt+Up</para></entry>
							<entry><para>Goto Parent Element</para></entry>
						</row>
					</tbody>
				</tgroup>
			</table>
			<!--
			<table id="insert-menu-shortcuts" frame="topbot">
				<title>Insert menu</title>
				<tgroup cols="2" colsep="0" rowsep="0">
					<thead>
						<row>
							<entry><para>Shortcut</para></entry>
							<entry><para>Description</para></entry>
						</row>
					</thead>
					<tbody>
					
					</tbody>
				</tgroup>
			</table>
			<table id="site-menu-shortcuts" frame="topbot">
				<title>Site menu</title>
				<tgroup cols="2" colsep="0" rowsep="0">
					<thead>
						<row>
							<entry><para>Shortcut</para></entry>
							<entry><para>Description</para></entry>
						</row>
					</thead>
					<tbody>
					
					</tbody>
				</tgroup>
			</table>
			<table id="tools-menu-shortcuts" frame="topbot">
				<title>Tools menu</title>
				<tgroup cols="2" colsep="0" rowsep="0">
					<thead>
						<row>
							<entry><para>Shortcut</para></entry>
							<entry><para>Description</para></entry>
						</row>
					</thead>
					<tbody>
					
					</tbody>
				</tgroup>
			</table>
			-->
			<table id="documents-menu-shortcuts" frame="topbot">
				<title>Documents menu</title>
				<tgroup cols="2" colsep="0" rowsep="0">
					<thead>
						<row>
							<entry><para>Shortcut</para></entry>
							<entry><para>Description</para></entry>
						</row>
					</thead>
					<tbody>
						<row>
							<entry><para>Ctrl+Page Up</para></entry>
							<entry><para>Previous Document</para></entry>
						</row>
						<row>
							<entry><para>Ctrl+Page Down</para></entry>
							<entry><para>Next Document</para></entry>
						</row>
						<row>
							<entry><para>Shift+Ctrl+L</para></entry>
							<entry><para>Save All Documents</para></entry>
						</row>
						<row>
							<entry><para>Shift+Ctrl+W</para></entry>
							<entry><para>Close All Documents</para></entry>
						</row>
						<row>
							<entry><para>Alt+1</para></entry>
							<entry><para>Switch to first document</para></entry>
						</row>
						<row>
							<entry><para>Alt+2</para></entry>
							<entry><para>Switch to second document</para></entry>
						</row>
						<row>
							<entry><para>Alt+3</para></entry>
							<entry><para>Switch to third document</para></entry>
						</row>
						<row>
							<entry><para>Alt+4</para></entry>
							<entry><para>Switch to fourth document</para></entry>
						</row>
						<row>
							<entry><para>Alt+5</para></entry>
							<entry><para>Switch to fifth document</para></entry>
						</row>
						<row>
							<entry><para>Alt+6</para></entry>
							<entry><para>Switch to sixth document</para></entry>
						</row>
						<row>
							<entry><para>Alt+7</para></entry>
							<entry><para>Switch to seventh document</para></entry>
						</row>
						<row>
							<entry><para>Alt+8</para></entry>
							<entry><para>Switch to eighth document</para></entry>
						</row>
						<row>
							<entry><para>Alt+9</para></entry>
							<entry><para>Switch to nineth document</para></entry>
						</row>
					</tbody>
				</tgroup>
			</table>
			<table id="help-menu-shortcuts" frame="topbot">
				<title>Help menu</title>
				<tgroup cols="2" colsep="0" rowsep="0">
					<thead>
						<row>
							<entry><para>Shortcut</para></entry>
							<entry><para>Description</para></entry>
						</row>
					</thead>
					<tbody>
						<row>
							<entry><para>F1</para></entry>
							<entry><para>Show this manual</para></entry>
						</row>
					</tbody>
				</tgroup>
			</table>
		</sect1>
	</appendix>
	
	<appendix id="authors">
		<title>Authors</title>
		<sect1 id="appauthors">
			<title>Developers</title>
			<para>
				<application>&app;</application> was written by:
			</para>
			<itemizedlist>
				<listitem><para>David A Knight <email>david@screem.org</email></para></listitem>
				<listitem><para>Lee Mallabone <email>lee0@callnetuk.com</email></para></listitem>
				<listitem><para>Joe Orton (<application>Sitecopy</application>, as such deserves a mention here)<email>joe@light.plus.com</email></para></listitem>
				<listitem><para>Sven Liessem <email>sven_liessem@hotmail.com</email></para></listitem>
				<listitem><para>Matthew Colyer <email>linuxcoder@colyer.org</email></para></listitem>
				<listitem><para>Sven Salzwedel <email>salzwede@fh-coburg.de</email></para></listitem>
			</itemizedlist>
			<para>
				To find more information
				about it, please visit the <application>&app;</application> <ulink
					url="http://www.screem.org" type="http">Web page</ulink>.
				Please send comments, and suggestions to the mailing list, and bug reports to the
				<ulink url="http://sourceforge.net/bugs/?group_id=142" type="http">&app; bug
					tracking database</ulink>. 
			</para>
		</sect1>
		<sect1 id="manauthors">
			<title>Documenters</title>
			<para>
				This manual was written by:
			</para>
			<itemizedlist>
				<listitem><para>David A Knight 	<email>david@screem.org</email></para></listitem>
			</itemizedlist>
			<para>		
				Please send all comments
				and suggestions regarding the manual to <email>david@screem.org</email> or the
				screem mailing list.
			</para>
		</sect1>
		<sect1 id="graphics">
			<title>Artists</title>
			<para>
				The following people are responsible for the artwork/graphics in <application>&app;</application>.
				(not including the standard gtk/gnome icons)
			</para>
			<itemizedlist>
				<listitem><para>Matthew J Gardner <email>matthew@screem.org</email></para></listitem>
				<listitem><para>Matthew Colyer <email>linuxcoder@colyer.org</email></para></listitem>
				<listitem><para>Nestor Di</para></listitem>
				<listitem><para>Jakub 'jimmac' Steiner - icons used from <ulink url="http://jimmac.musichall.cz/ikony.php3">http://jimmac.musichall.cz/ikony.php3</ulink></para></listitem>
			</itemizedlist>
		</sect1>
	</appendix>
	<appendix id="bugs">
		<title>Reporting bugs</title>
		<para>
			As can be expected with software 
			<application>&app;</application> will contain bugs.  In order
			to sort this out we need your help.  If you find a bug, or
			&app; crashes and you don&apos;t know why then submit a bug
			report giving as much information on what you did, what you
			had been doing, and information about your system.
		</para>
		<para>
			The preferred way for bugs to be reported is via our
			<ulink url="http://sourceforge.net/tracker/?group_id=142&amp;atid=100142">Sourceforge Bug Tracking system</ulink>.  
			You can not use the GNOME crash dialog to submit a report
			to this.
		</para>
		<para>
			Another method would be to email your bug report to
			<ulink url="mailto:bugs@screem.org">bugs@screem.org</ulink>
		</para>
	</appendix>
	<appendix id="donations">
		<title>Donations</title>
		<para>
			You can donate money to &app; via paypal by clicking the
			"support his project" button at the bottom of the page at <ulink url="http://www.screem.org/">screem.org</ulink>
		</para>
		<para>
			Donations will be put towards the cost of the domain name, which
			has been kept going for the last 6 years by David A Knight, and
			primarily by Matthew J Gardner, without whom the domain would
			have expired a few years ago.
		</para>
	</appendix>
</book>
