Configuring Plugins We use a pugin scheme to allow easy addition of software modules to the framework. These plugins may either be used to work on the data streams ([Plugin Telnet]), display additional information ([Plugin Status]) to the user or be bywork ([Plugin URLFilter]). Standard plugins are provided with the package. These plugins are desribed here. __How the plugins work:__ It is __important__ that you understand how the plugins work to configure them correctly. You cannot simply put the plugins in the configuration file in any order; __order is important__. Imagine the data flowing through the plugins from __left to right__ (from remote computer to user). {code}__CORRECT:__ plugins=Socket,Telnet,Terminal,Status{code} {code}__WRONG: __(Telnet must be between Socket and Terminal) plugins=~~Telnet~~,Socket,Terminal,Status{code} ~~All plugins that work with the data stream (like [Plugin Script]) must be between [Plugin Socket] and [Plugin Terminal].~~ ---- __standard plugins:__ {table} Plugin | Comments __[Plugin Socket]__ | A most basic plugin used for low level communication with remote hosts. It almost always needed. __[Plugin Telnet]__ | This is the actual handler for telnet type communications. It filters the data streams and handles all telnet options. __[Plugin SSH]__ | For more secure communication you would rather use SSH instead of the Telnet plugin as it provides a way for secure communication over insecure networks. __[Plugin Terminal]__ | This is a very important plugin as it is the actual terminal so you can see what you do. It implements an [ANSI]/[VT320] compatible terminal emulation. __[Plugin Shell]__ | A shell plugin for use with local command shells. Not really useful right now. {table} __add-on plugins:__ {table} Plugin | Comments __[Plugin Status]__ | An example how to write a listener plugin and display information. __[Plugin Timeout]__ | A useful plugin for Applet users. It will allow you to define an idle timeout to close the connection. __[Plugin ButtonBar]__ | The new implemenation of our well known button bar module. With new configuration options and better look than ever. __[Plugin Script]__ | The script plugin may be used to automate login procedures for guest accounts. __[Plugin Sink]__ | The Sink plugin is a replacement of the Terminal plugin, which just reads and discard data. Useful if you do not want output. __[Plugin URLFilter]__ | Filters URLs out of the incoming data and displays a list to open them in a web browser (Applet) __[Plugin MudConnector]__ | A special plugin for www.mudconnector.com to display a list of muds to connect to. __[Plugin BSX]__ | A third party plugin for use with BSX enabled MUDs. It is contained in the contributed package (see [download]). {table} ---- __More than one plugin with the same name:__ To accomplish that we have introduced identifier for the plugins. A normal plugin list would look like: {code}plugins = Socket,Telnet,ButtonBar,Terminal{code} If you wanted to set up another button bar you are in trouble because it would read the same options twice. So when setting up two plugins of the same name you do as follows: {code}plugins = Socket,Telnet,ButtonBar(one),ButtonBar(two),Terminal{code} You give both plugins a unique name (one and two) and use this name in any following configuration properties: {code} layout.ButtonBar(one) = North layout.ButtonBar(two) = South ButtonBar(one).setup = http://server/one.conf ButtonBar(two).setup = http://server/two.conf {code} And that is it! If you define properties without the unique name they will be used as fallback values in case a needed property is not set for a specific plugin. Have a look at the [applet.conf]. 2005-11-10 14:23:52.731 2005-11-10 14:23:52.731