[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Status of kdenetwork module
From:       "Robert D. Williams" <rwilliams () jrc-utah ! com>
Date:       2000-05-17 17:24:38
[Download RAW message or body]

On Wed, 17 May 2000, Michael Reiher wrote:
> Matthias Kalle Dalheimer wrote:
> > I would suggest that Carsten tries to fix ksirc (hopefully) with your
> > input, and we continue to offer kvirc from our FTP server. If Carsten
> > does not manage to freshen up ksirc in time, I'd rather go with no IRC
> > client in the base distribution than an not-maintainable one - we don't
> > have an ICQ client either...
>
> Which is a pitty, btw. Because ICQ is a widely used service. Kdenetwork
> should cover most common services. So IMO it would be good if we could
> find an ICQ client for inclusion into the base distribution.
> KXicq for instance. My favourite client;) Itīs pretty feature rich and
> widely configurable. And, as far as I can judge that, in a pretty good
> shape and actively maintained.  The only technical drawback from my
> point of view is that itīs not yet ported over to the 2.0 API. But this
> point probably applies to most apps that are not(yet) part of CVS. And
> of course the author would need to want that.
> This is of course only my opinion as a user of KXicq. The author might
> have a different one;)
>
> Btw: I think we should also have an AIM client in kdenetwork. Is there
> something like that for KDE?
>

Do you know the author of kxicq?  I would  really like an ICQ client in 
kdenetwork.  IM is so important now.  If he would put it into our cvs it 
would get the 2.0 make over pretty quick I would bet.


-- 
Robert Williams       rwilliams@jrc-utah.com
Jarob Consulting      rwilliams@kde.org
Provo, Utah           rwilliams71@excite.com
USA

[prev in list] [next in list] [prev in thread] [next in thread]