[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: KQuickControls
From:       Martin Graesslin <mgraesslin () kde ! org>
Date:       2014-01-27 18:33:55
Message-ID: 5972706.FJE4o0ZRuX () martin-thinkpad
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Monday 27 January 2014 19:15:56 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.
> 
> 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. (such
> as KIO which is being discussed right now)
> 
> Thoughts?

Plasma won't be the only user of it, but most likely the first. Thus I agree 
that it shouldn't be in the Plasma framework.

I'm wondering whether it makes sense to have the "KQuickControls" together 
with the original QWidgets or to put them into a new framework. If the code is 
done right there is a business logic class which is used by the QWidget class 
and could be very easy to hook into a Quick class. But knowing the age of 
kdelibs I doubt that this is the case for all QWidgets.

So own framework or kdeclarative. My suggestion: send your mail also to 
frameworks-devel or bring up the topic tomorrow in the meeting.

Cheers
Martin
["signature.asc" (application/pgp-signature)]

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


[prev in list] [next in list] [prev in thread] [next in thread]