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

List:       kopete-devel
Subject:    Re: [Kopete-devel] Jabber plans
From:       Nick Betcher <nbetcher () usinternet ! com>
Date:       2002-06-06 3:16:14
[Download RAW message or body]

On Wednesday 05 June 2002 07:08 pm, Daniel Stone wrote:
> All,
> While I have a 5-day weekend starting in about 30 hours (whoohoo!), I'm
> also going to be extremely busy with exams et al during the next couple of
> weeks. Thus, I thought I might outline my rough plan for 0.5 to you guys;
> however, please do not implement stuff without talking with me first. I
> have a large Psi upstream sync to do, a cleanup to finish, and a lot of
> half-finished local code and ideas. It's not marking out my territory a la
> your common dog, just to avoid wasting both of our time.
>
> * Support transports.
>   - Every transport will have a separate JabberProtocol subclass; however,
> they
>     will not be listed as separate in the plugins page. This is my plan,
> anyway.
>     This is just so JabberProtocol isn't filled with a lot of ugly hacks to
> deal
>     with every transport known to man. It looks messy on paper, but will be
> pure
>     poetry in code. Or something.
>   - Despite this change, you will still add users on transports via the
> Jabber Add
>     New Contact page. So, you will select the Jabber protocol, not ICQ or
>     whathaveyou.
> * Support agents, e.g. Jabber User Directory.
>   - The JUD is a very commonly-requested feature. 'Nuff said.
> * Support viewing user info.
>   - Self-explanatory.
> * Support sending email-type messages, as opposed to chats.
>   - Currently all we have is KopeteChatWindow. However, fire up a client
> such as Psi or WinJab, and you will see that you can either start a chat
> with a user (a la KopeteChatWindow), or just send a message. This
> distinction is meant so that clients that differentiated properly between
> the two would
>     be able to store the "email-type" messages. It's just useful. I've
> already started implementing this locally. Thankfully I was able to ram
> through enum KopeteMessageManager::WidgetType, so this is Easy(tm) to do
> without touching libkopete (well, much; all it needs is more else if's, no
> API changes). This is IMHO one of the more important changes.
> * Massive UI cleanups.
>   - Guys, I *still* need help here. None of the Jabber stuff has layouts,
> and it's pretty ugly and unintuitive. Can someone please help me with this?
> * Support file transfers.
>   - Nick, I told you there was a reason KMM should have a file sending

Well, I was waiting to make a file transfer dialog so the API could stabilize 
in libkopete. Now since that has roughly happened, I will consider doing such 
a thing. Please read my next email reguarding my future plans (short and long 
term).

> widget. * Support group chats.
>   - This will require a bit of work in KMM/KCW, but is definitely doable.
> This actually has two parts - the necessary support in libkopete, and the
> Jabber
>     support itself. Jabber has a concept of group chats similar to IRC
> channels;
>     you join the channe^Wchat, and others join and part as they please. You
>     don't send a message to all the users, you send a message to the
> "channel",
>     and the server takes care of the details.
> * Support viewing user info.
>   - I don't think I really need to say anything here, do I?
> * Miscellaneous nifty stuff.
>   - Just things like showing away messages/reasons, that sort of thing.
>
> As you can see, I have a mammoth task ahead of me (you too can help! ;).
> Thankfully, I have holidays coming up after my exams, which means I'll have
> a lot
> of spare time. Hopefully I'll also get a very decent laptop very soon,
> which means
> lots of Kopete hacking (I spend 3 hours per day in transit to and from
> school, and going to Mum's place takes 2 hours, not to mention the fact
> that Mum's only
> PC runs Windows, and is rather slow ...).
>
> When this list is all ticked, Kopete will have truly kick-arse Jabber
> support. When I'm at the stage of adding lots of features to Psi to support
> what Kopete's
> doing, then I'll be happy. Then, and only then.
>
> -d
>
> (yes, it's unsigned; yes, this is Eudora ... I'm at school)

Wow, the formatting sucks too ;)

>
> _______________________________________________
> Kopete-devel mailing list
> Kopete-devel@mail.kde.org
> http://mail.kde.org/mailman/listinfo/kopete-devel

_______________________________________________
Kopete-devel mailing list
Kopete-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kopete-devel
[prev in list] [next in list] [prev in thread] [next in thread]