Hi Marco,<br><br>I'm am working on Calligra Mobile as an Intern at Nokia. Just remembered that you had sent this mail. I understand that libkdeclarative is planned to be *the* way to access essential kdelibs functionality. If so, I was thinking about adding functionality to libkdeclarative as per needs arise for calligra mobile.<br>
<br>e.g. right now I need a way to access Image loading in QML similar to KIcon("kwords.png"), so we can add something to libkdeclarative, right?<br><br>Cheers,<br><br clear="all">-- <br><div><br></div>Shantanu Tushar (UTC +0530)<br>
<a href="http://www.shantanutushar.com/" target="_blank">http://www.shantanutushar.com</a><br><br><div class="gmail_quote">On Sun, Jan 9, 2011 at 10:11 PM, Marco Martin <span dir="ltr"><<a href="mailto:notmart@gmail.com">notmart@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi all,<br>
during last couple of days I've been working on<br>
git@git.kde.org:scratch/mart/libkdeclarative<br>
<br>
This is a thing we agreed upon (and that I promised to do ;) at the mobile<br>
sprint.<br>
It's a little ~60KB library that's meant to be used inside KDE apps that are<br>
using QML, what do they do? but before, a bit of history:<br>
<br>
Since 4.6, Plasma has bindings to write plasmoids using just QML/Javascript,<br>
and especially in the light of our previous pure JS bindings, we immediately<br>
had some issues, that made KDE integration really poor, namely:<br>
* no way to use our own i18n<br>
* not possible to use Icons, pixmap and images (only pathnames of on-disk<br>
images)<br>
* no kconfig, kjobs<br>
* all urls manipulation hidden deeply into default qml elements only accepting<br>
strings<br>
<br>
This mostly because 2 severe design limitations of QML:<br>
* no access to the QScriptEngine<br>
* read only QScriptEngine main object<br>
<br>
that made impossible among other things to register any non-qobject class or<br>
global functions. Both are possible to be "reverted" in a quite hacky way, but<br>
so needed that made the hack acceptable to us, so now the QML based plasmoids<br>
can do all of the above without problems.<br>
<br>
Talking with the PIM people we discovered they had all of the same problems,<br>
so we agreed with them to have a KDE-wide solution that would make easy to<br>
anybody to use in a nice way what of kdelibs makes it so uhm, kdelibs ;)<br>
<br>
This library is basically a class, that after setting a QDeclarativeEngine<br>
with initialize() pulls the qscriptengine out of it, then replaces the main<br>
object with a writable copy.<br>
<br>
the setupBindings() function (unsure if keeping this step optional or just<br>
pput it into initialize()) binds in the main object goodies like i18n, kjob,<br>
kconfig, kicon and kurl.<br>
<br>
at the moment it links to qtdeclarative, kdecore and kdeui (just for kicon, if<br>
QIcon::fromTheme works good enough perhaps we can keep kdeui out)<br>
<br>
This would go in a (probably separate library) in kdelibs, making it possible<br>
to use from qml plasmoids as before or also in c++plasmoids or non plasmoid ui<br>
components of plasma (where we still don't have the same nice bindings)<br>
but also from completely independent applications like Kontact touch/calligra<br>
mobile/whatever.<br>
<br>
Cheers,<br>
<font color="#888888">Marco Martin<br>
_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
</font></blockquote></div><br><br>