Le mercredi 13 juin 2007, Gustavo Pichorim Boiko a écrit :
> Hi
>
> After thinking a bit more about that subject, I've got to write a proposal
> on that subject.
>
> http://people.mandriva.com/~boiko/kopete/user_info/



From your page:

> One approach to simplify that would be to share a single identity across all 
> protocols, but this does not fit in all cases (for example, in a jabber 
> account used for work contacts, you might want to put a different photo than
> the one you would put in a personal account), and for the uncovered cases we
> still lack a solution.   

That's the point of having multiple identities.

My idea of a identity is the same as a meta-contact.  (or like a meta-account)
An Identity contains accounts like a meta-contact contains contact.

account that are in the same identity share all data. that include nickname, 
photo, vcard,  and even status and status messages.
by vcard i mean the "identity" card, basically the same as the one in kabc.
Identities would probably replace different accounts in the status bar.

This is anyway just my utopia.

I have not solved the problem of synchronisation 


> What I am proposing is to add as many properties as possible to the
> protocol-independent account layer (which would be Kopete::Account or
> Kopete::Contact, but probably the first).  
> The existence of such properties could be queried

It would be interesting if your "new widget" could be also be used for showing 
contacts (and meta-contact) properties. That's why IMO property should be at 
contact level (and they are already),  and the existence of properties could 
probably belong to Kopete::Protocol

> Shared Config Widget vs Custom Properties
> [...] 

Yes, that's good.

> The visual representation
> [...]

I'm not sure we should place that widget into the configure account page.
But place this in another dialog, like we already do in Jabber and AIM.

The reason is that the editaccount is more for connection and preference.
Also, for most protocols, that information is stored in the server, and then 
require to be connected (and then make no sens to put that widget when adding 
a contact)
It make sens to me to be able to show this widget also in the dialog of 
contact information  (and have theses dialog common either)

About your blender-like idea, it is AFAIK not used in KDE, I don't know why. 
It may be interesting.


Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
kopete-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kopete-devel

Reply via email to