# Screem User Manual &manrevision;

2000
2001
2002
2003
2004
2005
David A Knight
2000
2001
Matthew Colyer
SCREEM Development Team
David
A
Knight

    david@screem.org

This manual describes version &appversion; of &app;

## Preface

&legal;

## Introduction

### About &app;

&app; 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 GNOME desktop environment in mind it does not specifically require you to be running it, just have the libraries installed.

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'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.

Visit www.screem.org for the latest news about screem.

### Requirements

#### System Recommendations

These specifications are just guidelines and &app; will run on lower spec systems.

- 1024x768 screen resolution

- 128 Meg memory

#### Library Requirements

Unlike the system recommendations library requirements are mandatory and &app; will not run without them installed on your system.

- glib 2.6 or higher

- gtk+ 2.6 or higher

- libgnome 2.2.0 or higher

- libgnomeui 2.6.0 or higher

- libxml 2.4.3 or higher

- libglade 2.3.0 or higher

- gconf 2.2.0 or higher

- gnome-vfs 2.8.0 or higher

- libgtkhtml-2.0 2.2.0 or higher

- libgnomeprint-2.2 2.2.0 or higher

- libgnomeprintui-2.2 2.2.0 or higher

- gtksourceview 1.1.90 or higher

- dbus 0.22 or higher (optional at build time)

- dbus-glib 0.22 or higher (optional at build time)

- enchant 1.1.6 or higher (optional at build time)

## Getting Started with Screem

### Getting Started

#### To start &app;

You can start &app; in the following ways:

Applications menu

  Choose Programming &app; Website Editor

Command line

  Type `screem`, then press Return.

#### To start editing html pages straight away

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.

You can preview the results within &app; without having to start up a web browser by using the View menu. Choose the Preview menu item..

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.

### Creating new pages

There are two different ways of creating new pages / documents with &app;

From File New New Document .

  This method will present you with the new page druid, and will guide you through providing the information needed for a new HTML page.

  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.

From File New New Blank Document .

  Sometimes you may not want to go through the page druid, especially when you don't want an HTML file, but a Javascript file, or CSS file. For these occasions you can create a new blank document.

  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.

### Working with Sites

As mentioned in the "Getting Started" 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?

#### To create a new Site

From Site New Site

  The Site Druid window will then be displayed, and guide you through the necessary steps to create a new site.

From File New New Site

  This will have the same effect as if you had used the Site menu.

Opening an existing folder

  You can open any existing folder and &app; will create a site from this. see the following section on Opening an existing site

#### Opening an existing site

From Site Open

  This method will display the file selector allowing you to choose a folder. This folder will then be opened as a site.

From Site Open Location

  This method will display a dialog allowing you to enter a URL to where the site is located. This could be and FTP site, a WebDAV share, an SFTP connect, or any other method that is supported by GNOME

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.

## The Main Window

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.

### Document Views

&app; provides a number of methods of viewing the document currently being worked on.

#### The Editor View

From the View menu. Choose the Editor menu item.

The text editor based view is the main authoring section of &app;. It has all the usual features you find in gedit, the default GNOME text editor. There are of course a number of extra features geared towards editing HTML / XML documents.

##### Editor features

Context menu

  In addition to the usual right click popup menu &app; adds options to save and close the current document.

  When working on HTML / XML 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.

  If a wizard has been loaded that supports an HTML / XML tag that has been clicked on, then an option to edit the tag in the wizard will also be provided.

Enhanced copy / paste support

  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 Epiphany and paste it directly into &app; without having to search through the source of the page you are viewing. Other applications such as Abiword and Gnumeric can provide html when pasted into &app;

  The editor also has a special paste mode, which will encode the relevant characters as entities, so actual HTML can be shown in the page.

  These pasting features are available by selecting the following menu items:

  - Edit Paste

  - Edit Paste Encoded

  - Edit Paste Unformatted

Select Context

  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.

  This feature is available by selecting Edit Select Context from the main menu.

