1. irc client
I finally got the irc client working again!
It's based on tcp4u, is multi-channel, multi-server (and multi-net), but has no
text entry and no gui. It's a dos box. Functions are called for events, rather
mirc-like. Tested on only Sorcery.net, but was connected to dalnet at one
point last year.
At what point should i send it to the archives?
Kat
3. Re: irc client
On 28 May 2002, at 13:59, a.tammer at hetnet.nl wrote:
>
> NOW
Well, i'm sure it's lacking features people want, so at which point is it done
enough, and at which point is it over-engineered? No way will i compete with
mirc, but at least it shows how to connect with tcp4u and sorta-multitask it.
Kat
4. Re: irc client
- Posted by a.tammer at hetnet.nl
May 28, 2002
Let us have it without features and take your time to fill them=
in whenever asked for. PLEASE, Kat
antoine
5. irc client
Preliminary, non-working, can be found at:
http://www.pell.net/warning/Katbot_0.11.zip
Not included is tcp4u, or all the includes in my euphoria\include dir (like
machine.e, strtok.e, etc). When i am closer to done, i'll add them to the zip.
I am now in the middle of adding all the numerics, and then an internal
address list like mirc's ial.
But, those of you who are adventurous can take a peek. The main is irc
client 12.ew. Hidden.e is those things mirc does in the background.
Utilities.e is generic things like msg(), notice(), preparing the serverlist,
etc..
The mirc events are broken out into the other includes, like on_op.e (which
includes on_deop()), etc. I'll write a book on it later. I am one version beyond
this, but i was looking for some feedback for now. Speed wasn't an issue,
but may be later. Expandability, threading, and using more than one server
at one are the issues as i see them, which is why some things are done
wierdly. Before i made a few more changes, mid-version, it did connect, join
a room, say something, and reply to ctcp version requests.
Send me your wish list, critiques, etc......
Kat
