On Mon, Jun 11, 2001 at 10:14:58PM +0100, Chris Ball wrote:
> It's a good idea. You could write an IM client (which would be foolish,
> IMO - you'd be writing something adhering to a huge protocol specific to
> a desktop environment with (at the moment) a handful of users) or take
> advantage of some the features of some existing clients that lets
> external applications get status from them and write a wrapper. It's
> much like the xmmsctrl situation, I guess.
Totally. An IM client needs to be able to pop up windows, so it'd be in
GTK.
If I wrote an actual IM system for further, really, it'd be like this:
- backend system which speaks icq, aim, etc and translates to a unified
format, and communicates these messages via a pipe
- gtk program which reads this pipe and shows windows
- further plugin which either reads pipe or communicates with gtk app
The separation of the first two allows you to have different UIs for
it... a console client could use the same system, for example.
Sorta like Jabber, except that Jabber seems to be a lot more
heavyweight. Actually, maybe Jabber could work... *adds to mental list*
> Either way. Um. Evan, as an idea perhaps you could work on a generalised
> interface to handling IM information like the time of last page, number
> of users on-line, and a way of alerting of new messages. I'd be happy to
> take on writing an ICQ agent for the new interface (perhaps with Ed?), if
> you wanted to play with an AIM one. Or something. Anyway. Just an idea. :)
I'll look in to it. :)
-- Evan Martin - martine@speakeasy.org http://www.speakeasy.org/~martine_______________________________________________ Further-devel mailing list Further-devel@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/further-devel
This archive was generated by hypermail 2.1.2 : Sun Nov 11 2001 - 14:16:15 PST