[PATCH] WIP: use kirigami plugin instead of embedding in qrc

[Dirk Hohndel]

> On May 5, 2016, at 10:13 AM, Dirk Hohndel <dirk at hohndel.org> wrote:
> 
> 
>> On May 5, 2016, at 10:07 AM, Marco Martin <notmart at gmail.com> wrote:
>> 
>> On Thursday 05 May 2016 09:26:50 Dirk Hohndel wrote:
>>> In that context, is there a plugin, yet, with which I could test this?
>>> I looked at Kirigami master this morning and didn't see any sign of
>>> such a dependency, but maybe you are holding that back, waiting
>>> for us to get our act together?
>> 
>> the plugin atm is there but dummy (src/kirigamiplugin.cpp), didn't add other 
>> things in there so far, as wouldn't be possible to use them.
>> 
>> it should already be possible to see if it gets correctly packaged, since the 
>> qmldir includes it, an import org.kde.kirigami would fail if the plugin is not 
>> there
>> 
>> to move further to me is important to know if is easy enough to deploy, as i 
>> wouldn't move in a direction that makes things too hard for who is using it
> 
> I'm sure we can figure this out - I'll make playing with this a priority and
> will report back :-)

So Kirigami requires ECM. and KF5Plasma. and that requires KF5Activities. Which requires Boost. And KF5.

I think at this point we need to talk about scope.

No, it is not reasonable to assume that I want to build all of KDE just because I want to use Kirigami. Either the requirements in the CMakeLists.txt file are too broad and none of this is actually needed, or this may be the point where Subsurface needs to decide if building on top of Kirigami and there for apparently all of KF5 is the way we want to go.


/D