What should be in the contact list
David Edmundson
david at davidedmundson.co.uk
Wed Feb 9 22:27:22 CET 2011
Martin seems to be doing an awesome job on the contact list, but I feel we
need to discuss what should actually be in the contact list, and maybe
divide up some tasks to get things done quicker/give new people something to
do. Some of the dialogs/actions (such as add a contact) can easily be
developed outside of the contact list, and then merged in at any point, so
we can get a few more people working simultaneously.
So to get the list started:
- Super sexy model delegates to match how we designed the core parts of the
contact list.
Martin has the photos from the Sprint and is making a start on this.
- Some way of adding a new contact.
- A dialog for editing your "personal information", (alias, the XMPP
contact information)
I like how empathy does this with the dialog. I can't think of anything
better.
- A way of joining rooms
Ideally like Empathy which can query room lists, rather than my previous
simple text box. I've seen the Tp-Qt4 API documentation on doing this.
-- below are some more controversial thoughts.
- A text filter for contacts?
- A way of selecting your current presence?
(slightly controversial, given we have a plasmoid, but I can see plenty of
reasons to have it in the contact list as well. It'd be a bit clearer. I
don't think it goes away from desktop integration)
- A list of current connection issues?
(again like Empathy which displays warning at the top of the list if
anything failed to connect, then launching the accounts-kcm as appropriate)
What else either needs to go into the contact list application, or have you
any ideas for stuff that should go here?
David
P.S sorry for spamming the ML so much recently! Especially with all the bug
reports and review stuff.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-telepathy/attachments/20110209/e48a5312/attachment.htm
More information about the KDE-Telepathy
mailing list