Where to put QML Bindings for KDE frameworks?

[Aleix Pol]

On Tue, Jan 28, 2014 at 12:58 PM, David Edmundson <
david at davidedmundson.co.uk> wrote:

> For a task in Plasma I've had to port KKeySequence to render on
> QtQuick, using QtQuickControls.
>
> I expect over time we will see more KDE widgets having QtQuick
> implementations as well. Same for a lot of our other frameworks, such as
> KIO.
>
> I can either add these components to KDeclarative, and create a new
> import. It is already in tier3, but I would need to add quite a few
> dependencies to this module.
>
> We could put these things in plasma, but I don't think that makes
> sense as it's not really related to Plasma at all.
>
> Alternatively we can make a new framework for all KDE bindings.
>
> Or we can make an imports directory inside each of the relevant
> framework. i.e so KIO provides QML bindings too. Advantages are we can
> then use the relevant private API of a library, but it has the
> disadvantage of increasing dependencies, and mixing old very stable
> API with brand new libraries.
>
> Original thread on plasma-devel here:
> http://mail.kde.org/pipermail/plasma-devel/2014-January/028162.html
>
> Discuss.
>
> David

_______________________________________________
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>

Well, there are many different needs, so we'll probably want to have
different solutions for them.

Bindings to interact with each framework, I'd say they should be installed
by the framework itself, but that's only one case. I think we probably want
a KQuickAddons as well, to put the components we create to extend Qt. (for
example, this component you created for bindings).

Aleix
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140128/2867d486/attachment.html>