Le lundi 8 octobre 2007, Will Stephenson a écrit : > On Sunday 07 October 2007, Olivier Goffart said:
> > Another idea is to call the class ProtocolContact or AbstractContact > > You know 'abstract' is reserved for indicating an abstract data type, don't > you? > ImAddress? It's about the class name, and the current Kopete::Contact class is more than just a representation of the address, it contains all the protocol code. that's why I suggest Kopete::AbstractContact , and implementation of it are our current MSNContact, JabberContact, .... > I'm with Gof on this (surprise surprise). And if Gof, the leading > proponent of "Kopete as classic standalone IM client" in recent times, now > says this, I'm interested to know why you feel we should stop with an > 'INSTANT MESSENGER'. Unrelated, but I was not really proponent of "standalone IM client", I was just against the disparate view of telepathy. After more reflexion, the reason is probably because the whole Kopete codebase in not designed in that model. Going with telepathy probably mean a rewrite of everything but the UI. This is one of the reason I have been less active in Kopete lately, because I feel Kopete in his current form is going to dead.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
