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

I'm pretty sure that everything in kde-runtime is only for kdeli= bs. in
Frameworks, everything has been moved into the framework it is a part
of.

KAccounts sounds mostly like a network thing to me, at least so far. If
it becomes more than a network accounts thing, maybe it should become a
framework ?

At this point it's real= ly about the KCM and the kded module, doesn't
sound too frame= worky to me...
=C2=A0
> [1] KDE Telepathy repos are:
>=C2=A0 ktp-accounts-kcm
>=C2=A0 ktp-approver
>=C2=A0 ktp-auth-handler
>=C2=A0 ktp-call-ui*
>=C2=A0 ktp-common-internals
>=C2=A0 ktp-contact-list
>=C2=A0 ktp-contact-runner
>=C2=A0 ktp-desktop-applets
>=C2=A0 ktp-filetransfer-handler
>=C2=A0 ktp-kded-module
>=C2=A0 ktp-send-file
>=C2=A0 ktp-text-ui

would this also be a time to maybe reconsider if one went a bit
overboard with the original repository splitting?

This follows the upstream Telepathy philosophy (and hey, also unix),= where
everything is fully standalone component and can work with= out the others.

Also kinda follows the frameworks,= this way anyone can pick the component
that they need/want (like= the auth handler or filetransfer handler) and not have
to drag t= he whole stuff.

Personally I find the structure li= ke that better (as someone who works with
the code everyday); the= se days everything is/can be scripted anyway.
=C2=A0
Having a=C2=A0libkdetelepathyinternalsprivate as a *public* avail= able library somehow
smells like a bit wrong to me.

Right, t= his has been one of the #1 goals back in the times, to have this
= a proper public library. But everyone from the original team is now gone,
raising the question wasn't really a success [1]. But I agree = this should
be done.
=C2=A0
> *) ktp-call-ui is not yet ported and will most probably be dropped fro= m
> the 15.04 release

So that one is staying in ... playground ... so far?

Extragear.

[1] -=C2=A0= http://mail.kde.org/pipermail/kde-telepathy/2014-October/012250.html

Cheers
--
Martin Klapetek | KDE= =C2=A0Developer
--047d7bb04b56a79779050e6911c2--