[Kde-pim] QtQuick ToDo API / Plasmoid

[Kevin Krammer]

On Thursday, 2014-02-13, 20:35:59, Mark Gaiser wrote:

> The idea is nice but you will face some real hard difficulties in
> doing what you want to do.
> You can't do this for Plasma Next. The reason being Qt 5.x. The
> kdepimlibs are all still Qt 4.x based and not yet ported to Qt 5.
> 
> You can do this if you port kdepimlibs to Qt 5.

Really depends on the goals. The core of the idea discussed here is to create 
a QML API, which can be done with either version of Qt, so Qt4 based 
kdepimlibs will work as well.

Qt5 only comes into play if an extended goal involves creating a QtQuick2 
based UI. QtQuick1 or widget based or other Qt4 QML UI framework would be 
fine.

So it really depends on the scope that is proposed.

> Another option would be to use QDBusInterface like you suggested
> already. But is that worth the extra trouble?

That is highly unrealistic for anything involving data.
The D-Bus approach was mentioned as an option for the Workspace integration 
idea, which deals with Akonadi status and control and is thus not tied to the 
Akonadi Server Access Protocol :)

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20140213/718a92ec/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/