This tool provides you with an advanced editor for developing PL/SQL objects.
On the top of the screen is the toolbar for the editor.
Below that are two panes. The left one "Objects" contains the available objects in the selected schema. The schema is selectable through the toolbar. Select the code object you want to edit in this list or start a new object before starting to edit the code.
The right pane contains more widgets: Contents, Message Log, and the editor itself. In the Contents list 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.
The Message Log contains all errors and optional warnings for given PL/SQL code. Clicking the log items will take you to the exact place in the editor.
The toolbar and menu contain pretty much the same commands with a few exceptions.
Running static check will create a temporary file containing currently open code tab. Then external program will be called with name of temporary file (with full path) given as parameter. Result from that external program should be in specific format in order to be interpreted by TOra.
TOra expects one line of output (written to stdout) to contain one message from static checker. This line should start with number of line followed by semicolon and then text of message.
Note: in future TOra should be able to interpret linenumber, code of static message and then message itself. Code of static message will be used to open automatically generated URL descibing static checker message.
Example of output from static checker:
72:STC-0100:Comment describing function/procedure and it's parameters is missing 107:STC-0200:Name of procedure "my_procedure" does not comply with naming standard