<div class="gmail_quote">On Fri, May 6, 2011 at 10:49 AM, Daniele E. Domenichelli <span dir="ltr"><<a href="mailto:daniele.domenichelli@gmail.com">daniele.domenichelli@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello,<br>
<div><div></div><div class="h5"><br>
On 05/05/2011 11:26 PM, Marc Mauri Alloza wrote:<br>
> I'm preparing my proposal for Season of KDE. This week I've been<br>
> talking with people of kde-telepathy and kobby to get information<br>
> about how this should be implemented. I have a doubt about where<br>
> this should be implemented. Maybe inside KatePart or as a subclass<br>
> of KatePart? The goal is that my work could be reused easily in<br>
> other projects with a minimum (or zero) impact on code of the<br>
> application that wants to adopt the collaborative edition features.<br>
<br>
<br>
</div></div>I don't know where this should be implemented, probably in KatePart, but<br>
you should ask this to kate people...<br>
Anyway, how do you plan to use telepathy with kobby and/or the infinote<br>
protocol?<br>
I had a look at this last summer (before my gsoc proposal) and I didn't<br>
come to an easy solution...<br>
<br>
You could tunnel the protocol using a streamtube, (and that's quite easy<br>
to do) but then you get a protocol that handles connection, chat, etc.<br>
transported into another protocol that handles connection, chat etc, and<br>
that's quite ugly and redundant.<br>
<br>
Another option is to support only a subset of the inifinote protocol<br>
stripping all the unneeded stuff and let telepathy handle connection and<br>
chat and just use a streamtube to transport the collaborative editing<br>
messages, but I didn't investigate the protocol that much and I don't<br>
know if this is possible.<br>
<br>
Last option is to strip the infinote protocol from the unneeded stuff,<br>
write a XMPP XEP (there is probably something similar already), add a<br>
new channel type to the telepathy-spec and implement it in<br>
telepathy-glib, telepathy-gabble, telepathy-qt4 and finally use it in kate!<br>
<br>
Last one is probably the hardest method, but definitely the cleanest...<br>
and that's why I support it. :-D<br>
Unluckily it is also the less related to kde (and that's also the reason<br>
why I abandoned the idea of collaborative editing using telepathy in kde<br>
for last summer gsoc).<br>
If you choose this method you should definitely talk about this with<br>
xmpp and telepathy developers before starting.<br>
<br>
<br>
Cheers,<br>
Daniele<br>
<br>
<br>
P.S. Please don't feel discouraged from this, I really support the idea<br>
of collaborative editing using telepathy, but I don't like the idea of a<br>
quick hack just to make it work! ;)<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>
</blockquote></div><br><div>I'm not sure how this works but sounds to me like we're making it slightly more complicated than it is. Why isn't a telepathy socket enough to send information?</div><div><br></div>
<div>I've always understood that telepathy can handle this kind of connection... Does it clash with the rest of services?</div><div><br></div><div>Aleix</div>