kde-workspace/soliduiserver/actions/CMakeLists.txt

install(
    FILES
    openinwindow.desktop
    unmountdevice.desktop
    DESTINATION ${KDE4_DATA_INSTALL_DIR}/solid/actions
)
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(`
soliduiserver: implement mountpoint cleaner lots of references have to be kept and passed around because once the device is removed Solid::Device is just an UDI - anything else is obtained dynamically and will return invalid results (even casts will not work) what the mountpoint cleaner does? when a device is removed without being unmounted (e.g. USB storage) the program will call `unmount` essentially making sure the device node and the mount point can be used when the device is inserted again, no other project does that as far as I am aware Signed-off-by: Ivailo Monev <xakepa10@gmail.com> 2023-09-09 10:56:55 +03:00			`FILES`
			`openinwindow.desktop`
			`unmountdevice.desktop`
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			`DESTINATION ${KDE4_DATA_INSTALL_DIR}/solid/actions`
			`)`