Where to put QML Bindings for KDE frameworks?

[Martin Klapetek]

On Tue, Jan 28, 2014 at 7:10 PM, Kevin Ottens <ervin at kde.org> wrote:

>
> I don't think we'll get a one size fit all type of solution, that will
> heavily
> depend on the nature of the framework. For instance something like KConfig
> should probably provide it's own imports, it is in the natural order of
> things
> as it already provides a core/gui split. KIO is in pretty much the same
> situation.
>
> But for some others it is less clear... For those ones we'll have to
> decide if
> we want to change them toward providing several payloads as well (sounds
> doable for most except the *addons ones), or if we want the import to be in
> one of the imports provided by KDeclarative.
>

One of the downsides that wasn't mentioned yet (I think) is keeping the
imports away from their modules can (and possibly will) cause the imports
to bitrot and get behind the modules. Say that someone makes some changes
to the framework but forgets/doesn't know about imports in KDeclarative, so
those stay unupdated and may even break. Can also lead to "not my problem"
situation when the KDeclarative maintainer will say "that's code from kio,
talk to kio maintainer" etc.

So I think it makes sense to keep the code together.

Cheers
-- 
Martin Klapetek | KDE Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140129/7c50ef50/attachment.html>