Select Element Content

  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.

  This feature is available by selecting Edit Select Element Content from the main menu.

Goto Context Start / End

  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.

  These are available from the Search Goto Context Start and Search Goto Context End menu items.

Goto Parent Element

  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.

  This is available from the Search Goto Parent Element menu item.

Special Block Operations

  A number of block operations are supported, that will operate on the whole document, or the selected text.

  - Auto indent, which will indent the block based on the document structure

  - Indent / Unindent, which will change the indentation taking no account of the document structure,

  - Encode as Entities, which will convert any necessary characters to HTML / XML entities

  - URI Encode, changes all characters to their URI encoded equivalent. e.g. a space becomes %20

  - Convert between upper / lower case for tag names.

  All of these operations are available under the Edit Block Operations submenu.

Spell Checking

  A markup aware spell checker is included, that will ignore tags, and only check their content.

  This is accessible from the Tools Spell Check menu item.

Document structure based auto indentation

  This is the same automatic indentation that is available as a block operation, but can be enabled to operate while editing, e.g. pressing Return or Tab will indent the next, or current line based on the document structure.

Intelligent tag closing

  Using this feature > will be automatically inserted when a < is entered. In addition if a / is typed between <> the correct closing tag will be automatically filled in.

Auto completion

  Based on &app; tag trees and reference files, and the type of document being edited, autocompletion may be provided.

  Auto completion is always provided for markup based documents after a < has been typed, providing a list of all tag names.

Tooltips

  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.

Inline tagging

  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.

Automatic entity insertion

  Some characters are forbidden in HTML / XML documents, such as < and >. As such the editor helps ease the use of the correct entity. Typing an & 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 &; an entity will be inserted.

Enhanced Drag and Drop support

  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 The Gimp, or a URI / file.

  Pressing Alt 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.

Error highlighting

  The editor has the option to highlight invalid markup in HTML / XML documents, if such a section is right clicked on a "Learn More" item will appear in the context menu.

  The "Learn More" feature will open your web browser to a page hosted at www.screem.org, although no help pages are currently available.

#### The Preview View

From the View menu. Choose the Preview menu item.

The preview provides a quick way of checking how your HTML pages may look in web browsers. It has rudimentary CSS support, and no support for scripting.

#### The Link View

From the View menu. Choose the Link View menu item.

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.

#### The Tree View

From the View menu. Choose the Tree View menu item.

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.

Future versions of &app; will allow you to edit from within this view

### Sidebars

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 View Dock items submenu or the close button on their individual title bars.

#### Files

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.

##### When working on single files

When working on single files you will be presented with a tree view of the local system.

##### When working on a site

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.

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

- Images

- Scripts

- Stylesheets

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.

Link updating is only supported for HTML and XML documents where the doctype in use specifies which attributes contain URIs, and for CSS files.

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.

#### Tree

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.

This is currently an informational display only, no editing can take place here.

#### Attributes

When working on an HTML / XML 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.

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.

Attributes

  This will list all the valid attributes for the tag, and allow you to change any of them.

  Any attributes that the tag is required to have will be displayed in bold.

Applied Styles

  This will list any CSS rules that will be applied to the tag. It will base this on any <link> based stylesheet in the document, any <style> tags, and any style attribute that may be present.

  Double clicking on an item in this list will take you to the file that contains the rule definition.

Description

  Provides a description of the tag if one could be extracted from the dtd.

#### Resources

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.

A number of tag trees are provided by default with screem, these are:

- Apache

- CSS 2.0

- HTML 4.0

- PHP

- Python

- Screem Javascript Library

- TEI Lite

In addition to these tag trees a special entry is added here for the current doctype in use.

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.

#### Symbols

The symbols sidebar only comes into play when working on a site. If a ctags 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.

This relies on ctags being present on your system, and the site being worked on also being local rather than on a remote system.

#### Messages and Errors

These two sidebars provide feedback messages, and errors. Any multiline messages will be shown here rather than the status bar.

