Re: [Kmess-devel] Support of knewstuff for downloading emoticons

[Diederik v. d. B. <vd...@co...>]

On Sunday 20 November 2005 17:29, ha...@mp... wrote:
> Hi, i am interested to help in the development of kmess. I found some
> features lacking from kmess and i would like to try to implement them. I
> am not experienced, so i may not make it :)

We'll see what we can do :-) or drop an e-mail at my address if you're stuck 
with some coding problem.

> The first one is knewstuff support. I had already a patch accepted for
> kcontrol regarding knewstuff so i have previous experience on this. The
> code implementation is easy and except that we need 2 external xml files;
> the first essentially points to the second, and the seconds hlds all the
> information for the emoticons. Do we use <<standar>> emoticon support? Can
> we use emoticons from kopete for example?

It would be cool to be able to share emoticons between programs, and avoid 
duplicate work. I'd go for it. Seams like the Kopete emoticon stuff is a good 
start. There are even old KMess icons in $KDEDIR/share/emoticons/ :-)

and there are some other thoughts of mime I'd include here too:

- The XML stuff makes things only more cool. Our website is generated from XML 
already (using XSL off course), so this could be integrated nicely with our 
online HTML pages too.

- KMess doesn't handle custom emoticons in the chat sessions yet. I'm not 
asking you to write this too, but it is something you could keep in mind 
while designing the classes. ;-)

- Since KMess is still used with KDE 3.2 (even KDE 3.1 :-| ) we could use 
#ifdef KDE_IS_VERSION(3,3,0) to make the KNewstuff compile and include calls 
to KDE::version() at runtime to display the proper error messages or 
alternative options.

> Ps: i am behind a firewall, so i don't have access to the cvs service. Do
> we have nightly tarballs? If not i will send the patches against the
> latest release

You can download the CVSROOT at 
http://cvs.sourceforge.net/cvstarballs/kmess-cvsroot.tar.bz2, I'm not sure 
this is what you really want... Otherwise a ssh-tunnel could solve your 
problems (our developer cvs access uses ssh too). For small things, a patch 
against the current release would still work I think.

Greetings and welcome to the mailing list,

Diederik

-- 
Peace cannot be kept by force; it can only be
achieved by understanding.  -- A. Einstein