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

List:       kopete-devel
Subject:    Re: [Kopete-devel] patch, and other stuff
From:       Andres Krapf <dae () chez ! com>
Date:       2002-05-05 17:49:50
[Download RAW message or body]

On Sunday 05 May 2002 18:33, Martijn Klingens wrote:
> messageManager->messageSent( KopeteMessage *msg ) as a method call. Maybe
> this is simply a place where the good old C++ callbacks are actually more
> useful than the Qt styly signals/slots? ;-)
> Generally I'm strongly against such appraches, but given that the protocol
> needs to know about KMM's existance and API anyway, and added to that all
> the problems with the message acting as intermediate entity, I'm more and
> more inclined to see it as a solution rather than a sin... Opinions?

i feel about the same... i'm usually inclined to decouple things whenever 
possible. but i'm beginning to think that maybe qt signal/slots might have 
been overused... they're not always the best solution.

until there's time to find a better solution (real decoupling and no signal 
slot crazyness), i'll accept any of these two approaches, so that we can move 
on with the other things to be done. pick one and commit it :-)

on the matter, before release time we should ideally come to the same level of 
functionality that we had with the previous release. for example, i'm 
thinking of aim warnings or icq send-through-servers. so i'll probably set 
out to work on protocol personalization of the chatwindow (and kmms?) next. 
is there anybody working on this ? any plans been drawn ?
right now all i could see in this endeavour was the optionsWidget(). it's not 
very well defined, and also restricts the extensibility... there's probably a 
better way. comments ?

> I'm not sure how KMM maintains history internally, though I hope that it's
> something like a QPtrList<KopeteMessage> or so, which is flexible and
> supports a user-definable history length in the future. The history as
> written to disk is probably not useful enough for the user's scroll back
> history in the chatview.
> Not sure here though, this needs more thought. You probably know better
> yourself :-)

i'm not sure either... i think the KMM doesn't hold any history whatsoever. 
i've taken a quick look at it, and it seems nobody holds a history. only the 
widget used to display the messages :-), and that's one big QString.

cheers,

-- 
Andres
_______________________________________________
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]