<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<link rel="stylesheet" href="style.css"/>
<title>What is IMCom</title>
</head>
<body>
<table width="100%" cellpadding="15">
<tr>
<td>
<div class="intro">
<h1>
What is IMCom
</h1>
<p class="intro">IMCom is a command-line Jabber client
written in Python.<br/> Its original goal was to replace
mICQ as my instant messenger. To that end it looks very
similar to mICQ, though the actual command interpreter
is a bit different. Commands are issued to IMCom in a
style similar to IRC.
</p>
</div>
</td>
<td class="navigation" rowspan="12">
<div>
<p class="intro"><strong class="heading">Navigation</strong>:<br/><br/>
<a href="../index.html">Home</a><br/>
<a href="news.html">IMCom News</a><br/>
<a href="whatis.html">What is IMCom</a><br/>
<a href="download.html">Download</a><br/>
<a href="commands.html">Commands</a><br/>
<a href="advanced.html">Advanced</a><br/>
<a href="CHANGELOG">ChangeLog</a><br/>
<a href="imcomrc.html">Example Config</a><br/>
<br/>
<a href="http://www.jabber.org/"><img src="jabberbutton.png" alt="Jabber Open IM"/></a>
</p>
</div>
</td>
</tr>
<tr>
<td>
<div>
<h2>What does IMCom support?</h2>
<p class="noi">IMCom supports the following Jabber technologies:</p>
<ul>
<li>Sending/Receiving Messages</li>
<li>Presence Updates</li>
<li>File Transfer</li>
<li>SSL Connections</li>
<li>vCard retrieval and submission</li>
<li>Basic Support of the jabber:iq:admin namespace</li>
<li>Agent and Transport Registration</li>
<li>Handles Jabber Resources properly</li>
<li>Jabber Group Chat</li>
<li>Jabber Multi-User-Chat (JEP0045)</li>
<li>Jabber:x:data (JEP0004) (Only partial support, submit only, not retrieve)</li>
</ul>
<p class="noi">IMCom supports the following UI stuffs:</p>
<ul>
<li>Command customization</li>
<li>Multi-line messages</li>
<li>Sending a message to a particular resource a user is logged in from</li>
<li>ignore and lurker group support</li>
<li>Auto-Status</li>
<li>Reply/Again (sending a message to the last person to message you and sending a message to the last person you messaged</li>
<li>Color customization</li>
<li>Command Customization</li>
<li>Multiple profile support</li>
<li>Generic module support</li>
</ul>
</div>
</td>
</tr>
<tr>
<td>
<div>
<h2>What does IMCom require?</h2>
<p>
IMCom first and foremost requires a python interpreter
which can be obtained at <a
href="http://www.python.org">www.python.org</a>. I have
tested with Linux C Python 2.2. IMCom will function with
Python 2.1, but the new module support will be disabled.
IMCom uses Python's metaclass enhancements that were
introduced in 2.2 for handling modules.
</p>
<br/>
<p>
IMCom requires the pyexpat or expat module for
python. Note that while the windows binary distribution
of python includes the expat parser the linux source by
default doesn't build in support for expat. You have to
edit the Setup file in the Modules subdirectory of the
source tree and specify where the expat library and
includes are kept. For more information about building
python with expat support read the python README and the
Modules/Setup.in file from the python source tree.
</p>
<br/>
<p>
The expat library itself can be found here:<a
href="http://www.jclark.com/xml/expat.html">http://www.jclark.com/xml/expat.html</a>
</p>
<br/>
<p>
It is highly recommended, but not required, to have the
readline module for python installed as well. Readline
needs to be explicitly compiled in under unix. Windows
does not ship with readline, but supposedly there is a
working implementation here: <a
href="http://newcenturycomputers.net/projects/readline.html">http://newcenturycomputers.net/projects/readline.html</a>
</p>
<br/>
<p>
If you're <b>lazy</b> you can go to <a
href="http://www.activestate.com">ActiveState</a> and
get ActivePython which includes everything you need.
</p>
</div>
</td>
</tr>
<tr>
<td>
<div>
<h2>Where can I get IMCom?</h2>
<p class="noi">
<a href="http://imcom.floobin.cx">http://imcom.floobin.cx</a> Documentation<br/>
<a href="http://nafai.dyndns.org/~crabbkw/files/imcom-betas/">http://nafai.dyndns.org/~crabbkw/files/imcom-betas/</a> Beta Builds.
<br/>
<a href="http://imcom.floobin.cx/files">http://imcom.floobin.cx</a>Source tar balls for official versions.
<br/>
<a href="http://nafai.dyndns.org/~crabbkw/imcom-src/">http://nafai.dyndns.org/~crabbkw/imcom-src/</a> Bleeding Edge Source
<br/>
</p>
</div>
</td>
</tr>
<tr>
<td>
<div>
<h2>Who Maintains IMCom</h2>
<p>
Casey Crabb (<a
href="mailto:crabbkw@nafai.dyndns.org">crabbkw@nafai.dyndns.org</a>)
maintains IMCom and enthusiastically accepts bug
reports, especially if they are reproducible. Feature
requests are also taken into consideration and
potentially added to the list of things to do.
</p>
</div>
</td>
</tr>
</table>
</body>
</html>
