>Yes, i should probably convert it to a CMake project Yeah then it can may be used in the clock with calendar plasmoid I am working on [1] for having events . [1] http://quickgit.kde.org/?p=kde-workspace.git&a=commit&h=e06679a09802d48c4fe0cd9375ef433ae1a89a3d
On Fri, Jul 12, 2013 at 6:29 PM, Aaron J. Seigo <ase...@kde.org> wrote: > On Friday, July 12, 2013 14:20:37 Mark wrote: > > This is also one of the questions i have, where should i put this, > > kdepim-runtime or kde-runtime? > > that entirely depends on the dependencies. > > what would be optimal is: > > * QML calendar widgetry with no akonadi integration in kde-runtime > * akonadi integration for the calendar in kdepim-runtime > > looking at the documentation on the wiki, this seems like it should be > possible. > > if it is not possible to separate out the akonadi support, then it will > need > to go into kdepim-runtime .. but you will need to check with the kdepim > developers first as they maintain those modules, not us here on > plasma-devel :) > > having apidocs along these lines: > > http://api.kde.org/4.x-api/plasma-qml-apidocs/ > > would be good; using cmake is a requirement before it can move anywhere. > > having just tried it out, the QML does need some work yet as you noted. > would > be nice to see use of Plasma QML Components for the header and buttons .. > but > it is a nice start! > > -- > Aaron J. Seigo > _______________________________________________ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > > -- -Heena Season of kde'12 participant Google Summer of Code 2013 Delhi College of Engineering(COE),India http://about.me/heena.mahour http://heenamahour.blogspot.in
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
