On Wed, 2010-10-27 at 11:45 +0100, Marco Barisione wrote: > On Wed, 2010-10-27 at 01:20 -0500, Mateu Batle wrote: > > Right, I don't know much about metacontacts but I guess they would be > > handled by a separate model. > > Anyway currently I think metacontacts are out of the scope of tp-qt4. > > I agree, different platforms using qt could want to use different ways > to represent meta-contacts. On GNOME we use libfolks, KDE uses Nepomuk > and Meego seems to want to use QtContacts (from QtMobility). The latter > is just an abstraction on top of different backends, for instance I > wrote a backend for QtContacts that works on top of libfolks. > > To be honest, I wonder if it's useful to have a model that none of these > platforms will use. Wouldn't it be more useful to have the UI bit and > models on a library on top of something like QtContacts?
It should still be easy to write a simple Telepathy client using just tp-qt4. The world exists of more thing then these three platforms :) Some UIs might not want to use meta-contacts at all or just focus on one protocol, or or... :) -- Sjoerd Simons <[email protected]> Collabora Ltd. _______________________________________________ telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
