You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

rrr-jr

Beginner

  • "rrr-jr" started this thread

Posts: 11

Location: Earth

  • Send private message

1

Sunday, January 29th 2006, 8:42pm

[KOPETE] Feature requests

I've been looking all around for a place where I can post my feature requests for kopete and I guess this is the perfect place . I'm sorry if there is a place and I didnt find it :).
There are some things I would like to be implemented in kopete (for yahoo and gtalk coz thats what I use):
- the first thing is the buddy icon for yahoo which doesn't work ... the other users can't see my image ;
- the file transfer would be nice for yahoo but I understand thats in progress;
- sending messages to offline buddies doesn't work ... thats silly but doesnt workl;
- voice support for gtalk becoz for yahoo i understand it cant be implemented;
- webcam support doesnt work at all for me ... it works for a couple of seconds and then kopete shuts down !
Gentoo rulz !

2

Tuesday, January 31st 2006, 4:05pm

RE: [KOPETE] Feature requests

Quoted

Originally posted by rrr-jr
I've been looking all around for a place where I can post my feature requests for kopete and I guess this is the perfect place . I'm sorry if there is a place and I didnt find it :).
No, I think this is wrong place. The right place is http://bugs.kde.org . When you file a bug report, you can also select "feature request". At least some of these request already exists in the bug system.

If you post features request here, it isn't sure if it is read by a developer.

Quoted

Originally posted by rrr-jr
- voice support for gtalk becoz for yahoo i understand it cant be implemented;
Voice support for Jabber is implemented in the currrent development branch. The protocol doesn't exist that long, so it is logic that it takes some time. It's expimental and buggy at the moment (but seems to work).