On Sunday 06 August 2006 15:52, Olivier Goffart wrote: > > and the contactlist data structure ought to be able to feed directly into > > views. > > What do you mean ?
having a data structure for contacts, a view and then a bridge between those two that needs to maintained is not necessary these days. we have the ability to provide a data model and tell a view "show this model" and with 0 work to show that model in the view have it shown. this means when you modify the data structures the views (which may not be visual, btw) are updated as there is no sync issue to do with data<->view bridges. > > one of the use cases kopete will run into is being able to bridge the > > contact data to lists that appear on the desktop or in other > > applications. identity is moving more and more towards sharing and > > coordinating this data between multiple apps. > > And that's one important topics. > > But I fail to see how QAbstractItemModel helps. > > What we need here is a defined dbus interface. the dbus interface would interface to the data structure. if someone removes a contact via dbus and the data structure is a QAM then the visual views will update automatically. no manually synchronizing changes from out of the GUI with the GUI. no manually synchronizing changes in 2 views with the data structures and each other. etc ... -- Aaron J. Seigo Undulate Your Wantonness GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
pgp95ztU979dx.pgp
Description: PGP signature
_______________________________________________ kopete-devel mailing list kopete-devel@kde.org https://mail.kde.org/mailman/listinfo/kopete-devel
