On Friday, March 7, 2003, at 04:00 AM, Jason Townsend wrote:
> On Wednesday, March 5, 2003, at 08:40 PM, Matthew Stuckwisch wrote:
>> Seems that #fire has come in handy once again. I've made a few=20
>> comments in here. I'll send him an e-mail tomorrow night unless=20
>> someone else would like to (looks at Jason)
>>> From: Dan Christiansen <danchr@...>
>>> Date: mi=E9r. marz 5, 2003 14:36:09 US/Central
>>> To: guifa@...
>>> Subject: Fire development
>>> I just dropped by #fire on EsperNet to see your email there. I just=20=
>>> might end up contributing to Fire :)
>> Note here, Fire's connection got dropped, that's why I wasn't=20
>> actually there.
>>> There are really two things I'd like to do:
>>> 1) Fix that !/&%!=80"/& connection issue, for good and The Right Way =
> I'd like to go into more detail on what the issue is, and what your=20
> solution is. Hopefully this is complementary to something I'm working=20=
> on to improve the error reporting mechanism. I'm adding an=20
> AlertController class, which will provide an abstraction between the=20=
> errors and how they are displayed to the user. This will get us=20
> nonblocking alerts (including ones that ask questions), suppressing=20
> duplicate alerts, dumping alerts to the console, etc.
I once saw a dialog in Quicktime which allowed you to show many alerts=20=
in one window; seemed very nice to me. At least that would solve the=20
"window leak" ;) It should be fairly easy to implement it once there is=20=
>>> 2) Improve or rewrite the IRC client to make it replace my current=20=
>>> IRC client, Snak
>>> Suddenly, it dawned on me; I want to write an IRC client - Fire's=20
>>> IRC client sucks - combine those two, and - oooooh...
>> and....ooooh....ooooh, IRC programmer, we could use that ^_^
> Yes, I would love to have an IRC afficionado take a look at improving=20=
> Fire in that area. I'm the stand in for maintaining it, but haven't=20
> really done much.
I'm currently trying to figure out how it should be done. It would be=20
an interesting exercise
to do it in Objective-C, but without any dependencies on Mac OS X- and=20=
OpenStep-specific parts, i.e. only using POSIX and ANSI C calls. Also,=20=
once doing it, I believe it would be better to isolate the entire IRC=20
client in a library, so that other people could make an IRC client=20
easily using my implementation of IRC.
The way I see it, it should be possible to implement instant messaging=20=
via IRC. It has support for most features Fire has - different codings=20=
is an exception.
I have been using Fire for quite some time, and I would like to=20
contribute to your project.