Menu
▾
▴
[Tora-cvs] SF.net SVN: tora: [2093] trunk/tora/doc/help
|
From: <nn...@us...> - 2007-01-10 17:15:05
|
Revision: 2093
http://svn.sourceforge.net/tora/?rev=2093&view=rev
Author: nneul
Date: 2007-01-10 09:14:58 -0800 (Wed, 10 Jan 2007)
Log Message:
-----------
remove generated html
Removed Paths:
-------------
trunk/tora/doc/help/additionalhelp.html
trunk/tora/doc/help/alert.html
trunk/tora/doc/help/analyze.html
trunk/tora/doc/help/api.html
trunk/tora/doc/help/browser.html
trunk/tora/doc/help/charts.html
trunk/tora/doc/help/common.html
trunk/tora/doc/help/current.html
trunk/tora/doc/help/database.html
trunk/tora/doc/help/debugger.html
trunk/tora/doc/help/editors.html
trunk/tora/doc/help/fonts.html
trunk/tora/doc/help/help.html
trunk/tora/doc/help/history.html
trunk/tora/doc/help/invalid.html
trunk/tora/doc/help/lists.html
trunk/tora/doc/help/newconnection.html
trunk/tora/doc/help/output.html
trunk/tora/doc/help/preferences.html
trunk/tora/doc/help/rollback.html
trunk/tora/doc/help/script.html
trunk/tora/doc/help/searchreplace.html
trunk/tora/doc/help/security.html
trunk/tora/doc/help/session.html
trunk/tora/doc/help/sqledit.html
trunk/tora/doc/help/storage.html
trunk/tora/doc/help/template.html
trunk/tora/doc/help/toc.htm
trunk/tora/doc/help/tools.html
trunk/tora/doc/help/toolsetting.html
trunk/tora/doc/help/trace.html
trunk/tora/doc/help/tuning.html
trunk/tora/doc/help/window.html
trunk/tora/doc/help/worksheet.html
trunk/tora/doc/help/workspace.html
Deleted: trunk/tora/doc/help/additionalhelp.html
===================================================================
--- trunk/tora/doc/help/additionalhelp.html 2007-01-10 17:14:27 UTC (rev 2092)
+++ trunk/tora/doc/help/additionalhelp.html 2007-01-10 17:14:58 UTC (rev 2093)
@@ -1,28 +0,0 @@
-<HTML><HEAD><TITLE>Additional Help Settings</TITLE></HEAD><BODY>
-<H1>Additional Help Settings</H1>
-This page is used to configure extra manuals for viewing in the TOra help viewer. Specifically
-the Oracle HTML based manuals which contents can be parsed and included in the left pane contents
-tree of the TOra help.<P>
-<IMG SRC=images/additionalhelp.png><P>
-If you have compiled TOra with KDE support (Not Windows or Qt versions) you can point this to any
-HTTP location. You could even use the help browser to browse the Oracle manuals directly from
-Technet if you wanted to (Free membership required).<P>
-<TABLE>
-<TR><TD VALIGN=top>
-<B>Remove path</B></TD>
-<TD VALIGN=top>This will remove the currently selected manual from the list.</TD></TR>
-<TR><TD VALIGN=top>
-<B>Oracle Manuals</B></TD>
-<TD VALIGN=top>This is a quick way to add a collection of manuals. When you select this button a
-dialog will pop up and ask you for a filename. In Oracle 8 this should be the index page that contains
-the links to the manuals. Observe that this is not the page which links to the different
-book categories. In Oracle 9i you should point it to the docindex.htm file in the base
-directory of the documentation. If successful all the manuals available on the page
-is added to the list of manuals.</TD></TR>
-<TR><TD VALIGN=top>
-<B>Add path</B></TD>
-<TD VALIGN=top>Add a manual to the list of manuals. This pop up a dialog asking for the name
-of the manual and the location of the manuals table of contents HTML file (toc.htm).</TD></TR>
-</TABLE>
-</BODY>
-</HTML>
\ No newline at end of file
Deleted: trunk/tora/doc/help/alert.html
===================================================================
--- trunk/tora/doc/help/alert.html 2007-01-10 17:14:27 UTC (rev 2092)
+++ trunk/tora/doc/help/alert.html 2007-01-10 17:14:58 UTC (rev 2093)
@@ -1,37 +0,0 @@
-<HTML><HEAD><TITLE>Alert Tool</TITLE></HEAD><BODY>
-<H1>Alert Tool</H1>
-This tool is usefull for debugging database packages that send or depend on receiving
-dbms alerts.<P>
-<IMG SRC=images/alert.png><P>
-This tool is controled solely from it's toolbar which is followed by a list containing the
-alerts received so far on the watched alerts. The toolbar contains the following controls.<P>
-<TABLE>
-<TR><TD VALIGN=top><B>Registered</B></TD>
-<TD>This list contains the alerts that are registered for listening. To add a new alert
-simply write the name in this combo box and press return or the <B>register current</B>
-button immediately to the right. To remove an alert select it in the list and press the
-<B>remove registered</B> button.
-</TD></TR>
-<TR><TD VALIGN=top><B>Register current</B></TD>
-<TD>Register the name currently entered in the <B>registered</B> combo box.
-</TD></TR>
-<TR><TD VALIGN=top><B>Remove registered</B></TD>
-<TD>Stop listening to the registered alert currently selected in the <B>registered</B>
-combo box.
-</TD></TR>
-<TR><TD VALIGN=top><B>Name</B></TD>
-<TD>Name of the alert to send.
-</TD></TR>
-<TR><TD VALIGN=top><B>Message</B></TD>
-<TD>Message to send in an alert. Pressing return in this lineedit will send the alert.
-</TD></TR>
-<TR><TD VALIGN=top><B>Edit message in memo</B></TD>
-<TD>Edit the message in a memo editor, usefull for sending newlines and longer messages.
-</TD></TR>
-<TR><TD VALIGN=top><B>Send alert</B></TD>
-<TD>Send the currently defined alert. You can also send an alert by pressing return in the
-<B>message</B> line editor.
-</TD></TR>
-</TABLE>
-</BODY>
-</HTML>
Deleted: trunk/tora/doc/help/analyze.html
===================================================================
--- trunk/tora/doc/help/analyze.html 2007-01-10 17:14:27 UTC (rev 2092)
+++ trunk/tora/doc/help/analyze.html 2007-01-10 17:14:58 UTC (rev 2093)
@@ -1,53 +0,0 @@
-<HTML><HEAD><TITLE>Statistics manager</TITLE></HEAD><BODY>
-<H1>Statistics manager</H1>
-This tool is usefull for collecting statistics and analyze tables in parallel. You can also
-use it to browse collected statistics.<P>
-<IMG SRC=images/analyze.png><P>
-You control the interface through the controls in the toolbar. The rest of the interface simply
-displays currently available tables in the current schema. When collecting statistics only the
-selected items in the tablelist are analyzed.<P>
-<TABLE>
-<TR><TD VALIGN=top><B>
-Refresh
-</B></TD><TD>
-Refresh the table list from the database.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Schema
-</B></TD><TD>
-The next control is which schema to investigate tables for.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Operation
-</B></TD><TD>
-What operation to perform. Select one of <B>compute statistics</B>, <B>estimate statistics</B>, <B>delete statistics</B> and <B>validate references</B>.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Target
-</B></TD><TD>
-Depending on the <B>operation</B> you can sometimes select what kind of statistic to collect. Choose between <B>all</B>, <B>table</B>, <B>indexed columns</B> and <B>local indexes</B>.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Sample
-</B></TD><TD>
-If the <B>operation</B> is <B>estimate statistics</B> you can choose how large sample should be used to estimate the statistic information in percent of
-total amount of data.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Parallel
-</B></TD><TD>
-Indicate the number of separate connections to open to the database and run collecting statistics concurrently when collecting.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Start analyzing
-</B></TD><TD>
-Press this button to perform the indicated operation on the tables selected in the list below the toolbar.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Stop
-</B></TD><TD>
-Stop current run. Before the stop button you can also see information about the currently running statistics gathering run if any is running.
-</TD></TR>
-</TABLE>
-</BODY>
-</HTML>
Deleted: trunk/tora/doc/help/api.html
===================================================================
--- trunk/tora/doc/help/api.html 2007-01-10 17:14:27 UTC (rev 2092)
+++ trunk/tora/doc/help/api.html 2007-01-10 17:14:58 UTC (rev 2093)
@@ -1,254 +0,0 @@
-<HTML>
-<HEAD>
-<TITLE>TOra Tool Tutorial</TITLE>
-</HEAD>
-<BODY bgcolor="#ffffff" text="#000000" link="#0000ff" vlink="#000099" alink= "#ffffff">
-<H1>TOra Tool Tutorial</H1>
-This tutorial will create a simple tool that can execute an SQL statement and display it's
-content in a list. This tutorial assumes you have knowledge of C++ and Qt programming.<p>
-
-First of all we create an include file which defines the tool widget. This is the window
-that will be displayed when the a tool window is created. How that happens comes later.<p>
-
-<table width=100% border=0><tr><td bgcolor="#BEEAE0">
-<pre>
-#ifndef TOSIMPLEQUERY_H
-#define TOSIMPLEQUERY_H
-
-#include "totool.h"
-
-class <A HREF=api/toResultView.html>toResultView</A>;
-class QLineEdit;
-class <A HREF=api/toConnection.html>toConnection</A>;
-
-class toSimpleQuery : public <A HREF=api/toToolWidget.html>toToolWidget</A> {
- Q_OBJECT
-
- <A HREF=api/toResultView.html>toResultView</A> *Result;
- QLineEdit *Statement;
-private slots:
- void execute(void);
-public:
- toSimpleQuery(QWidget *parent,<A HREF=api/toConnection.html>toConnection</A> &connection);
-};
-
-#endif
-</pre></td></tr><tr><td align=right>tosimplequery.h</td></tr></table>
-
-If this file is put in the main TOra source directory the configure script will generate the
-appropriate moc file which will be needed later. If you don't know what moc is, please go back
-to the Qt manual to read up on slots and signals.<p>
-The rest is pretty straight forward and will be much clearer after we start working our
-way through the implementation of this tool.<p>
-
-The first thing we need to do is create a tool description which is done by subclassing the
-<A HREF=api/toTool.html>toTool</A> class. This is how we implement this class for this function.
-<p>
-<table width=100% border=0><tr><td bgcolor="#BEEAE0">
-<pre>
-#include "totool.h"
-#include "tosimplequery.h"
-
-static char * tosimplequery_xpm[] = {
-"16 16 3 1",
-" c None",
-". c #000000",
-"+ c #FFFFFF",
-" ...... ",
-" ..++++. ",
-" .+.++++. ",
-" .++.++++. ",
-" .....++++. ",
-" .++++++++. ",
-" .++++++++. ",
-" .++++++++. ",
-" .++++++++. ",
-" .++++++++. ",
-" .++++++++. ",
-" .++++++++. ",
-" .++++++++. ",
-" .++++++++. ",
-" .++++++++. ",
-" .......... "};
-
-class toSimpleQueryTool : public <A HREF=api/toTool.html>toTool</A> {
-protected:
- virtual char **pictureXPM(void)
- { return tosimplequery_xpm; }
-public:
- toSimpleQueryTool()
- : toTool(203,"Simple Query")
- { }
- virtual const char *menuItem()
- { return "Simple Query"; }
- virtual QWidget *toolWindow(QWidget *parent,<A HREF=api/toConnection.html>toConnection</A> &connection)
- {
- return new toSimpleQuery(parent,connection);
- }
-};
-
-static toSimpleQueryTool SimpleQueryTool;
-</pre></td></tr><tr><td align=right>tosimplequery.cpp</td></tr></table>
-
-The first thing that happens is that we include the header file which defines the tool widget and
-the tool definition header files. Even if this is included in the <code>tosimplequery.h</code> it
-is good practice not to assume any extra files are included by header files.<p>
-
-Next comes a definition of an xpm pixmap. Normally these are placed in the <code>icons</code>
-directory and then included into the file as you can see in the TOra source. This is placed
-inline for clarity.<p>
-
-The next one is the big one. Here we define the tool class which has a few important
-virtual functions.<p>
-<table border=0 width=100%>
-<tr><td valign=top><code>pictureXPM</code></td>
-<td>This function should if defined return a pointer to a xpm definition.
-This will then be used for toolbar icon, menu icon and tool window icon.
-</td></tr>
-<tr><td valign=top><code>menuItem</code></td>
-<td>Should return a string containing the name of the menu item to add to the tools menu. This
-is also used for a tip for the toolbar icon by default.
-</td></tr>
-<tr><td valign=top><code>toolWindow</code></td>
-<td>This function will create a new tool widget and return a pointer to it. It doesn't need
-to create a widget, then it should then return NULL. Some tools there might only be one per
-connection for instance.
-</td></tr>
-</table><p>
-
-The number in the constructor is a priority indicator that denote where in the list of
-tools this tool should be inserted, between each 100 step a separator is inserted into
-the toolbar and menubar.<p>
-
-And last a not so obvious line where the an instance of the tool descriptor is instantiated.
-This is a feature that is used a lot in TOra. This will ensure that all tools are registered
-when the application is started. It also works when using modules, if this is compiled as
-a module the tool will be instantiated on loading without any hassle with functions with
-predefined names and such stuff.<p>
-
-Lastly comes the implementation of the tool widget which is not much longer. I have divided
-this into several parts to simplify explaining them<p>
-<table width=100% border=0><tr><td bgcolor="#BEEAE0">
-<pre>
-#include <list>
-
-#include <qtoolbar.h>
-#include <qlabel.h>
-#include <qtoolbutton.h>
-#include <qlineedit.h>
-
-#include "tosimplequery.h"
-#include "toresultview.h"
-#include "toparamget.h"
-#include "tochangeconnection.h"
-
-#include "tosimplequery.moc"
-
-static char * execute_xpm[] = {
-"16 16 3 1",
-" c None",
-". c #000000",
-"+ c #0FFE14",
-" ",
-" ",
-" ",
-" . ",
-" .. ",
-" .+. ",
-" .++. ",
-" .+++. ",
-" .+++. ",
-" .++. ",
-" .+. ",
-" .. ",
-" . ",
-" ",
-" ",
-" "};
-
-toSimpleQuery::toSimpleQuery(QWidget *main,<A HREF=api/toConnection.html>toConnection</A> &connection)
- : <A HREF=api/toConnection.html>toToolWidget</A>(SimpleQueryTool,"simplequery.html",main,connection)
-{
- QToolBar *toolbar=toAllocBar(this,"Simple Query",connection.description());
- QPixmap executePixmap((const char **)execute_xpm);
- new QToolButton(executePixmap,
- "Execute current statement",
- "Execute current statement",
- this,SLOT(execute()),
- toolbar);
- toolbar->setStretchableWidget(new QLabel("",toolbar));
- new <A HREF=api/toChangeConnection.html>toChangeConnection</A>(toolbar);
-</pre></td></tr><tr><td align=right>tosimplequery.cpp</td></tr></table><p>
-
-In this part the parent constructor is called and the toolbar is set up. Also note the inclusion
-of the moc file which by convention is called tosimplequery.moc.
-
-One thing worth noticing here is the <code>toAllocBar</code> which is used to be able to
-transparently support either using KToolBar or QToolBar depending on whether this is a Qt or
-KDE application. This is very important since TOra also supports windows to which KDE is not available.<p>
-
-The second part is the <code>setStretchableWidget</code> call which is used to indicate that
-an empty label should be stretch instead of the tool button which just looks really weird.<p>
-
-Also worth noting is that the <A HREF=api/toToolWidget.html>toToolWidget</A> class is derived
-from QVBox so any widgets constructed in this widget will be lined up vertically in the order
-of creation.<p>
-
-Next up is creating our widgets and connecting them.<p>
-<table width=100% border=0><tr><td bgcolor="#BEEAE0">
-<pre>
- Statement=new QLineEdit(this);
- Result=new <A HREF=api/toResultView.html>toResultView</A>(this);
- connect(Statement,SIGNAL(returnPressed()),this,SLOT(execute()));
-}
-
-</pre></td></tr><tr><td align=right>tosimplequery.cpp</td></tr></table><p>
-
-This just adds two additional widgets and connect the <code>returnPressed</code> signal to
-the <code>execute</code> slot. One thing to realise here is that all the toResult children
-will use the connection of the closest parent of type
-<A HREF=api/toToolWidget.html>toToolWidget</A> in the widget hierarchy. And now the last
-thing to do is implement the execute method.<p>
-
-<table width=100% border=0><tr><td bgcolor="#BEEAE0">
-<pre>
-
-void toSimpleQuery::execute(void)
-{
- try {
- QString sql=Statement->text();
- toQList params=<A HREF=api/toParamGet.html>toParamGet</A>::getParam(this,sql);
- Result->query(sql,params);
- } TOCATCH
-}
-
-</pre></td></tr><tr><td align=right>tosimplequery.cpp</td></tr></table><p>
-
-The toParamGet::getParam function is used to ask for bind values in the query string. To understand
-what I mean try executing the query "select :hello from dual" when you try the result. The toQList
-is simple a list of <A HREF=api/toQValue.html>toQValue</A> which can hold different datatypes and
-converting between them transparently.<P>
-
-Now finally to compile this module you need to add the <code>tosimplequery.cpp</code> file
-to <code>SOURCES</code> define in the file <code>Makefile</code>. To build a plugin you also
-need to add the following line.<p>
-
-<table width=100% border=0><tr><td bgcolor="#BEEAE0">
-<pre>
-plugins/tosimplequery.tso:objs/tosimplequery.o
-</pre></td></tr><tr><td align=right>Makefile</td></tr></table><p>
-
-This should go among the other plugin definitions and you also need to add the
-<code>plugins/tosimplequery.tso</code> to the dependencies of <code>tora-plugin</code>.<p>
-
-You must rerun configure for the tosimplequery.moc file to be generated the first time.
-Any subsequent changes should update the moc file automatically from the Makefile.<p>
-
-Here are the example files in their entire.<p>
-<A HREF=tosimplequery.h>tosimplequery.h</A><br>
-<A HREF=tosimplequery.cpp>tosimplequery.cpp</a><p>
-
-Hopefully this is a starting point to help you read the rest of the documentation and
-start cranking out those plugins.
-</BODY>
-</HTML>
Deleted: trunk/tora/doc/help/browser.html
===================================================================
--- trunk/tora/doc/help/browser.html 2007-01-10 17:14:27 UTC (rev 2092)
+++ trunk/tora/doc/help/browser.html 2007-01-10 17:14:58 UTC (rev 2093)
@@ -1,309 +0,0 @@
-<HTML><HEAD><TITLE>Database Browser</TITLE></HEAD><BODY>
-<H1>Database Browser</H1>
-This tool provides you a simple browser for exploring database schema objects. Initially it can
-be said that the browser also provides a browser like functionality for the
-<A HREF=template.html>template help</A> which is covered separately. This browser will provide
-you with more information and you will also in future versions of TOra be able to interact with
-schema objects (Dropping or create tables etc.), this is not possible in the template help version.
-The <A HREF=template.html>template help</A> on the other hand is tree based and some people
-consider it easier and faster to work with.<P>
-<IMG SRC=images/browser.png><P>
-<H2>Using the browser</H2>
-The database browser has a very simple interface with a toolbar which contain the following
-functions. All of these are also available in the <B>Browser</B> menu item except for the
-schema selection and change object.<P>
-<TABLE>
-<TR><TD VALIGN=top><B>
-Refresh
-</B></TD><TD>
-Refresh the displayed data from the database. Also available on the
-<B>F5</B> key.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Define filter</B></TD><TD>
-Displays the <A HREF=browser.html#filter>define filter dialog</A>. This is used to specify which
-objects to show in the browser. The default filter is to show everything. Also available on the
-<B>CTRL+SHIFT+G</B> key.</TD></TR>
-<TR><TD VALIGN=top><B>
-Clear filter</B></TD><TD>
-Remove the current filter and revert to the default of showing everything. Also available on the
-<B>CTRL+SHIFT+H</B> key.</TD></TR>
-<TR><TD VALIGN=top><B>
-Schema</B></TD><TD>
-The last item on the toolbar is a combo box where you can select the schema to display
-objects for. It defaults the schema you are currently logged in as. Only schemas that are
-visible to the current user is selectable in the lost (Really, TOra does not contain the
-secret DBA password that will always let you access everything regardless of your privileges).
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Change connection</B></TD>
-<TD VALIGN=top>
-Change the connection this tool window should operate on.</TD></TR>
-</TABLE><P>
-The rest of the interface consists of two tabbed windows, one within the other. The first one
-you can use to select the object type you want to inspect. When you have selected a type you
-can see the visible objects of the specified type available in the selected schema. The second
-tab indicate what kind of information you want to explore about the selected object and depends
-on the object type (For more information about available information see
-<A HREF=browser.html#types>this</A>). When you select an object name in the left list you
-can inspect information about it to the right.<P>
-You can move the keyboard focus to the schema selection using <B>ALT+S</B> and to the current
-object list using <B>ALT+N</B>.
-<A NAME=types><H2>Available information</H2>
-This is the available information for the different object types.<P>
-<TABLE>
-<TR><TD><I>Object type</I></TD><TD><I>Name</I></TD><TD><I>Description</I></TD></TR>
-<TR><TD VALIGN=top><B>
-Tables</B></TD><TD></TD><TD VALIGN=top>
-</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Columns</B></TD><TD VALIGN=top>
-A description of the columns in the table. For more information about this information also see
-<A HREF=common.html#describe>object description</A>.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Indexes</B></TD><TD VALIGN=top>
-A list with the indexes that have been created for this table.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Constraints</B></TD><TD VALIGN=top>
-Lists the constraints for this table.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-References</B></TD><TD VALIGN=top>
-Displays the foreign key constraints that references this table and the other objects that have
-dependencies on this table.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Grants</B></TD><TD VALIGN=top>
-The grants that have been made on this table.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Triggers</B></TD><TD VALIGN=top>
-Lists the triggers that exist for this table.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Data</B></TD><TD VALIGN=top>
-Displays the data in the table. This is the only part of the database browser that let you modify any data. For
-more information about how to use the content editor see <A HREF=browser.html#content>this</A>.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Information</B></TD><TD VALIGN=top>
-Contains information about the table available in the SGA including
-analyzed statistics etc.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Script</B></TD><TD VALIGN=top>
-This tab displays an SQL script to recreate the database object.</TD></TR>
-<TR><TD VALIGN=top><B>
-Views</B></TD><TD></TD><TD VALIGN=top>
-</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Columns</B></TD><TD VALIGN=top>
-A description of the columns in the view. For more information about this information also see
-<A HREF=common.html#describe>object description</A>.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-SQL</B></TD><TD VALIGN=top>
-The SQL that defines the view.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Data</B></TD><TD VALIGN=top>
-Displays the data in the view. This is the only part of the database browser that let you modify any data. For
-more information about how to use the content editor see <A HREF=browser.html#content>this</A>. You can not
-modify some views depending on how they are defined. See the Oracle reference for more information about editing
-views.
-</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Grants</B></TD><TD VALIGN=top>
-The grants that have been made on this view.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Dependencies</B></TD><TD VALIGN=top>
-The objects that depend on this view.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Script</B></TD><TD VALIGN=top>
-This tab displays an SQL script to recreate the database object.</TD></TR>
-<TR><TD VALIGN=top><B>
-Indexes</B></TD><TD></TD><TD VALIGN=top>
-</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Columns</B></TD><TD VALIGN=top>
-The columns that the index operate on.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Info</B></TD><TD VALIGN=top>
-Information in the SGA about an index. For instance analyzed statistics available for this index.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Script</B></TD><TD VALIGN=top>
-This tab displays an SQL script to recreate the database object.</TD></TR>
-<TR><TD VALIGN=top><B>
-Sequences</B></TD><TD></TD><TD VALIGN=top>
-</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Info</B></TD><TD VALIGN=top>
-Information about the sequence.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Grants</B></TD><TD VALIGN=top>
-The grants that have been made on this object.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Script</B></TD><TD VALIGN=top>
-This tab displays an SQL script to recreate the database object.</TD></TR>
-<TR><TD VALIGN=top><B>
-Synonyms</B></TD><TD></TD><TD VALIGN=top>
-</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Info</B></TD><TD VALIGN=top>
-Information about the synonyms</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Grants</B></TD><TD VALIGN=top>
-The grants that have been made on this object.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Script</B></TD><TD VALIGN=top>
-This tab displays an SQL script to recreate the database object.</TD></TR>
-<TR><TD VALIGN=top><B>
-PL/SQL</B></TD><TD></TD><TD VALIGN=top>
-</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Declaration</B></TD><TD VALIGN=top>
-The declaration of a package or type.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Body</B></TD><TD VALIGN=top>
-The implementation of a package, body, procedure or function.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Grants</B></TD><TD VALIGN=top>
-The grants that have been made on this object.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Dependencies</B></TD><TD VALIGN=top>
-Dependencies this object has.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Script</B></TD><TD VALIGN=top>
-This tab displays an SQL script to recreate the database object.</TD></TR>
-<TR><TD VALIGN=top><B>
-Triggers</B></TD><TD></TD><TD VALIGN=top>
-</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Info</B></TD><TD VALIGN=top>
-Information about the trigger.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Code</B></TD><TD VALIGN=top>
-The code that implement the trigger.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Columns</B></TD><TD VALIGN=top>
-The columns this trigger operates on.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Grants</B></TD><TD VALIGN=top>
-The grants that have been made on this object.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Dependencies</B></TD><TD VALIGN=top>
-Dependencies of this object.</TD></TR>
-<TR><TD></TD><TD VALIGN=top><B>
-Script</B></TD><TD VALIGN=top>
-This tab displays an SQL script to recreate the database object.</TD></TR>
-</TABLE><P>
-<A NAME=content><H2>Content editor</H2>
-The content let you edit the contents of a table or view. There are a few things to note about this.<P>
-First of all the content editor is designed to behave nicely to the database which means that it
-will only save the data when it thinks you are finished editing a row. This happens when you the current row
-change or you commit the database. When there is unsaved data you can see it in the status bar that there
-exists unsaved data. Also observe that the content editor will respect the auto commit setting in the
-<A HREF=database.html>database settings</A>.<P>
-The content editor has it's own toolbar with the following buttons.<P>
-<TABLE>
-<TR><TD VALIGN=top><B>
-Define filter</B></TD><TD>
-Displays the <A HREF=browser.html#contentfilter>define filter dialog</A>. This is used to specify which
-objects to show in the browser. The default filter is to show everything.</TD></TR>
-<TR><TD VALIGN=top><B>
-Clear filter</B></TD><TD>
-Remove the current filter and revert to the default of showing everything.</TD></TR>
-<TR><TD VALIGN=top><B>
-Add new record
-</B></TD><TD>
-Add a new record to the current table.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Save changes
-</B></TD><TD>
-Save the changes made to the current row to the database. Observe that this will not commit the changes.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Discard changes
-</B></TD><TD>
-Discard the changes made to the current row to the database. Observe that this will not rollback the database connection.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Delete current record
-</B></TD><TD>
-Delete the current record from the database.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Go to first row
-</B></TD><TD>
-Go to the first record in the editor.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Go to previous row
-</B></TD><TD>
-Go to the previous record in the editor.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Go to next row
-</B></TD><TD>
-Go to the next record in the editor.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Go to last row
-</B></TD><TD>
-Go to the last record in the editor. Observe that this will read in all available records in the table into memory.
-</TD></TR>
-</TABLE><P>
-<A NAME=contentfilter>
-The content editor can define a fileter to specify which part of a table to edit. This dialog looks like this.<P>
-<IMG SRC=images/contentfilter.png><P>
-In the <B>selection criteria</B> part you can add whatever you want to go after a <B>where</B> in a select statement.
-In the <B>sort order</B> you can list the columns you want to sort on. The sort order only affect the order the records
-are read from the database, after they are read you can still sort on any column by clicking it. To the right is a
-list of available columns in the table.<P>
-Finally at the bottom is a checkbox called <B>use for all tables</B>. If this box is checked the index is used for
-all tables, if not checked you can define specific filters for each tables and the content editor will remember the
-different filters as you jump between tables. The reason for this is that it's quite common that not all tables have
-all the columns you want to filter on for a table, in this case you will get an error trying to access the table
-with a faulty filter setting.<P>
-<A NAME=filter><H2>Defining a filter</H2>
-Filtering is based on the object name and can be specified in a variety of ways. This
-is the dialog used to specify the filter.<P>
-<IMG SRC=images/browserfilter.png><P>
-The most important part of this dialog is the editor which let you specify the string
-to apply the criteria to. This is not available for <B>No filter</B> setting.
-The different available types and options are.<P>
-<TABLE>
-<TR><TD VALIGN=top><B>
-No filter</B></TD><TD>
-No filter specified, display all objects.</TD></TR>
-<TR><TD VALIGN=top><B>
-Start with</B></TD><TD>
-Only include objects which name starts with the specified string.</TD></TR>
-<TR><TD VALIGN=top><B>
-End with</B></TD><TD>
-Only include objects which name ends with the specified string.</TD></TR>
-<TR><TD VALIGN=top><B>
-Contains</B></TD><TD>
-Only include objects which name contain the specified string.</TD></TR>
-<TR><TD VALIGN=top><B>
-RegExp</B></TD><TD>
-Only include objects which name matches the regular expression specified in the editor. The dialect of RegExp:s
-is the ones in the version of Qt that TOra is compiled against.
-For more information on regular expressions check out
-<A HREF=http://doc.trolltech.com/qregexp.html>http://doc.trolltech.com/qregexp.html</A>, if you are using Qt 3.0
-or later you have a more advanced form of regular expressions.</TD></TR>
-<TR><TD VALIGN=top><B>
-Ignore case</B></TD><TD>
-Ignore the case when matches. Since object names are pretty much always uppercase it is probably safest to leave this on.</TD></TR>
-<TR><TD VALIGN=top><B>
-Invert selection</B></TD><TD>
-If set, include all the objects that does not meet the specified criteria instead of the ones which does.</TD></TR>
-</TABLE><P>
-Some objects you can also search on what tablespace they are located on. This can be specified by the lower
-part of the dialog.<P>
-<TABLE>
-<TR><TD VALIGN=top><B>
-Include all</B></TD><TD>
-Include all regardless of tablespace.</TD></TR>
-<TR><TD VALIGN=top><B>
-Include</B></TD><TD>
-Include the objects located on the selected tablespaces in the list below.</TD></TR>
-<TR><TD VALIGN=top><B>
-Exclude</B></TD><TD>
-Include the objects not located on the selected tablespaces in the list below.</TD></TR>
-</TABLE>
-</BODY>
-</HTML>
\ No newline at end of file
Deleted: trunk/tora/doc/help/charts.html
===================================================================
--- trunk/tora/doc/help/charts.html 2007-01-10 17:14:27 UTC (rev 2092)
+++ trunk/tora/doc/help/charts.html 2007-01-10 17:14:58 UTC (rev 2093)
@@ -1,41 +0,0 @@
-<HTML><HEAD><TITLE>Using charts</TITLE></HEAD><BODY>
-<H1>Using charts</H1>
-There are several different chart types in TOra, you can see them all in the screenshot below.<P>
-<IMG SRC=images/charts.png BORDER=1><P>
-<H2>Piecharts</H2>
-This is the most simple chart. If the chart is too small you can open a snapshot of the chart
-by doubleclicking it. You can also open a context menu by rightclicking it. In the context menu
-you can choose to print the chart as well and open a snapshot in a new window.<P>
-<H2>Linecharts & barcharts</H2>
-These two charts work in the same way. The difference is that in a barchart the values are added
-on top of each other so you can easily see the sum of all values.<P>
-You can zoom a part of a chart by leftclicking it and dragging a selection. If a chart is currently
-zoomed the word <B>Zoom</B> is printed in the upper left corner. You can remove the zooming by right
-clicking on the chart.<P>
-The snapshot feature, context menu and printing works the same for these charts as for the piechart.
-In the context menu you have an additional item though that is <B>Properties</B>.<P>
-<IMG SRC=images/chartsetup.png><P>
-<TABLE>
-<TR><TD VALIGN=top><B>
-Y-Axis</B></TD>
-<TD VALIGN=top>This part is pretty self explanatory and is used to set up the range to display on the Y-axis of the chart.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Show last value</B></TD>
-<TD VALIGN=top>Display the last sample added to the chart under the title of the chart.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Show axis legend</B></TD>
-<TD VALIGN=top>Display text with the range and units of the axises.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Show chart legend</B></TD>
-<TD VALIGN=top>Display the colors used in the chart in a legend to the right.
-</TD></TR>
-<TR><TD VALIGN=top><B>Divide chart in grids
-</B></TD>
-<TD VALIGN=top>How many gridlines to divide a chart into.
-</TD></TR>
-</TABLE>
-</BODY>
-</HTML>
\ No newline at end of file
Deleted: trunk/tora/doc/help/common.html
===================================================================
--- trunk/tora/doc/help/common.html 2007-01-10 17:14:27 UTC (rev 2092)
+++ trunk/tora/doc/help/common.html 2007-01-10 17:14:58 UTC (rev 2093)
@@ -1,58 +0,0 @@
-<HTML><HEAD><TITLE>Other common elements</TITLE></HEAD><BODY>
-<H1>Other common elements</H1>
-These describe other elements that are used in several parts of the user interface.<P>
-<A NAME=sga><H2>SGA Statement</H2>
-This element is used to describe an element in the SGA.<P>
-<IMG SRC=images/sgastatement.png BORDER=1><P>
-The SGA statement have three tabs. The first tab called <B>SQL</B> simply display all of the SQL of the statement.
-The second tab called <B>Execution plan</B> displays the execution plan of the statement. This is described in more
-detail later. The last tab called <B>Information</B> simply display the information available about the statement
-in the SGA.<P>
-<A NAME=explain><H2>Explain plan</H2>
-This element can be either part of an SGA statement or by itself in some cases (See above for a screenshot).
-For more information about execution paths check the Oracle manual Designing and Tuning for Performance,
-chapter 5 in the 8i release.<P>
-A few notes here is that the execution plan displayed here is not necessarily the same as when run depending
-on one of these reasons.<P>
-<UL>
-<LI>It is run as a different user which doesn't access the same database objects as the user you are logged in as now.
-<LI>The session running the query can have changed some optimizer parameters compared to your session.
-</UL><P>
-What you see in this window is the execution you would get if you ran the statement like the one you are logged in
-as now and in your session. One example of this problem is if a user executes SQL which accesses his own objects which
-doesn't have public synonyms, then another person can simply not execute the SQL without modifying it to add owner specifier to
-the tables which TOra will not do automatically.<P>
-Explain plan requires a table to store the result in. The name of this table can be configured in the <A HREF=database.html>options</A>.
-If the table doesn't exist TOra will ask you if it should try to create it. Without this table you can not display execution plans
-in TOra.<P>
-<A NAME=param><H2>Getting bind parameters</H2>
-This dialog is displayed when input parameters are required to run the SQL. For instance the example dialog is the dialog displayed
-when running the following SQL in the worksheet.<P>
-<table width=100% border=0><tr><td bgcolor="#BEEAE0">
-<pre>
-select * from essprc where prcid > :prcid and begrdt > :begrdt;
-</pre></td></tr></table><P>
-<IMG SRC=images/getparam.png><P>
-As you can see the field name as specified after the : character is presented as a title. If the same field name is used at
-several parts of the query you only get to specify it once. You specify the value in the editor line just to the right of the
-field name label. If you want to specify a NULL value check the <B>NULL</B> checkbox to the right of the editor. You can
-also edit the value in a <A HREF=common.html#memo>memo editor</A> pressing the <B>Edit</B> button to the right on the
-value.<P>
-The parameter editor will cache it's value so it will remember the last parameters you fed to it when you run the query again.
-<A NAME=describe><H2>Object description</H2>
-<IMG SRC=images/describe.png BORDER=1><P>
-This is a list that describes the columns of a table or view. There is nothing much special
-about this view except that you can check the collected analyze statistics for the column by
-placing the cursor over it and reading the tooltip that will be displayed. If no tooltip
-is displayed there is no analyzed statistics available. Also notable is that this list is
-read completely from the object cache if it available. This will mean that if you are modifying
-the object you are modifying you need to reread the object cache before you can see the
-changes.<P>
-<A NAME=memo><H2>Memo editor</H2>
-<IMG SRC=images/memo.png><P>
-This is used to display or edit larger text than is easily entered in a oneline editor or list. To the top
-is a toolbar with some editing buttons. Specifically you have the save changes button to the left. You can
-also do this using the key <B>CTRL+Return</B>. You can remove the editor without saving changes using the <B>Escape</B>
-key or closing the window.
-</BODY>
-</HTML>
\ No newline at end of file
Deleted: trunk/tora/doc/help/current.html
===================================================================
--- trunk/tora/doc/help/current.html 2007-01-10 17:14:27 UTC (rev 2092)
+++ trunk/tora/doc/help/current.html 2007-01-10 17:14:58 UTC (rev 2093)
@@ -1,17 +0,0 @@
-<HTML><HEAD><TITLE>Current Session</TITLE></HEAD><BODY>
-<H1>Current Session</H1>
-This tool provides information about the current session.<P>
-<IMG SRC=images/current.png><P>
-The interface for this tool is very simple. There are four tabs in the window. The first one
-present the <B>privileges</B> currently granted to the your session. Roles can be expanded to
-display what privileges are available through those groups.
-The second one present the <B>version</B> of the different components in the connection.
-The <B>parameters</B> tab displays the parameters of the current session. For more information
-of parameter editors see <A HREF=tuning.html#pfile>here</A>.
-The fourth and last tab display the <B>statistics</B> of the session.
-The statistics is shown in two columns, the first one contain the actual value,
-the second show the change in the value since the last update. To update press the <B>refresh</B>
-button in the toolbar. You can also change the connection for the tool using the <b>change
-connection</b> button to the right on the toolbar.
-</BODY>
-</HTML>
\ No newline at end of file
Deleted: trunk/tora/doc/help/database.html
===================================================================
--- trunk/tora/doc/help/database.html 2007-01-10 17:14:27 UTC (rev 2092)
+++ trunk/tora/doc/help/database.html 2007-01-10 17:14:58 UTC (rev 2093)
@@ -1,103 +0,0 @@
-<HTML><HEAD><TITLE>Database Settings</TITLE></HEAD><BODY>
-<H1>Database Settings</H1>
-This page of the options contain settings on how to interact with the database.<P>
-<IMG SRC=images/database.png><P>
-<TABLE>
-<TR><TD VALIGN=top>
-<B>Autocommit changes</B></TD>
-<TD VALIGN=top>If this is set any changes made to the database will be automatically committed
-as soon as you make them. Use this with care, the transaction handling is there for a reason
-you know.
-</TD></TR>
-<TR><TD VALIGN=top>
-<B>Read object cache on connect</B></TD>
-<TD VALIGN=top>If this checkbox is set TOra will start reading the object cache when you start
-a connection to a database. If unchecked it will start reading it when it is first used. Reading
-this is quite a costly query so you probably shouldn't have this checked if you are in a
-production environment, on a slow connection or not using the object cache. The object cache
-is mostly used for describing tables, the PL/SQL debugger and code completion.
-</TD></TR>
-<TR><TD VALIGN=top>
-<B>Initial rows to fetch in query</B></TD>
-<TD VALIGN=top>This setting indicates how many rows to always fetch from a query when executing it.
-Observe that you can always read more from the individual query just by scrolling down. Check
-the <B>All</B> checkbox to always read all available records. Be aware that TOra will interact sluggishly
-or not at all while reading many lines. It will also keep the entire result in memory so checking
-the <B>All</B> box and reading a really large table could bring your machine to it's knees.
-</TD></TR>
-<TR><TD VALIGN=top>
-<B>Initially read in content editor</B></TD>
-<TD VALIGN=top>If set to something other than <B>All</B> a query will be placed only this number
-of rows initially from Oracle when browsing the content. The reason for this is that Oracle will be under high load if
-a content list is started on a large table. When this value is reached the query will be reread
-to fetch the rest of the values so you as a user will not see any difference.
-</TD></TR>
-<TR><TD VALIGN=top>
-<B>Maximum size display</B></TD>
-<TD VALIGN=top>The maximum width a list column will get automatically regardless of how large the content
-is. This is so you can still see the rest of the columns even if one of the first can contain
-very large values. You can always resize the column by hand afterwards.
-</TD></TR>
-<TR><TD VALIGN=top>
-<B>Run UI blocking threads exclusively in main thread.</B></TD>
-<TD VALIGN=top>Let queries normally running in the background use their own connection to the
-database. This is so that when a query that would block the user interface needs to be run the
-main connection is more likely to be free. Background queries include many parts of the database
-browser and all charts.
-</TD></TR>
-<TR><TD VALIGN=top>
-<B>Don't reread data if query is exactly same.</B></TD>
-<TD VALIGN=top>If checked TOra will not refresh a query if it is reexecuted exactly the same two times in a row.
-This is mainly usefull in the schema browser when you have a slow connection and need to switch between
-tabs a lot.
-</TD></TR>
-<TR><TD VALIGN=top>
-<B>Abort long running queries and reexecute in own connection.</B></TD>
-<TD VALIGN=top>If checked TOra will abort any queries running in the main connection of the database
-<B>in the background</B> and reexecute them in their own connection to make you able to continue
-to work in other parts of TOra until the query gives a reply. Only queries that have not given
-any response at all will be aborted and moved.
-</TD></TR>
-<TR><TD>
-<B>Move to own connection after</B></TD>
-<TD VALIGN=top>The number of seconds to wait before moving the query from the main connection (See
-<B>Abort long running queries and reexecute in own connection</B> above for more info).
-</TD></TR>
-</TABLE>
-<A NAME=oracle>
-There may also be pages under this for each individual database provider. Currently onlye Oracle uses
-this feature. That setup looks like this.<P>
-<IMG SRC=images/oracle.png>
-<TABLE>
-<TR><TD VALIGN=top>
-<B>Checkpoint name</B></TD>
-<TD VALIGN=top>This is a checkpoint TOra should use when it is making changes that need to be rolled back.
-One place where this is used is to perform explain plans without filling up the plan table. The
-name doesn't matter, just make sure you don't use this checkpoint name yourself.
-</TD></TR>
-<TR><TD VALIGN=top>
-<B>Default date format</B></TD>
-<TD VALIGN=top>The format that you prefer dates to be displayed. Changing this will require a reconnect to
-the database before it starts to operate. The string should be a standard Oracle date to string
-conversion specification. For more information see the Oracle SQL Reference.
-</TD></TR>
-<TR><TD VALIGN=top>
-<B>Explain plan table</B></TD>
-<TD VALIGN=top>The table to use to temporarily store explained execution plans. Use the <B>Create Table</B>
-button to create the table if you don't have it.
-</TD></TR>
-<TR><TD VALIGN=top>
-<B>Keep plans</B></TD>
-<TD VALIGN=top>If this is check explained plans are left in the explain plan table. The normal
-behaviour is to rollback the explanation after it is initially read to keep the explain plan
-table from filling up with old plans.
-</TD></TR>
-<TR><TD VALIGN=top>
-<B>Max LONG and LOB data length</B></TD>
-<TD VALIGN=top>The amount of data to read from LONG, BLOB or CLOB data fields. If you always want
-all the data to be read check the <B>Unlimited</B> checkbox to the right. LONG datafields can
-not be specified as <B>Unlimited</B>, if this is specified 33000 characters are read by default.
-</TD></TR>
-</TABLE>
-</BODY>
-</HTML>
\ No newline at end of file
Deleted: trunk/tora/doc/help/debugger.html
===================================================================
--- trunk/tora/doc/help/debugger.html 2007-01-10 17:14:27 UTC (rev 2092)
+++ trunk/tora/doc/help/debugger.html 2007-01-10 17:14:58 UTC (rev 2093)
@@ -1,218 +0,0 @@
-
-<HTML><HEAD><TITLE>PL/SQL Debugger</TITLE></HEAD><BODY>
-<H1>PL/SQL Debugger</H1>
-This tool provides you with an advanced editor and debugger for developing PL/SQL objects.<P>
-<IMG SRC=images/debugger.png><P>
-<H2>Elements of the debugger window</H2>
-On the top of the screen is the <A HREF=debugger.html#toolbar>toolbar</A> for the debugger.<P>
-Below that to the left are two panes. The top one <B>Objects</B> contains the available objects
-in the selected schema. The schema is selectable through the <A HREF=debugger.html#toolbar>toolbar</A>.
-Select the code object you want to debug or edit in this list or start a new object before
-starting to edit the code.<P>
-The lower pane <B>Contents</B> contains the structure of the selected object. Here you can
-find declared methods of packages and also variables or even anonymous blocks in your code.
-Selecting a line in this pane will move the cursor to where the element is in your code, for
-instance where a variable or method is declared.<P>
-To the right is a large editor area where you can edit the current object. The editor is
-describe more <A HREF=debugger.html#editor>later</A>.<P>
-The last part of the screen is not always visible and contain information about the
-currently running <A HREF=debugger.html#debugging>debugging</A> session.<P>
-<A NAME=toolbar><H2>Toolbar & menu</H2>
-The toolbar and menu contain pretty much the same commands with a few exceptions.
-<TABLE>
-<TR><TD VALIGN=top><B>
-Refresh object list</B></TD><TD VALIGN=top>
-Update the <B>Object</B> list to the left of the screen. This is first on the toolbar and close
-to the end in the menu. The keyboard shortcut for this is <B>F5</B>.
-Observe that this list is read from the object cache and will not be updated unless you
-reread the object cache as well (Available from the <I>File</I> menu.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Select schema</B></TD><TD VALIGN=top>
-In the toolbar this is a combobox listing the available schemas. Changing the schema will change
-the objects displayed in the <B>Object</B> list. Selecting it in the menu (Close to the end) or
-selecting the <B>ALT+S</B> keyboard shortcut will move the keyboard focus to the toolbar
-combobox.</TD></TR>
-<TR><TD VALIGN=top><B>
-New sheet</B></TD><TD VALIGN=top>
-Start editing a new object.</TD></TR>
-<TR><TD VALIGN=top><B>
-Scan source</B></TD><TD VALIGN=top>
-Update the <B>Contents</B> list to the left on the screen according to the source currently in
-the editor. TOra will try to keep up with this as you write, but new blocks and declarations
-will only show up if you rescan the source. The keyboard shortcut for this is <B>CTRL+F9</B>.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Compile</B></TD><TD VALIGN=top>
-Compile the current editor. This will compile the procedure with the debug option, if you don't
-have the debug options you need to recompile it in order to be able to see watches.
-The keyboard shortcut for this is <B>F9</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Execute</B></TD><TD VALIGN=top>
-Call the method, procedure or function closest to the cursor. It's off course only when you
-edit packages that there are several methods to choose from in the current editor. If you have
-changed the source TOra will ask you if you want to recompile and start over or simply continue
-without recompiling. The keyboard shortcut for this is <B>CTRL+Return</B>.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Stop</B></TD><TD VALIGN=top>
-Halt the currently running execution. The keyboard shortcut for this is <B>F12</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Step into</B></TD><TD VALIGN=top>
-Step into any functions or procedures called on the current line of execution.
- The keyboard shortcut for this is <B>F7</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Step over</B></TD><TD VALIGN=top>
-Step to the next line of the current editor.
- The keyboard shortcut for this is <B>F8</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Return from</B></TD><TD VALIGN=top>
-Continue running until returned from the current function or procedure.
-The keyboard shortcut for this is <B>F6</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Head editor</B></TD><TD VALIGN=top>
-Switch between the head and body editor. For more information see the
-<A HREF=debugger.html#editor>editor</A> section below.
-The keyboard shortcut for this is <B>CTRL+Space</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Debug pane</B></TD><TD VALIGN=top>
-Display or hide the <A HREF=debugger.html#debugging>debugging pane</A> at the bottom of
-the debugging window. The keyboard shortcut for this is <B>F11</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Next error</B></TD><TD VALIGN=top>
-Move the cursor to the next syntax error in the current editor. For more information
-about syntax errors in editors see the <A HREF=debugger.html#editor>editor section</A>.
-The keyboard shortcut for this is <B>CTRL+N</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Previous error</B></TD><TD VALIGN=top>
-Move the cursor to the previous syntax error in the current editor. For more information
-about syntax errors in editors see the <A HREF=debugger.html#editor>editor section</A>.
-The keyboard shortcut for this is <B>CTRL+P</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Toggle breakpoint</B></TD><TD VALIGN=top>
-Add or remove a breakpoint on the current line of the editor. Breakpoints are indicated
-with a small stop sign to the right of the line in the <A HREF=debugger.html#editor>editor</A>.
-The keyboard shortcut for this is <B>CTRL+F5</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Disable breakpoint</B></TD><TD VALIGN=top>
-Will disable or enable a breakpoint on the current editor. A disabled breakpoint will be
-seen is grayed out in the margin of the <A HREF=debugger.html#editor>editor</A> of the line
-it is on. The keyboard shortcut for this is <B>CTRL+F6</B>.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Add watch</B></TD><TD VALIGN=top>
-Add a watched variable. See here for more information about
-<A HREF=debugger.html#watches>watches</A>. The keyboard shortcut for this is <B>F4</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Delete watch</B></TD><TD VALIGN=top>
-Remove a watched variable. The keyboard shortcut for this is <B>CTRL+Del</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Change watch</B></TD><TD VALIGN=top>
-Change the value of a watch. See here for more information about
-<A HREF=debugger.html#watches>watches</A>. The keyboard shortcut for this is <B>CTRL+F4</B>.
-</TD></TR>
-<TR><TD VALIGN=top><B>
-Erase runtime log</B></TD><TD VALIGN=top>
-Remove the content of the runtime log which is in the rightmost pane of the
-<A HREF=debugger.html#debugger>debugger info</A>.</TD></TR>
-</TABLE><P>
-<A NAME=editor><H2>Debugger editor</H2>
-There are a few things that are special to the PL/SQL debugger compared to other editors in
-TOra. First of all there are actually two editors. In one you edit the declaration of a package
-this is called the <B>head</B> editor. The other one is used to edit the implementation of a
-package and is called the <B>body</B> editor. If you are editing procedures or functions you
-will only use the <B>body</B> editor. You switch between the editors using the <B>CTRL+Space</B>
-keyboard shortcut or with the <B>head editor</B> toolbar button or menu entry. This also mean
-that when you run a program and make a change, but still decide to keep stepping through your
-program without restarting you can have one other changed file plus the current file, if you
-try to step to another object TOra will ask if you want to continue until you are back in the
-edited files or recompile.<P>
-Another thing special in this editor is that the PL/SQL editor will show you errors in the
-package. The errors are highlighted with a special background color (The default is red, but
-this is configurable in the <A HREF=fonts.html>options</A>. You can also use the <B>next error</B>
-or <B>previous error</B> toolbar button/menu entries to step between the errors.<P>
-Next thing to know about the debugger is breakpoints. You can set a breakpoint either by
-selecting the <B>toggle breakpoint</B> toolbar button or menu entry. This will add a breakpoint
-to the line you are currently on in the editor. To remove the breakpoint simply select
-<B>toggle breakpoint</B> again. Another way to add or remove breakpoints is to double-click in the
-left margin of the editor where you also see where the breakpoints are. They are indicated by a
-small stop sign in the margin. If you want to temporarily disable a breakpoint that you might
-need to enable again later you can also choose <B>disable breakpoint</B>, this is also a toggle
-so selecting the command again will re-enable the breakpoint. For those of you who don't know
-breakpoints means that when execution of the object comes to the line containing the breakpoint
-the debugger will stop and allow you to inspect the data.<P>
-Which brings us to the last special thing in this editor which is the current line of execution,
-this is an indication of where the execution currently is at. This line is indicated by a
-special background (Default is green, but that is configurable in the
-<A HREF=fonts.html>options</A>).<P>
-<A NAME=debugging><H2>Debugger information</H2>
-Information about the current state of execution is shown in the pane at the bottom of
-the debugger window which you can be hidden. You hide or show this by selecting the command
-<B>debug pane</B> command or by pressing the <B>F11</B> key. The debug pane consist of
-several tabs containing the following information.<P>
-<TABLE>
-<TR><TD VALIGN=top><B>
-Stack trace</B></TD><TD VALIGN=top>
-Contains the current stack trace. This means the list of called objects that have lead to
-the current line of execution. Selecting a line will bring up the object and line where
-the the call to the next object was made except for the last line which is the current
-line of execution.</TD></TR>
-<TR><TD VALIGN=top><B>
-Watches</B></TD><TD VALIGN=top>
-Watches is where you can inspect variables in your PL/SQL code while running. They are
-explained in more detail <A HREF=debugger.html#watches>later</A>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Breakpoints</B></TD><TD VALIGN=top>
-A list of where you current have your breakpoints and their status. The status can be
-<B>enabled</B> or <B>disabled</B> which are pretty self explanatory. It can also be
-<B>deferred</B> which means that some error have occurred setting the breakpoint. Every time
-execution is restarted TOra tries to set any breakpoints that are <B>deferred</B>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Parameters</B></TD><TD VALIGN=top>
-This displays the input and output parameters that you passed to the
-original call that started the debugging. The output parameters are off course not available
-until the execution is finished.</TD></TR>
-<TR><TD VALIGN=top><B>
-Debug output</B></TD><TD VALIGN=top>
-Any DBMS_OUTPUT output from your debugging session will end up in this window. For more
-information about using this see the <A HREF=output.html>output tool</A>.</TD></TR>
-<TR><TD VALIGN=top><B>
-Runtime log</B></TD><TD VALIGN=top>
-This is simply a log displaying what is happening in the target debugging thread and
-probably not of much interest to anybody except TOra developers. One exception is that
-if you somehow get an SQL error when you function or procedure of choice is executed those
-errors will end up here.</TD></TR>
-</TABLE><P>
-<A NAME=watches><H2>Watches</H2>
-Watches are a way to inspect the contents of variables in a running program. When you add
-a watch using the <B>add watch</B> command you are presented with the following dialog.<P>
-<IMG SRC=images/addwatch.png><P>
-First of all you need to select the scope the variable is declared in. The <B>local</B> scope
-is variables only declared in the current context, like for instance this function or procedure.
-The <B>head</B> and <B>body</B> are variables declared in packages. Variables in packages
-are usually also available in the <B>global</B> scope. When you declare a watch in any scope
-except for <B>local</B> you should also indicate the object in which the variable is declared
-in the format <I>schema.object.variable</I>. The current object is prepended to the variable
-name when you select anything but the <B>local</B> scope.<P>
-Finally you have to fill out the variable name. If you have the cursor on a variable in the editor that
-name is the default when you add the watch.<P>
-You can then see the contents of this variable in the <B>watch</B> pane of the
-<A HREF=debugger.html#debugging>debugger info</A>. The value will be updated every time execution stops
-while you are debugging. If the variable can not be found it will be <B>{Unavailable}</B>. If
-all variables are unavailable even though they shouldn't you have probably forgotten to compile
-the object with the debug option. You can remedy this by simply using the <B>compile</B>
-command. TOra will always compile programs using the debug option when in the PL/SQL debugger.<P>
-TOra can also inspect list and table object which will show up as child items in the list to
-the variable. When this is a case you can also see how many items an array is having in the
-parent of the actual data items.<P>
-You can remove a watch by selecting it in the watch list and selecting the <B>remove watch</B>
-command.<P>
-You can also change the content of a watch. First you select the watch you want to change in
-the watch list, then you select the <B>change watch</B> command. You will be shown this
-dialog.<P>
-<IMG SRC=images/changewatch.png><P>
-If you have selected the parent of an array watch you will be able to select the index you
-want to assign a new value with the <B>index</B> indicator to right. Then you enter the new value in
-the text field or check the <B>NULL</B> indicator to set the value to NULL.<P>
-</B...
[truncated message content] |