On Thu, Jan 28, 2016 at 8:12 PM, Stephen Kelly wrote:
> Aleix Pol wrote:
>>> QML bindings are "one layer above" the class they bind. Just like
>>> kdebindings is separate rather than "mixed into every framework". Having
>>> the javascript bindings for KIO in KIO would tick all your criterias
>>> a
Aleix Pol wrote:
>> QML bindings are "one layer above" the class they bind. Just like
>> kdebindings is separate rather than "mixed into every framework". Having
>> the javascript bindings for KIO in KIO would tick all your criterias
>> above ("simpler to use because part of the framework", "all th
On Thu, 28 Jan 2016, Aleix Pol wrote:
The problem I see with having a big KDeclarative framework is that it
requires to have many KDE Frameworks available. The root
CMakeLists.txt file [4] already shows that it's full of conditionals
and it largely depends on whether the actual framework is avai
On Thu, 28 Jan 2016, Aleix Pol wrote:
Personally, I don't really see how QtQml build-time dependency is
holding back the adoption of KCoreAddons. Is QtQml something that
often isn't available?
All dependencies are bad. Really -- I know I sound like a broken record here,
but _all_ dependencies
On Thu, Jan 28, 2016 at 1:11 AM, David Faure wrote:
> On Wednesday 27 January 2016 18:19:49 Aleix Pol wrote:
>> Hi,
>> I would like to move KCoreAddons qml plugin into KCoreAddons. Now it's
>> KDeclarative where we are dumping all QML plugins.
>>
>> I think it's a good idea because:
>> - it simpli
On Thursday, January 28, 2016 1:11:38 AM CET David Faure wrote:
> I honestly don't see the problem with having this in KDeclarative, but maybe
> I'm missing a good reason for splitting such qml plugins into a separate
> framework. Or maybe there's no point in doing that either.
The problem is that
On Wednesday 27 January 2016 18:19:49 Aleix Pol wrote:
> Hi,
> I would like to move KCoreAddons qml plugin into KCoreAddons. Now it's
> KDeclarative where we are dumping all QML plugins.
>
> I think it's a good idea because:
> - it simplifies usage the plugins for such frameworks (kcoreaddons is
Hi,
I would like to move KCoreAddons qml plugin into KCoreAddons. Now it's
KDeclarative where we are dumping all QML plugins.
I think it's a good idea because:
- it simplifies usage the plugins for such frameworks (kcoreaddons is
not the only one).
- it ensures the code related to a feature is to
