[Development] QML engine C++ class renaming
Stephen Kelly
stephen.kelly at kdab.com
Thu Feb 16 13:42:06 CET 2012
On Thursday, February 16, 2012 09:26:57 you wrote:
> Having lot of QObject classes is ok, that would still work.
>
> I was talking about sublclasses of QDeclarativeItem. I looked in
> kde-baseapps kdeedu kdegraphics kdelibs kdepim kdepimlibs
> kdepim-runtime kdeplasma-addons kde-runtime kdeutils kde-workspace
> and there are 14 classes inheriting from QDeclarativeItem.
mostly in kdepim right for kontact-touch? You don't find much else in the rest
for the simple reason that not many kde apps were ported or created to use
QML. I'm sure porting kontact touch to QML2 would be more than just porting
those classes. There is stuff in there like use of QGraphicsProxyWidget.
> I believe
> quite a lot could use the non optimal QQuickPaintedItem to be ported
> quickly.
I have no idea. We should know in a few weeks when we should be able to do an
experimental port of kdepim to Qt5.
Thanks,
--
Stephen Kelly <stephen.kelly at kdab.com> | Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090
KDAB - Qt Experts - Platform-Independent Software Solutions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120216/83952a99/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120216/83952a99/attachment.sig>
More information about the Development
mailing list