Why using Nepomuk as a contact store is probably not a good idea

[David Edmundson]

On Thu, Jul 21, 2011 at 10:24 PM, Daniele E. Domenichelli
<daniele.domenichelli at gmail.com> wrote:
> On 21/07/11 18:34, David Edmundson wrote:
>>   - To do something useful like start a chat, I have to link against
>> TpQt4, find the actual telepathy contact and ensureTextChannel().
>
> The initial idea that I started to implement for my GSoC last year was
> to offer methods like ensureTextChannel() but that accept nepomuk
> resources (and kde-telepathy contacts) instead of Tp::Contact
> The logic behind the choice of the account, of the contact, etc is
> hidden to the user.
> Therefore you can ensure a text channel with a person, without knowing
> which account will be used or send a file to a person using the best
> account online (or perhaps by e-mail if the user is not available or if
> he doesn't support file transfer).

Oh those KJobs - I want to restore them. (this is a bit off topic, but
anyway) we need to wrap the PendingChannel Tp classes in something in
order to translate the error messages from raw codes into actual
translatable useful strings. Restoring those KJobs would be a good
approach.

My point was trying to be that the computer eventually has to talk to
telepathy, (via our code or via a library) at which point it could
just find out presence in real time.

>
> Of course there is still a lot of work to do before this can be done
>
> Daniele
> _______________________________________________
> KDE-Telepathy mailing list
> KDE-Telepathy at kde.org
> https://mail.kde.org/mailman/listinfo/kde-telepathy
>