Ok, I'd take a look at the fake backend. Who currently codes the real backend, so we can coordinate with him?<div><br></div><div>Marty<br><br><div class="gmail_quote">On Mon, Nov 22, 2010 at 16:06, George Kiagiadakis <span dir="ltr"><<a href="mailto:kiagiadakis.george@gmail.com" target="_blank">kiagiadakis.george@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">2010/11/22 Chinmaya Padhi <<a href="mailto:padhi.chinmaya@gmail.com" target="_blank">padhi.chinmaya@gmail.com</a>>:<br>
<div><div></div><div>> Hi ,<br>
><br>
> Yesterday , I was an observer to the discussion that happened in the<br>
> kde-telepathy channel . With the wiki updated with some latest tasks ,<br>
> I am interested to contribute to these items :<br>
><br>
> (Re-)write the contact list UI.<br>
> (Re-)write the call UI (just the UI, not the actual call mechanism).<br>
><br>
> I am not aware of the current development state , but would prefer the one<br>
> which can be tested easily . I believe these tasks require QML<br>
> and it will be a great practical experience for me to use my QML knowledge<br>
> in this project.<br>
><br>
> Please share your inputs !!<br>
<br>
<br>
</div></div>Hello and welcome,<br>
<br>
You are welcome to adopt these tasks, or parts of them. The problem<br>
with both of these tasks is that no functional backend exists yet.<br>
The contact list requires a contacts model, which will be provided by<br>
libktelepathy. Before implementing it, some issues need to be fixed in<br>
the nepomuk integration service. The call ui needs a functional<br>
backend as well, which is blocked on missing functionality from other<br>
libraries (farsight, telepathy-qt4, see the wiki for details).<br>
<br>
However, we decided that both could be implemented in parallel with<br>
the development of the backends, using a fake backend for testing. For<br>
the contact list, you could implement a fake model with some static<br>
contacts on it, and for the call ui, you could implement a small<br>
testing library that implements the same interface as the call library<br>
that will be (re-)written.<br>
<br>
I think that in both cases, having those testing backends will be<br>
useful even when we have the real backends working, so that we can<br>
make unit tests for the ui or make ui changes easier (so that for<br>
example I don't have to start a conference just to test a change in<br>
the ui).<br>
<br>
Perhaps the contact list is easier to start with, so you could start<br>
experimenting if you wish. Just make sure to coordinate the model<br>
interface with others, so that the real model can be implemented with<br>
the same interface. Similarly for the call ui, of course.<br>
<br>
Best regards,<br>
<font color="#888888">George<br>
</font><div><div></div><div>_______________________________________________<br>
KDE-Telepathy mailing list<br>
<a href="mailto:KDE-Telepathy@kde.org" target="_blank">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></div>