<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html xmlns:fn="http://www.w3.org/2005/02/xpath-functions">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" href="../../../../doc/otp_doc.css" type="text/css">
<title>Erlang -- Toolbar</title>
</head>
<body bgcolor="white" text="#000000" link="#0000ff" vlink="#ff00ff" alink="#ff0000"><div id="container">
<script id="js" type="text/javascript" language="JavaScript" src="../../../../doc/js/flipmenu/flipmenu.js"></script><script id="js2" type="text/javascript" src="../../../../doc/js/erlresolvelinks.js"></script><script language="JavaScript" type="text/javascript">
<!--
function getWinHeight() {
var myHeight = 0;
if( typeof( window.innerHeight ) == 'number' ) {
//Non-IE
myHeight = window.innerHeight;
} else if( document.documentElement && ( document.documentElement.clientWidth ||
document.documentElement.clientHeight ) ) {
//IE 6+ in 'standards compliant mode'
myHeight = document.documentElement.clientHeight;
} else if( document.body && ( document.body.clientWidth || document.body.clientHeight ) ) {
//IE 4 compatible
myHeight = document.body.clientHeight;
}
return myHeight;
}
function setscrollpos() {
var objf=document.getElementById('loadscrollpos');
document.getElementById("leftnav").scrollTop = objf.offsetTop - getWinHeight()/2;
}
function addEvent(obj, evType, fn){
if (obj.addEventListener){
obj.addEventListener(evType, fn, true);
return true;
} else if (obj.attachEvent){
var r = obj.attachEvent("on"+evType, fn);
return r;
} else {
return false;
}
}
addEvent(window, 'load', setscrollpos);
//--></script><div id="leftnav"><div class="innertube">
<img alt="Erlang logo" src="../../../../doc/erlang-logo.png"><br><small><a href="users_guide.html">User's Guide</a><br><a href="index.html">Reference Manual</a><br><a href="release_notes.html">Release Notes</a><br><a href="../pdf/toolbar-1.4.2.2.pdf">PDF</a><br><a href="../../../../doc/index.html">Top</a></small><p><strong>Toolbar</strong><br><strong>User's Guide</strong><br><small>Version 1.4.2.2</small></p>
<br><a href="javascript:openAllFlips()">Expand All</a><br><a href="javascript:closeAllFlips()">Contract All</a><p><small><strong>Chapters</strong></small></p>
<ul class="flipMenu" imagepath="../../../../doc/js/flipmenu"><li id="loadscrollpos" title="Toolbar" expanded="true">Toolbar<ul>
<li><a href="toolbar_chapter.html">
Top of chapter
</a></li>
<li title="Toolbar Window"><a href="toolbar_chapter.html#id61415">Toolbar Window</a></li>
</ul>
</li></ul>
</div></div>
<div id="content">
<div class="innertube">
<h1>1 Toolbar</h1>
<div class="warning">
<div class="label">Warning</div>
<div class="content"><p>
<p>
The Toolbar application is deprecated and will be removed in R16.
</p>
</p></div>
</div>
<p>Toolbar provides an interface to the various Erlang tools which are available. Toolbar can also provide access to user supplied tools which are included with the Erlang software release. These tools are called GS Contributions.</p>
<p>All tools included in Toolbar must have a configuration file which contains information about the tool, such as its start function and the location of help information. The name of a configuration file must include the suffix <span class="code">.tool</span>.
</p>
<p>Start the Toolbar application with one of the following commands:
</p>
<ul>
<li>enter the command <span class="code">toolbar:start().</span> from the command line after Erlang has been started.</li>
<li>start Erlang with the command <span class="code">erl -s toolbar</span>.</li>
</ul>
<p>When started, Toolbar automatically checks for <span class="code">*.tool</span> files in the current path and adds the corresponding tools. For each <span class="code">ebin</span> directory found in the path, it will also look in a <span class="code">priv</span> directory next to it. This is a function of the Erlang file structure.
</p>
<p>You can update Toolbar with menu commands on Toolbar window. Refer to the File Menu and Tools Menu sections below for details.
</p>
<h3><a name="id61415">1.1
Toolbar Window</a></h3>
<p>The following illustration shows <span class="bold_code"><a href="#fig_1">The Toolbar Window</a></span>.
</p>
<a name="fig_1"></a>
<img alt="IMAGE MISSING" src="bar.gif"><br>
<em>Figure
1.1:
The Toolbar Window</em>
<p>Each icon on Toolbar represents a separate tool, which is started by clicking on the icon. You can also display place the mouse pointer over an icon to display the name of the tool at the bottom of Toolbar window.
</p>
<p>The Toolbar window also has a menu which includes the following menu items:
</p>
<ul>
<li>File menu</li>
<li>Tools menu</li>
<li>Help menu</li>
</ul>
<p>These menu are described in the following sections.
</p>
<h4>The File menu</h4>
<a name="file_menu"></a>
<p>The File menu has the following two menu items:
</p>
<dl>
<dt><strong>Update Toolbar</strong></dt>
<dd>Select this menu item to search for new tool files in the current path and add the corresponding tools to the Toolbar window. This action is performed automatically every the Toolbar application is started.</dd>
<dt><strong>Quit</strong></dt>
<dd>Select this menu item to exit the oolbar application.</dd>
</dl>
<h4>The Tools menu</h4>
<a name="tools_menu"></a>
<p>The Tool menu has the following menu items:
</p>
<dl>
<dt><strong>Create Tool File</strong></dt>
<dd>Choose this menu item to display the Create Tools File Window, where you create a new tools file, or edit an existing tools file. This window is described in detail below.</dd>
<dt><strong>Add GS Contributions</strong></dt>
<dd>Choose this menu item to add GS contributions by entering the path to the directory where these tools are situated. GS contributions are user supplied tools which are included with the Erlang software release. These tools are not supported by Erlang/OTP.</dd>
</dl>
<h4>The Create Tool File Window</h4>
<p>This window is displayed when you select <strong>Create Tool File</strong> from the <strong>Tools</strong> menu. The following illustration shows <span class="bold_code"><a href="#fig_2">The Create Tool File Window</a></span>.
</p>
<a name="fig_2"></a>
<img alt="IMAGE MISSING" src="create_tool.gif"><br>
<em>Figure
1.2:
The Create Tool File Window</em>
<p>Follow these steps to create a new tool file, or to edit an existing tool file:</p>
<ul>
<li>To edit an existing tools file, enter the file name of the tools file into the field <strong>File name</strong> and press <strong>Enter</strong>. The contents of the tool file are displayed in the information fields. Edit the information in the following fields as required.</li>
<li>To create a new tools file, enter information into the following fields.</li>
<li>When finished, select <strong>Update Toolbar</strong> from the <strong>File</strong> menu.</li>
</ul>
<ul>
<li>
<strong>File name</strong>. Enter the name of the tools file. The application will add the <span class="code">.tool</span> suffix if omitted.</li>
<li>
<strong>Tool name</strong>. Enter the name of the tool. This field defaults to the name entered into the File name field. For example, if you enter <span class="code">mytool.tool</span> as a file name, this field defaults to <span class="code">mytool</span>.</li>
<li>
<strong>Start function</strong>. Enter a module name and a function name into the fields titled module and function respectively. The function must exist and take zero arguments.</li>
<li>
<strong>Icon file</strong>. Enter the file name of the icon to be displayed in the Toolbar. The file must be a bitmap file or a GIF image with the file extension <span class="code">.xbm</span> or <span class="code">.gif</span> respectively. If no path name is entered, the system assumes that the file is located in the same directory as the tools file. This field is optional.</li>
<li>
<strong>Message</strong>. Enter a descriptive string of maximum 30 characters for the tool. This field is optional. The information entered here is displayed at the bottom of the Toolbar window when the mouse pointer is placed on the Toolbar icon.</li>
<li>
<strong>HTML</strong>. Enter an URL, a HTML file name, or a plain text file name, which points to the help text file for the tool. An URL should be given in the form <span class="code">http://...</span>. If no path is given, the system assumes that the file is located in the same directory as the tool file. For an HTML file name ending with <span class="code">.html</span>, it is possible to add an index which points to a specific location in the file. This is written as <span class="code">.html#index</span>. This field is optional.</li>
</ul>
<p>The window has the following command buttons:
</p>
<ul>
<li>
<strong>Clear</strong>. Click on this button to clear the information fields.</li>
<li>
<strong>Save</strong>. Click on this button to save the information. A new tool file can be saved only when mandatory information such as file name, tool name and start function has been entered.</li>
<li>
<strong>Stop</strong>. Click on this button to quit the Create Tool File window.</li>
</ul>
<div class="note">
<div class="label">Note</div>
<div class="content"><p>
<p>No error check is performed on the information entered.</p>
<p>You must select <strong>Update Toolbar</strong> from the <strong>File</strong> menu to update the configuration and make the tool visible on the Toolbar.</p>
</p></div>
</div>
<h4>The Help menu</h4>
<a name="help_menu"></a>
<p>The Help Menu has the following two menu items, plus additional help menu items for those tools which have a help system.
</p>
<dl>
<dt><strong>About</strong></dt>
<dd>This menu item displays a short message about accessing the help information.</dd>
<dt><strong>Toolbar</strong></dt>
<dd>This menu item provides access to the Toolbar documentation.</dd>
</dl>
</div>
<div class="footer">
<hr>
<p>Copyright © 1997-2012 Ericsson AB. All Rights Reserved.</p>
</div>
</div>
</div></body>
</html>
distrib
>
Fedora
>
17
>
i386
>
media
>
updates
>
by-pkgid
>
675c8c8167236dfcf8d66da674f931e8
>
files
>
1499