Helper applications may also output to these sidebars so results can be seen, or the reason for any errors determined.

## Wizards

&app; supports plugins for providing wizards to perform common tasks more easily. All wizards are reachable from the Insert Wizards submenu, and may possibly add an icon to the wizards toolbar.

### Provided Wizards

#### Color Wizard

The color wizard provides a simple color selection dialog, which allows you to insert a color code either via the Apply or ok buttons, or by dragging a color to the editor window.

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.

#### CSS Selector Wizard

Relieving you of having to remember the different selectors for CSS 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 Insert button will insert it into the editor.

As well as allowing you to define the selector you can also set specific style properties. Click the Styles button to jump to the properties page. This will present you with a grouped display of CSS properties. Clicking the Match button will take you back to the selector page.

#### Entity Wizard

HTML 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.

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.

#### Form Wizard

The form wizard provides a simple method of setting up the submission details for a <form>. 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

#### Image Wizard

The image wizard allows you to insert an <img> tag into your HTML documents. It also supports creating thumbnailed links to images if they are too large to include inline in the page.

#### Object Wizard

The object wizard is very similar to the image wizard, but deals with the <object> tag in HTML documents. As such it can also be used to insert images that way.

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 GNOME desktop can thumbnail, such as movie files.

#### Link Wizard

This wizard will insert links to other documents in your site, or on external sites.

The Edit pop-up 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.

#### Server Side Include Wizard

Although less commonly used with sites now this wizard allows you to insert the different server side include directives into your page.

#### Table Wizard

Tables are commonly used for layout purposes in HTML 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.

## Using Templates

&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; (if not prohibited by the template's license)

### Creating Templates

Templates can only be created when working on a site, not when working on individual files

Creating a template is no different to creating a normal document. The difference comes when you save it. From the File menu choose, Save As Template .

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)

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.

### Adding Editable Regions

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.

To add an editable region choose Editable Regions Create Editable Region... from the Edit menu.

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.

### Modifying a Template

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.

If there are areas of a document you want to stay intact after a template has updated look into using editable regions

## Helper Applications

Adding, editing, and removing helpers is all done via the edit helpers dialog. This is under the Tools menu as Helpers Edit Helpers

### Adding Helpers

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.

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.

#### Input:

- Page text This mode will feed the current document to the helper when it is used.

  If you only want part of the document to be processed simply select it in the editor view.

- Used defined 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.

- None As the name would suggest, no input will be given to the helper.

#### Output:

- Replaces Page This mode will replace the current document with the output (on stdout) of the helper.

  If you only want part of the document to be processed simply select it in the editor view.

- Inserted into page This mode will insert the helper output (on stdout) at the current cursor position.

  Not implemented yet

- Shown as messages The output of the helper (on stdout) will be displayed in the messages window.

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 Execute helper when saving documents checkbox, and then select the type of file you want the helper to be used for.

After you have filled in all the details click the Add button and the helper will be added to the list, and appear in the menu with any others you have already created.

### Editing Helpers

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 refresh button.

### Removing Helpers

Choose the helper you want to remove from the list shown in the edit helpers dialog, and then click the Remove button.

### System Wide Helpers

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 `<prefix>/share/screem` where <prefix> is the path &app; is installed to. (this will generally be `/usr` if you are using a packaged version.)

You can organized `<prefix>/share/screem` by placing related helpers in subfolders if you choose to.

### Passing extra information to helpers

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:

#### Special flags

Flag | Purpose
--- | ---
%f | current document filename, including directory
%U | current document uri
%d | current document directory
%S | current site directory
%p | uri the published site can be viewed at.
%% | a normal % character, should you need one

### Preincluded Helpers

&app; comes with some predefined helpers for the following purposes:

#### Predefined Helpers

Name | Purpose
--- | ---
Tidy (HTML) | This helper runs HTML Tidy on the current document, indenting it, and replacing the document with the tidied HTML
Tidy (XML) | Like Tidy (HTML) this helper runs HTML Tidy on the current document the only difference being it is meant for use with XML documents instead of HTML

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.

