plasma-framework/src/declarativeimports/calendar/CMakeLists.txt

set(calendar_SRCS
    calendarplugin.cpp
    #incidencemodifier.cpp
    calendar.cpp
    calendardata.cpp
    #calendardayhelper.cpp
    #calendarroleproxymodel.cpp
    #datetimerangefiltermodel.cpp
    daysmodel.cpp
    eventdatadecorator.cpp
    eventpluginsmanager.cpp
)

add_library(calendarplugin SHARED ${calendar_SRCS})

target_link_libraries(calendarplugin
    Qt5::Core
    Qt5::Quick
    Qt5::Qml
    Qt5::Gui
    KF5::I18n
    KF5::CalendarEvents
)

install(TARGETS calendarplugin DESTINATION ${KDE_INSTALL_QMLDIR}/org/kde/plasma/calendar)
install(DIRECTORY qml/ DESTINATION ${KDE_INSTALL_QMLDIR}/org/kde/plasma/calendar)
re-add the calendar qml component CCMAIL:heena393@gmail.com 2013-08-31 15:23:04 +02:00			`set(calendar_SRCS`
			`calendarplugin.cpp`
			`#incidencemodifier.cpp`
			`calendar.cpp`
			`calendardata.cpp`
			`#calendardayhelper.cpp`
			`#calendarroleproxymodel.cpp`
			`#datetimerangefiltermodel.cpp`
			`daysmodel.cpp`
[calendar] Add plugin system for Calendar events This adds a simple plugin interface that can be subclassed and provide events integration with Plasma Calendar applet. It's asynchronous and I've kept it deliberately simple. For now the Calendar tells the plugins which date range is being displayed, the plugins load the data and then emit the dataReady() signal containing the events. The events are stored in a multihash for quick access by the Calendar's agenda part but also for overall easy-to-use (eg. in teh model data()). The event data is stored in EventData class, which has a pretty self-explanatory members, except perhaps the "isMinor" property. The intention with this is to support namedays, where in some countries the calendars have different name every day. This is just a minor holiday and as such should not mark the calendar grid, otherwise the whole grid would be in a different color. Putting the interface here might raise the question of depending on plasma-framework, but plugins provided by KDE can go to plasma-workspace and other 3rd party ones would just have to live with it. I don't think it will be a problem but if it turns out it is, we can rethink the placement. REVIEW: 125817 CCBUG: 349676 CHANGELOG: Allow plugins to supply event data to Calendar applet 2015-11-02 15:33:15 -05:00			`eventdatadecorator.cpp`
[calendar] Move the plugins handling to a separate class This is also made a QML singleton that will be used for the applet config view where it will add the plugin configs once we add that possibility. The same instance is then set to the DaysModel from QML. REVIEW: 125951 2015-11-04 13:55:32 -05:00			`eventpluginsmanager.cpp`
re-add the calendar qml component CCMAIL:heena393@gmail.com 2013-08-31 15:23:04 +02:00			`)`

			`add_library(calendarplugin SHARED ${calendar_SRCS})`

			`target_link_libraries(calendarplugin`
Make sure that plasma-framework is not using anything from kdelibs4 Stop finding the packages Remove KDE4_ includes Remove unused LIBINTL finder, provided by kdelibs 2013-11-11 18:27:16 +01:00			`Qt5::Core`
			`Qt5::Quick`
			`Qt5::Qml`
Stop using Qt5Transitional in Plasma Frameworks Removes the find_package(Qt5Transitional) and does the proper find_package(Qt5) with the list of modules. Most of the porting is about using the Qt5:: targets. REVIEW: 113345 2013-10-22 00:40:17 +02:00			`Qt5::Gui`
[calendar] Add plugin system for Calendar events This adds a simple plugin interface that can be subclassed and provide events integration with Plasma Calendar applet. It's asynchronous and I've kept it deliberately simple. For now the Calendar tells the plugins which date range is being displayed, the plugins load the data and then emit the dataReady() signal containing the events. The events are stored in a multihash for quick access by the Calendar's agenda part but also for overall easy-to-use (eg. in teh model data()). The event data is stored in EventData class, which has a pretty self-explanatory members, except perhaps the "isMinor" property. The intention with this is to support namedays, where in some countries the calendars have different name every day. This is just a minor holiday and as such should not mark the calendar grid, otherwise the whole grid would be in a different color. Putting the interface here might raise the question of depending on plasma-framework, but plugins provided by KDE can go to plasma-workspace and other 3rd party ones would just have to live with it. I don't think it will be a problem but if it turns out it is, we can rethink the placement. REVIEW: 125817 CCBUG: 349676 CHANGELOG: Allow plugins to supply event data to Calendar applet 2015-11-02 15:33:15 -05:00			`KF5::I18n`
[calendar] Move the plugin library to KDeclarative Marco is not happy with the plugin being here and having a Plasma namespace, so after some discussion it was decided to move it to KDeclarative and change to CalendarEvents namespace. 2015-11-16 14:26:26 -05:00			`KF5::CalendarEvents`
re-add the calendar qml component CCMAIL:heena393@gmail.com 2013-08-31 15:23:04 +02:00			`)`

Update installation variables. 2015-01-10 17:47:31 +00:00			`install(TARGETS calendarplugin DESTINATION ${KDE_INSTALL_QMLDIR}/org/kde/plasma/calendar)`
			`install(DIRECTORY qml/ DESTINATION ${KDE_INSTALL_QMLDIR}/org/kde/plasma/calendar)`