Le lundi 7 mai 2007, Michaël Larouche a écrit : > Le May 6, 2007 17:32, Olivier Goffart a écrit :
> > the task *MAY* have no subtask *if the protocol doesn't want to perform
> > any action*
> Okay, how do you handle the deletion of the contact on the protocol server
> in your vision ?
Normal protocols will add a subtask. But if there is no need to remove
contact on server, no need of subtask.
> My idea was more like:
>
> class Kopete::ProtocolTaskFactory
> {
> virtual KJob *createDeleteContactTask() = 0;
> virtual KJob *createAddContactTask() = 0;
> };
> [...]
This doesn't allow plugins to add tasks. It is also harder to add task
without breaking binary compatibility.
> Though your idea isn't bad either.
My idea is less object oriented.
Maybe we can have a look at the QEvent system, and create a KopeteTaskEvent
which is sent to the object when a new task regarding him is created. But
this seems more complex.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
