Le jeudi 14 juin 2007, Gustavo Pichorim Boiko a écrit : > IMO chatwindow will still use the myself() contact from the account, no? > I thought about that, and we would need to still keep the myself() contacts > for the protocols, they would still be needed. > > The identity contact would be used to set online status for the identity > accounts, and to set/get user info (either from the akonadi side, or from > the server side, or from the info dialog.
So there will be two myself() contact ? This look strange to me. > What would be the advantage of using metacontact? The fact that contact must have a metacontact. That could be a fake metacontact. But i suggest to use the metacontact as information container since we have it. But what's the advantage of using Kopete::IdentityContact, and not just Kopete::Identity and Kopete::Account > > nickname source and photo source are specially for contact that are _not_ > > the myself contact. (it's also used for the myself contact) > > It is used in the metacontact (that's why I think metacontact is not a good > idea for the identity. Theses source can be ignored for the myself() metacontact. > > theses source are in order to know from which contact comes the nick and > > the avatar if you have several contacts into a contact in your > > contactlist, this is not related to identity (althought the global > > identity code also use that, but that's unrelated) > > That is what I propose: we do not use different photo/nickname for accounts > on the same identity: they are all synchronized and use the same info (the > info does not come from the account, but from the identity contact) yes, source can be ignored So in other words: - Each Kopete::Contact in the contactlist is in one or several Kopete::MetaContact - Each KopeteAccount is in one or several Kopete::Identity - there is a Kopete::Contact *Kopete::Account::myself() - there is a Kopete::MetaContact *Kopete::Identity::myself() - One can REMOVE Kopete::MetaContact *Kopete::Contactlist::myself() Where the information reside is implementation detail. Is it better to place is in the Kopete::Identity or in the Kopete::Identity::self() ? I don't mind really, this depends of how the code can be done the more easily. I personally think that Kopete::Identity::self() is a good place because that information need to be accurate anyway (so chatwindow dispay good tooltip) so the information is accurate. All the fooSource method can be ignored by setting a "CustomSource"
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
