You can modify the operational variables and the look and feel of the Chat Blazer client interface easily by editing the Chat Blazer Java applet parameter tags i.e. <param>. The list of the parameters are included in the file cbclient.htm. Certain parameters might be missing from your cbclient.htm due to the different versions of Chat Blazer.
You can use any text editing software to modify the cbclient.htm or cbadmin.htm files. E.g. Windows "NotePad" or UNIX "vi" or "pico".
A brief description of the entire list of parameters (in alphabetical order) and what they can do is described below:
| Parameter Name | Value | Description |
| allow_ignore | "yes" or "no" | Determines whether users can ignore
other users. |
| allow_rooms | "yes" or "no" | Determines whether users can change
rooms after logging in. |
| allow_whisper | "yes" or "no" | Determines whether users can whisper
to other users. |
| banner_text | Your Text | Text to appear in the banner caption
under the banners in the chat interface. Use "" to remove this from the
chat interface. Use an empty text (" ") to just have the banner caption
without any text in it. |
| banner_text_bg | Hex color code, 000000 - FFFFFF | Background color of the banner caption. |
| banner_text_fg | Hex color code, 000000 - FFFFFF | Foreground color of the banner caption. |
| bannerfile1/2/3/4/5/...25 | Image filename, JPEG and GIF only. | List of the filenames of banners
that will be rotated in the chat interface, up to a maximum of 25. |
| bannerinterval | Number | Number of seconds to show a banner
before changing to the next one. |
| bannerlink1/2/3/4/5/...25 | URL, e.g. HTTP, FTP links, etc. | List of the URLs to be opened when
the corresponding banner in the chat interface is clicked. For example,
"bannerlink1"
is the URL for "bannerfile1". |
| bg | Hex color code, 000000 - FFFFFF | Background color of the chat interface. |
| bbg | Hex color code, 000000 - FFFFFF | Background color of buttons, excluding
the toolbar. |
| close_redirect | URL | The URL where the user will be redirected
to when he closes the applet. |
| fg | Hex color code, 000000 - FFFFFF | Foreground color of the chat interface. |
| fontface | Name of font | Name of font to be used in the chat
interface. Possible fonts include "Courier", "System", "Arial", etc. |
| fontsize | Number | Size of font in the chat interface. |
| help_redirect | URL | Redirects the user to another help
file contained in the URL when the Help button is clicked. Leave it blank
to use the default help URL provided (clienthelp.htm). |
| hide_help_button | "yes" or "no" | Determines whether to display the
Help button. |
| hide_audio | "yes" or "no" | Determines whether to hide the audio
messages list box. If hidden, users cannot send audio messages. |
| hide_emoticon | "yes" or "no" | Determines whether to hide the emoticon
messages list box. If hidden, users cannot send emoticon messages. |
| hide_moderator | "yes" or "no" | Hides the moderator button. Users
can still be in a moderated room but can never become a moderator. You can
use this to prevent your users from trying to become a moderator. Applicable
only if you have the moderator plug-in. |
| import_add | "yes" or "no" | Determines if the default sound set
is added on to any imported sound set. |
| import_sound | filename;description | List of imported sound files. Every
sound filename must be succeeded by its description, seperated by a semi-colon(";").
For example, a valid sound set is "hello.au;Hello!;hi.au;Hi there!;yahoo.au;Yahoo" |
| lock_interface | "yes" or "no" | Determines whether the user can switch
between a floated or embedded chat interface. |
| login_button | "0" or "1" | If "1", the login button will be
an image button. If "0", the button will be a standard button. |
| login_floated | "yes" or "no" | Determines whether the login window
is embedded ("no") into the webpage or shown as a seperate applet window. |
| login_image | Image filename, JPEG or GIF | Filename of the image to be used
for the login button. You can leave this field blank if you have put "0"
for login_button |
| loginbanner | Image filename, JPEG or GIF | Filename of the image to be displayed
at the login window. You can leave this field blank if you want to remove
the login banner. |
| login_method | "normal" or "direct" | Determines whether the login procedure
uses the login window ("normal") or goes straight to the chat interface
("direct"). The direct-login mechanism requires additional arguments to
be provided, namely login_name and login_room. |
| login_name | User name | This field needs to be filled if
your are using the direct-login mechanism, i.e. the value of login_method
is "direct". It is recommended that you derive the login_name
value from your database. Chat Blazer does not allow duplication of user
names even though the different users may be in different rooms. |
| login_room | Existing room name | The room which the direct-login user
will first enter. This field needs to be filled if the value of login_method
is "direct". The room must already be available in the chat network. |
| login_sound | Sound filename, .AU only | Sound file to be played when a person
enters a room. |
| logout_sound | Sound filename, .AU only | Sound file to be played when a person
leaves a room or logs out. |
| maximumidletime | Number | Number of seconds of inactivity before
the chat applet logs the user out. |
| mode | "0" or "1" | Determines the total look of the
chat interface. "0" enables normal mode which is the full-featured chat
interface. "1" enables minimal mode, which hides a lot of features and leaves
the chat interface to the bare minimum. |
| moderator | "yes" or "no" | Toggles the moderator plug-in. Applicable
only if you have the moderator plug-in. |
| port | Any number from 0 to 65535 | States the port number for the chat
client to connect to the chat server. This number must be the same as the
port number on which you have started your chat server, or else the client
applet cannot communicate with the chat server. Be advised that you should
not use a well-known port number, that is any number from 0 to 1024. |
| private_chat | "yes" or "no" | Determines whether users can engage
in private one-to-one chatting. |
| re-entry | "yes" or "no" | Determines if a user can login again
after logging out. Applies only to direct-login users. |
| show_button_text | "yes" or "no" | Determines if button text should
be displayed on the toolbar. |
| show_users | "yes" or "no" | Determines if the Users List is displayed
in the chat interface. |
| skip_login_button | "yes" or "no" | If "yes", the chat client will automatically
start in the login window. The user will not have to click on the login
button before being brought to the login window. If "no", the login button
appears as usual. This is useful for the implementation of a customer support
help button. |
| start_chat_floated | "yes" or "no" | If "yes", the chat interface starts
in a separate applet window. If "no", it starts embedded in the webpage.
|
| start_button_label | Your Text | You can configure the text in the
standard login button here. This is only applicable if the value of login_button
is "0". |
| text_color_set | "black", "white", "blue", "cyan",
"gray", "green", "magenta", "orange", "pink", "red", "yellow" |
The set of colors to be used in the
chat interface. Four colors have to be specified, the text background, the
color of system messages, your own messages and others' messages. For example,
"white,red,blue,green" will give a white text background, with red system
messages, blue for the user's messages and green for other users' messages.
Leave it blank to use the default set. |
| title | Your Text | The title of the applet window. |
| welcome_message | Your Text | This welcome message will be displayed
each time the user logs into the chat system. |