## Configuring &app;

From the Edit menu. Choose the Preferences menu item for the main preferences dialog

### Preferences Dialog

The preferences dialog is split into six sections.

- Misc

- Fonts & Colors

- Editor

- Doctypes

- Tag Trees

#### Misc

There are four items provided in the defaults section of this tab.

Page Filename

  This defines the filename that will be created as an initial file when creating a new site.

Character Set

  The default character set to use in documents if one isn't specified by the document itself. The default is UTF-8

  HTML / XML documents are the only types of document that the character set can be detected from.

Doctype

  The default markup document type to use for pages that don't specify one.

  The doctype is used in building up the tree view of the document, and providing the current doctype tag tree in the resources sidebar and providing autocompletion. The default is transitional HTML 4.01.

Blank document type

  The type of document that will be created when creating a new blank document. This defaults to an HTML document.

#### Fonts & Colors

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.

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.

#### Editor

The editor tab is split into two sections.

- Appearance

  Syntax Highlighting

    Use syntax highlighting where available

  Error Highlighting

    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.

    A Learn More option is also added to the popup menu in the editor when clicking on a highlighted section.

  Wrap lines

    Controls if long lines wrap, or if a horizontal scrollbar will be used instead.

  Tab Width

    controls how wide tabs are.

  Right column margin

    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.

- Features

  Inline Tagging

    Enables the inline tagging feature, where pressing space inside a tag presents the autocompletion popup with a list of all valid attributes.

  Auto Indent

    This option controls if document tree based auto indentation should be used rather than normal indentation based on the type of document being edited.

  Intelligent tag closing

    When typing `</` &app; can automatically fill in the correct closing tag name with this option enabled.

  Auto complete from tag trees

    Tag trees which specify the type of document they are for can be used to provide autocompletion with this feature enabled.

    Along side the PHP tag tree this provides &app; with autocompletion for all PHP4 functions.

  Show function definition tooltips

    As well as using tag trees for autocompletion, this option will show tooltips for functions contained within a tag tree.

    Using the PHP tag tree as and example again this will provide tooltips showing the definition of all PHP4 functions.

  Insert spaces instead of tabs

    Use the equivalent number of spaces instead of tab characters.

  Auto entity insertion

    This controls if &app; will insert character entities in markup class documents if the typed character should be encoded.

    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.

#### Doctypes

All DTDs available to &app; will be listed here. (most will be hidden by default) to avoid clutter.

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.

&app; attempts to guess the root element for a given DTD but may not always get this correct. Selecting the Override Root Element checkbox allows you to specify what the element is for the selected doctype.

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 W3C HTML validator won't be able to validate against the DTD correctly.

#### Tag Trees

This tab displays a list of all tag tree files that are available, and where they are stored.

If you do not want specific tree files to be loaded you can simply click the checkbox in the Active column of the list.

Additional files can be added from any location you like by clicking Add. Any tag trees added like this can also be removed by selecting them in the list, and clicking Remove.

If a tag tree file changes, you can force &app; to reload it, by selecting it in the list and clicking Refresh.

### Toolbars

#### Displaying

From the View menu you can show / hide both the main toolbars and the wizard toolbar.

Choose the Main Toolbar toggle button to hide/show the main toolbar, and any additional toolbars you add.

Choose the Wizard Toolbar toggle button to hide/show the wizard toolbar.

#### Appearance

The toolbars will follow the default appearance of your desktop, should you wish to change this, so they display

- Icons only

- Text only

- Text for all icons

- Text for important icons

or revert back to Desktop default then choose the appropriate item from the View Toolbar Appearance menu.

#### Changing toolbar buttons

&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.

- To add or remove buttons from your toolbar, select Edit Toolbars

- To add a new toolbar, click Add Toolbar in the toolbar editor.

- To remove a toolbar, remove all items from it. The toolbar will then automatically be removed.

- Drag buttons, to rearrange them either on the same toolbar or between different toolbars.

