<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Feb 5, 2015 at 10:24 PM, Sune Vuorela <span dir="ltr"><<a href="mailto:nospam@vuorela.dk" target="_blank">nospam@vuorela.dk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On 2015-02-02, Martin Klapetek <<a href="mailto:martin.klapetek@gmail.com">martin.klapetek@gmail.com</a>> wrote:<br>
> Another part that KDE Telepathy needs is KAccounts and we'd like<br>
> to move that one too, probably to kde-runtime but there seems to be<br>
> some disagreements of the purpose of kde-runtime. KAccounts is<br>
<br>
</span>I'm pretty sure that everything in kde-runtime is only for kdelibs. in<br>
Frameworks, everything has been moved into the framework it is a part<br>
of.<br>
<br>
KAccounts sounds mostly like a network thing to me, at least so far. If<br>
it becomes more than a network accounts thing, maybe it should become a<br>
framework ?<br></blockquote><div><br></div><div>At this point it's really about the KCM and the kded module, doesn't</div><div>sound too frameworky to me...</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">
> [1] KDE Telepathy repos are:<br>
> ktp-accounts-kcm<br>
> ktp-approver<br>
> ktp-auth-handler<br>
> ktp-call-ui*<br>
> ktp-common-internals<br>
> ktp-contact-list<br>
> ktp-contact-runner<br>
> ktp-desktop-applets<br>
> ktp-filetransfer-handler<br>
> ktp-kded-module<br>
> ktp-send-file<br>
> ktp-text-ui<br>
<br>
</span>would this also be a time to maybe reconsider if one went a bit<br>
overboard with the original repository splitting?</blockquote><div><br></div><div>This follows the upstream Telepathy philosophy (and hey, also unix), where</div><div>everything is fully standalone component and can work without the others.</div><div><br></div><div>Also kinda follows the frameworks, this way anyone can pick the component</div><div>that they need/want (like the auth handler or filetransfer handler) and not have</div><div>to drag the whole stuff.</div><div><br></div><div>Personally I find the structure like that better (as someone who works with</div><div>the code everyday); these days everything is/can be scripted anyway.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Having a libkdetelepathyinternalsprivate as a *public* available library somehow<br>
smells like a bit wrong to me.<br></blockquote><div><br></div><div>Right, this has been one of the #1 goals back in the times, to have this</div><div>a proper public library. But everyone from the original team is now gone,</div><div>raising the question wasn't really a success [1]. But I agree this should</div><div>be done.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">
> *) ktp-call-ui is not yet ported and will most probably be dropped from<br>
> the 15.04 release<br>
<br>
</span>So that one is staying in ... playground ... so far?<br></blockquote><div><br></div><div>Extragear.</div><div><br></div></div>[1] - <a href="http://mail.kde.org/pipermail/kde-telepathy/2014-October/012250.html">http://mail.kde.org/pipermail/kde-telepathy/2014-October/012250.html</a><br clear="all"><div><br></div><div>Cheers</div>-- <br><div class="gmail_signature"><div><span style="color:rgb(102,102,102)">Martin Klapetek | KDE Developer</span></div></div>
</div></div>