kde-workspace/plasma/applets/devicenotifier/CMakeLists.txt

project(plasma-applet-devicenotifier)

set(devicenotifier_SRCS
    devicenotifier.cpp
)

kde4_add_plugin(plasma_applet_devicenotifier ${devicenotifier_SRCS})
target_link_libraries(plasma_applet_devicenotifier
    KDE4::plasma
    KDE4::solid
    KDE4::kio
)

install(
    TARGETS plasma_applet_devicenotifier
    DESTINATION ${KDE4_PLUGIN_INSTALL_DIR}
)

install(
    FILES plasma-applet-devicenotifier.desktop
    DESTINATION ${KDE4_SERVICES_INSTALL_DIR}
)
generic: device notification reimplementation how does it look? something like this: https://ibb.co/1zbDVpk and because all the SolidUiServer bits are written by me now - copyright it to me. the actions dialog was not operational btw (not for hotplug events anyway). the solidautoeject thing does not even make sense - when the eject button is pressed it was calling Solid::OpticalDrive::eject() but if the button is pressed the tray will eject anyway so what was it doing actually? solid-device-automounter can be replaced with solid actions but the devices are mounted for solid actions anyway so dropping it as for KCM for the solid actions - there can be none but to add features such as non-interactive actions (e.g. launch the keyboard KCM when a keyboard is plugged without poping dialog) or actions that do something on device removal it has to be done anew note that the action file for opening a file manager was named "test-predicate-openinwindow" meaning it was a testing thing rather than a finished thing Signed-off-by: Ivailo Monev <xakepa10@gmail.com> 2023-09-06 23:50:46 +03:00			`project(plasma-applet-devicenotifier)`
initial import 2014-11-13 19:30:51 +02:00
generic: device notification reimplementation how does it look? something like this: https://ibb.co/1zbDVpk and because all the SolidUiServer bits are written by me now - copyright it to me. the actions dialog was not operational btw (not for hotplug events anyway). the solidautoeject thing does not even make sense - when the eject button is pressed it was calling Solid::OpticalDrive::eject() but if the button is pressed the tray will eject anyway so what was it doing actually? solid-device-automounter can be replaced with solid actions but the devices are mounted for solid actions anyway so dropping it as for KCM for the solid actions - there can be none but to add features such as non-interactive actions (e.g. launch the keyboard KCM when a keyboard is plugged without poping dialog) or actions that do something on device removal it has to be done anew note that the action file for opening a file manager was named "test-predicate-openinwindow" meaning it was a testing thing rather than a finished thing Signed-off-by: Ivailo Monev <xakepa10@gmail.com> 2023-09-06 23:50:46 +03:00			`set(devicenotifier_SRCS`
			`devicenotifier.cpp`
			`)`
initial import 2014-11-13 19:30:51 +02:00
generic: device notification reimplementation how does it look? something like this: https://ibb.co/1zbDVpk and because all the SolidUiServer bits are written by me now - copyright it to me. the actions dialog was not operational btw (not for hotplug events anyway). the solidautoeject thing does not even make sense - when the eject button is pressed it was calling Solid::OpticalDrive::eject() but if the button is pressed the tray will eject anyway so what was it doing actually? solid-device-automounter can be replaced with solid actions but the devices are mounted for solid actions anyway so dropping it as for KCM for the solid actions - there can be none but to add features such as non-interactive actions (e.g. launch the keyboard KCM when a keyboard is plugged without poping dialog) or actions that do something on device removal it has to be done anew note that the action file for opening a file manager was named "test-predicate-openinwindow" meaning it was a testing thing rather than a finished thing Signed-off-by: Ivailo Monev <xakepa10@gmail.com> 2023-09-06 23:50:46 +03:00			`kde4_add_plugin(plasma_applet_devicenotifier ${devicenotifier_SRCS})`
			`target_link_libraries(plasma_applet_devicenotifier`
			`KDE4::plasma`
			`KDE4::solid`
			`KDE4::kio`
			`)`
initial import 2014-11-13 19:30:51 +02:00
generic: device notification reimplementation how does it look? something like this: https://ibb.co/1zbDVpk and because all the SolidUiServer bits are written by me now - copyright it to me. the actions dialog was not operational btw (not for hotplug events anyway). the solidautoeject thing does not even make sense - when the eject button is pressed it was calling Solid::OpticalDrive::eject() but if the button is pressed the tray will eject anyway so what was it doing actually? solid-device-automounter can be replaced with solid actions but the devices are mounted for solid actions anyway so dropping it as for KCM for the solid actions - there can be none but to add features such as non-interactive actions (e.g. launch the keyboard KCM when a keyboard is plugged without poping dialog) or actions that do something on device removal it has to be done anew note that the action file for opening a file manager was named "test-predicate-openinwindow" meaning it was a testing thing rather than a finished thing Signed-off-by: Ivailo Monev <xakepa10@gmail.com> 2023-09-06 23:50:46 +03:00			`install(`
			`TARGETS plasma_applet_devicenotifier`
			`DESTINATION ${KDE4_PLUGIN_INSTALL_DIR}`
			`)`

			`install(`
			`FILES plasma-applet-devicenotifier.desktop`
			`DESTINATION ${KDE4_SERVICES_INSTALL_DIR}`
			`)`