On Wednesday, April 24, 2013 11:37:43 PM Albert Astals Cid wrote:
> > It appears that the imports I mentioned before provide i18n and access to
> > KIcons, so why would I choose KDeclarative over that? KTouch uses QML, but
> > appears (from what I've seen so far) to only use imports from Plasma, and
> > doesn't use KDeclarative at all.
>
> What do you mean KTouch doesn't use KDeclarative. What's this then?
>
> kdeunstable@xps:~/ktouch:master$ wcgrep -i kdeclarative
> ./src/application.cpp:26:#include <kdeclarative.h>
> ./src/application.cpp:80: KDeclarative kDeclarative;
> ./src/application.cpp:81:
> kDeclarative.setDeclarativeEngine(declarativeEngine);
> ./src/application.cpp:82: kDeclarative.initialize();
> ./src/application.cpp:83: kDeclarative.setupBindings();
> ./src/application.cpp:85: QScriptEngine* engine =
> kDeclarative.scriptEngine();
> ./src/CMakeLists.txt:5:find_package(KDeclarative REQUIRED)
> ./src/CMakeLists.txt:112:target_link_libraries(ktouch
> ${KDECLARATIVE_LIBRARIES} ${KDE4_PLASMA_LIBS} ${KDE4_KIO_LIBS}
> ${KDE4_KCMUTILS_LIBS} ${QT_QTCORE_LIBRARY} ${QT_QTOPENGL_LIBRARY}
> ${QT_QTSCRIPT_LIBRARY} ${QT_QTDECLARATIVE_LIBRARY}
> ${QT_QTXMLPATTERNS_LIBRARY} ${QT_QTSQL_LIBRARY})
> ./src/graph-plugin/CMakeLists.txt:17:target_link_libraries(graphplugin
> ${KDE4_PLASMA_LIBS} ${QT_QTSCRIPT_LIBRARY} ${QT_QTDECLARATIVE_LIBRARY}
> ${KDECLARATIVE_LIBRARIES})
Sorry, I missed that because I was only looking in mainwindow.cpp, where the
view was created, and didn't see that it called code the in the main
application to initialize kdeclarative.
Thanks for the help, I think I know enough now to be able to learn from
KTouch, since it uses kdeclarative and plasma code.
--
Michael Spencer
https://iBeliever.github.io
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
