<div class="gmail_quote">2011/7/22 Daniele E. Domenichelli <span dir="ltr"><<a href="mailto:daniele.domenichelli@gmail.com">daniele.domenichelli@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 21/07/11 22:52, David Edmundson wrote:<br>
> Oh those KJobs - I want to restore them. (this is a bit off topic, but<br>
> anyway) we need to wrap the PendingChannel Tp classes in something in<br>
> order to translate the error messages from raw codes into actual<br>
> translatable useful strings. Restoring those KJobs would be a good<br>
> approach.<br>
<br>
</div>We still need to figure out if the KJob approach is good... while it is<br>
good for a file transfer, I'm not sure if it is good for starting a text<br>
chat or a dbustube, maybe just a "regular" method is better.<br></blockquote><div><br>I think the KJob approach is way better, as it completely matches the Telepathy way of doing things, so I wouldn't give up on that<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
<br>
> My point was trying to be that the computer eventually has to talk to<br>
> telepathy, (via our code or via a library) at which point it could<br>
> just find out presence in real time.<br>
<br>
</div>I agree, but if you think about it, it's the same for everything that<br>
the contact can set, including name, avatar, etc., since we consider it<br>
"volatile" (that means that if the contact changes his name, the old<br>
name is deleted from Nepomuk and replaced by the new one)<br>
<br>
An approach could be to have our library to talk to telepathy directly<br>
but at the same time store only "events" on Nepomuk like name, presence,<br>
avatar changes, etc., but still other applications using only Nepomuk<br>
will need something to get the current information either using the<br>
library, or extracting the values from Nepomuk events, but that would<br>
require some knowledge and more complex queries. Or alternatively both<br>
events and current values should be stored.<br>
<br>
That's why I think that the approach that we are using at the moment is<br>
a good approach for now...<br>
<div><div></div><div class="h5"><br>
<br>
<br>
Daniele<br>
_______________________________________________<br>
KDE-Telepathy mailing list<br>
<a href="mailto:KDE-Telepathy@kde.org">KDE-Telepathy@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-telepathy" target="_blank">https://mail.kde.org/mailman/listinfo/kde-telepathy</a><br>
</div></div></blockquote></div><br>