\input texinfo
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Installation is fairly simply. Simply put the archive contents somewhere
on your harddisk. Note that you need MUI 2.3 or better!
Before you can use CLChatGUI, you must connect to a chat server
running ‘CLChatD’.
When started, CLChatGUI will prompt you for a server name and a port
number to connect to.
If you are connected to a LAN, you should ask your network adminstrator for both server name and port number.
If you are connected to the Internet, you may try pluribus.wupper.de
at port 5555, but be warned that the Internet link of this machine is
temporary and generally down. See ARCnet for a good choice of
servers to connect to.
You must also specify a Nickname and your Realname. The
nickname is a kind of username used within the chat system. It may be up
to 15 byte long and must consist of letters, digits and the characters
. and _. The realname is used for informational
purposes only.
Note that the server may reject your connection attempt because the entered nickname is invalid or already in use by another chat user. Change your nick and retry the connection.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If you start the client on a machine running the CLChatServer,
it will not connect using AmiTCP, but directly link to the chat server to
reduce overhead.
If you want to avoid this behaviour, e.g. for testing purposes, start ‘CLChatGUI’ with the TCPMode keyword or specify the TCPMode tooltype.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
After connecting to the chat server, the main window opens. It consists of a channel selection gadget, a topic gadget, the main output window, your input string gadget and the user operation gadget group. It also features a menu bar with several options and shortcuts for server commands.
You send text to the chat server by simply entering it in the input gadget. Commands are also send to the server by entering them in the input gadget. You may want to use the /HELP command to learn about available server commands. The input gadget is normally automatically activated; if it is not, simply press SPACE to activate it. A history of the last 100 lines entered is kept; you may use Cursor/UP or Cursor/DOWN for accessing entries in the history.
Changing channels is done by entering a new channel name in the channel selection gadget. Note that the server will automatically create a channel if it does not exist. Already existing channels may be selected with the popup listview right of the channel gadget. The popup button has a hidden keyboard shortcut h which opens the channel selection listview.
If you have channel operator status, you may change the current channel’s topic by entering a new one in the topic gadget. The contents of this gadget are automatically updated if someone else changes the topic.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The user listview displays all users currently logged into the chat server
and the name of the channel they are currently on. Users with channel
operator privilege are marked with a @, users with chat operator
privilege are marked with a ! before the name.
Double clicking on an entry in the user listview requests a /WHOIS
user command from the server. Pressing the Dialog button opens a
special so-called dialog window. A dialog window works much like the main
windows, but every text entered within a dialog window is send directly as
a private message to the user. Also, any incoming private messages from
this user are displayed in the dialog window and not the main window. If
the Auto checkbox is selected, a new dialog window is created for
the originator of every incoming private message.
If you have channel or chat operator privilege, you may also use the
OP, DEOP and KICK buttons to perform the requested
operation on the selected user.
Via the PING button you can request a PING request from the
selected user. If the user is running the GUI client, too, you
will eventually receive a reply stating the round-tripe time
from you to the remote user. This is usefull for TCP connections only.
If you have a TCP connection, you may also use the Send Files
option to directly send files to the remote user; see FileTransfer
for more information about this operation.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
In the setup window, you may modify several operation attributes.
Autoconnect will cause an automatic connection attempt each time the
‘CLChatGUI’ is started.
Max. Number of Lines specifies how many lines of incoming text will
be stored for the output listview.
File Receive Path specifies the path you want incoming CLFT
files to go (See section FileTransfer.).
The Event Handling checkboxes set the reaction of special events.
You may set Deiconify to automatically deiconify the application on
the given event, and DisplayBeep to just have the screen beep.
You may create several different configuration files using the
Save... and Load... items from the menu bar. If you create
icons for the configurations, you can start ‘CLChatGUI’ by simply
doubly clicking on the configuration icon.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If you connect via AmiTCP, you may also use the CLFT protocol to directly send files to users linked to the chat network (comparable to the IRC DCC protocol). Simply select the user you want to send to, press the Send files button and a filerequester will open. You can also directly drop Workbench icons onto the user listview to have the correspondending files to be send to the currently selected user.
When you have selected files, a CLFT request will be send to the
remote user, and the CLFT sender window will open on your side,
awaiting a connect from the receiving site. The receiver will then
eventually connect to you via TCP and grab the files offered to him.
If you receive incoming CLFT requests, a requester will open showing
you the originator of the request, the number of files to be send and a
list of the files to be transfered. You may accept or reject the request,
or you may change to destination directory. Use the Setup window to
change the default path in which incoming files are stored. Incoming files
are tagged with a filenote designating the originator nick and IP address
for later identification. If an equally named file already exists, the
file name is postpended with ".2", ".3" etc.
You may abort file transfers at any time by clicking on the close gadget of
the receive or send window. All transfers currently waiting or in progress
will automatically terminate if you quite CLChatGUI. Note that you
cannot send files to users which are connected via TelNet or the
Connectline ANSI client.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
‘CLChatGUI’ features an ARexx port. The port name is
CLCHATCLIENT.nr, with nr starting at 1 and increasing for
every instance of the program started.
Besides the builtin MUI commands (see the MUI User Guide), ‘CLChatGUI’ current features two commands:
SEND TEXT/FSends the given text string as it was entered in the input string gadget. Note that you may also send server commands this way.
RECONNECTCause the ‘CLChatGUI’ to reconnect to the current server.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Below is a list of normally available server commands. Don’t forget to use the /HELP command to learn if your server supports a different command set.
Operator only commands:
There are also special Chat operator commands which are not visible to the normal user or channel operator. Use the /HELP command to obtain a list of chat operator commands directly from the server.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
ARCnet, the Amiga Relay Chat Network, is a Internet based
network of CLChatServers available for public usage. As the time of
writing, the following servers were connected to the network:
All servers run the CLChatServer on port 5555. Note that some of
these servers are not available for 24h/day.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The CLChatSystem (‘CLChatServer’, ‘CLChatD’ ,
‘CLChatLink’ and ‘CLChatGUI’) is (C) 1994-1995 Oliver Wagner, All
Rights Reserved.
The package may be distributed freely as long as all files are distributed as a whole archive and are not modified in any way.
‘CLChatGUI’ is a MUI application. MUI is (C) 1993-95 Stefan Stuntz.
‘AmiTCP’ is (C) 1994-1995 NSDI Inc.
Please send bug-reports, suggestions and comments via E-Mail to
o.wagner@pluribus.wupper.de.
Updates are placed on AmiNet; they can also be downloaded via
anonymous FTP directly from pluribus.wupper.de. You can also check
out anonymous FTP at the servers listed in the ARCnet reference
if they have a better link to your host.
| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Version 1.7Version 2.0Version 2.1Auto Reconnect to automatically
attempt to reconnect if the server connections breaks down.
Version 2.2 (internal)Version 2.3Version 2.4| [ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
| Jump to: | A C F H L S U |
|---|
| Jump to: | A C F H L S U |
|---|
| [Top] | [Contents] | [Index] | [ ? ] |
| [Top] | [Contents] | [Index] | [ ? ] |
This document was generated on July 22, 2024 using texi2html 5.0.
The buttons in the navigation panels have the following meaning:
| Button | Name | Go to | From 1.2.3 go to |
|---|---|---|---|
| [ << ] | FastBack | Beginning of this chapter or previous chapter | 1 |
| [ < ] | Back | Previous section in reading order | 1.2.2 |
| [ Up ] | Up | Up section | 1.2 |
| [ > ] | Forward | Next section in reading order | 1.2.4 |
| [ >> ] | FastForward | Next chapter | 2 |
| [Top] | Top | Cover (top) of document | |
| [Contents] | Contents | Table of contents | |
| [Index] | Index | Index | |
| [ ? ] | About | About (help) |
where the Example assumes that the current position is at Subsubsection One-Two-Three of a document of the following structure:
This document was generated on July 22, 2024 using texi2html 5.0.