Le samedi 9 juin 2007, Gustavo Pichorim Boiko a écrit : > Hello > > I was configuring kopete, and setting the avatar images, nickname and so, > and I saw many different dialogs to configure each protocol account. > > So, I'm starting to work a bit on this: > I'll try to get information that are common to all protocols (like > nickname, photo - that might not be available on some, but is available on > most, name, etc) and put this in a single widget. > > For the user info configuring dialog, I'm planning to create it like the > ICQ one, configuring pages are selected from the side bar icons, and the > first entry will be a common info page for all protocols. > > I don't know if I made it clear, but as soon as I have something to commit, > I will send a patch for you to take a look and approve/reject > > In the mean time, I would like to get some feedback and ideas from you. > > Cheers
I think we need to see different categories of fields
#a) Offline fields:
Those that are required in order to connect
(login/password/server/ssl/...)
#b) Online fields:
Those that are account option that can be modified only when connected
#c) Protocol global config fields:
behavioral configuration setting independent of the account
#d) Identity fields:
fields that probably belong to the global identity (the vcard)
I think that #c doesn't really belong to the account configuration, it's now
placed there just because there is no other place to place them. Where to
place those settings ? Good question. In old version of kopete, protocols
(and plugin) was able to add configuration page in the kopete config dialog.
But this has been changed for usability issue IIRC.
#d should be in the identity page, and probably not in the protocol page.
But what about users that may want to give different information in different
account ? i think that the multiple identity cover that need.
What about field that are not available in each protocols ? (MSN doesn't have
a full vcard, unlike Jabber) The identity page should contains all fields.
If the user doesn't have a protocol that support a field, the field should be
disabled.
Now we have the #a and #b fields.
IMO, when adding a new account, only #a fields should be shown (maybe with #c)
But also some field to register a new account
Here was my little analysis :-)
Now, to reply to your mail, I think that fields that are common to each
protocols are only in categories #a and #d. I've already discussed about #d,
and there is already the PasswordWidget for #a.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ kopete-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kopete-devel
