KQuickControls

[Marco Martin]

On Monday 27 January 2014, David Edmundson 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. I expect a colour picker coming soon at
> least.

btw i have an early version of it in the config dialog of the wallpaper.. 
hopefully it may be reused.

> 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.

no, wouldn't make much sense

> Alternatively we can make a new framework for all KDE bindings. (such
> as KIO which is being discussed right now)
> 
> Thoughts?


i would really like one of the following scenarios:
* qml binding that use a particular framework in the same repo of the 
framework
* or, if they don't want qtdeclarative dependency, have a frameworkname-qml 
repository for each one.

the rationale rather than make a mega import for everything kde is exactly the 
same of frameworks themselves: if one wants to do an app that uses a single 
kde framework and want to use qml, they should be able to do so with few 
dependencies (so import org.kde.everything wouldn't really work).
so, since qml will be probably more and more used, in the future we will end 
up needing qml bindings for ~90% of the stuff in frameworks.
every framework having neatly its qml bindings looks nice to me..
comments?

-- 
Marco Martin