## Shortcuts

### Keyboard Shortcuts

#### File menu

Shortcut | Description
--- | ---
Ctrl+N | New Document
Ctrl+O | Open
Ctrl+L | Open Location
Ctrl+S | Save Document
Shift+Ctrl+S | Save Document as
Shift+Ctrl+P | Print Preview
Ctrl+P | Print
Ctrl+W | Close Document
Ctrl+Q | Quit &app;

#### Edit menu

Shortcut | Description
--- | ---
Ctrl+Z | Undo
Shift+Ctrl+Z | Redo
Ctrl+X | Cut
Ctrl+C | Copy
Ctrl+V | Paste
Ctrl+A | Select All
Shift+Ctrl+A | Select current context
Shift+Ctrl+C | Select current element content
Shift+Ctrl+I | Indent
Shift+Ctrl+U | Unindent
Ctrl+B | Bookmarks

#### View menu

Shortcut | Description
--- | ---
Ctrl+F1 | Show/Hide message window
Ctrl+F2 | Show/Hide error window
Ctrl+F4 | Show/Hide File browser
Ctrl+F5 | Show/Hide Resources
Ctrl+F6 | Show/Hide document structure tree
Ctrl+F7 | Show/Hide attributes
Ctrl+F8 | Show/Hide Symbol browser
Shift+Ctrl+T | Show/Hide Main Toolbar
Ctrl+1 | Switch to editor view
Ctrl+2 | Switch to internal preview view
Ctrl+3 | Switch to link view
Ctrl+4 | Switch to tree view

#### Search menu

Shortcut | Description
--- | ---
Ctrl+F | Find
Ctrl+G | Find Again
Ctrl+H | Find/Replace
Ctrl+I | Goto Line
Ctrl+[ | Goto Context Start
Ctrl+] | Goto Context End
Alt+Up | Goto Parent Element

#### Documents menu

Shortcut | Description
--- | ---
Ctrl+Page Up | Previous Document
Ctrl+Page Down | Next Document
Shift+Ctrl+L | Save All Documents
Shift+Ctrl+W | Close All Documents
Alt+1 | Switch to first document
Alt+2 | Switch to second document
Alt+3 | Switch to third document
Alt+4 | Switch to fourth document
Alt+5 | Switch to fifth document
Alt+6 | Switch to sixth document
Alt+7 | Switch to seventh document
Alt+8 | Switch to eighth document
Alt+9 | Switch to nineth document

#### Help menu

Shortcut | Description
--- | ---
F1 | Show this manual

## Authors

### Developers

&app; was written by:

- David A Knight david@screem.org

- Lee Mallabone lee0@callnetuk.com

- Joe Orton (Sitecopy, as such deserves a mention here)joe@light.plus.com

- Sven Liessem sven_liessem@hotmail.com

- Matthew Colyer linuxcoder@colyer.org

- Sven Salzwedel salzwede@fh-coburg.de

To find more information about it, please visit the &app; Web page. Please send comments, and suggestions to the mailing list, and bug reports to the &app; bug tracking database.

### Documenters

This manual was written by:

- David A Knight david@screem.org

Please send all comments and suggestions regarding the manual to david@screem.org or the screem mailing list.

### Artists

The following people are responsible for the artwork/graphics in &app;. (not including the standard gtk/gnome icons)

- Matthew J Gardner matthew@screem.org

- Matthew Colyer linuxcoder@colyer.org

- Nestor Di

- Jakub 'jimmac' Steiner - icons used from http://jimmac.musichall.cz/ikony.php3

## Reporting bugs

As can be expected with software &app; will contain bugs. In order to sort this out we need your help. If you find a bug, or &app; crashes and you don'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.

The preferred way for bugs to be reported is via our Sourceforge Bug Tracking system. You can not use the GNOME crash dialog to submit a report to this.

Another method would be to email your bug report to bugs@screem.org

## Donations

You can donate money to &app; via paypal by clicking the "support his project" button at the bottom of the page at screem.org

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.