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>
### Katana - Be Free and Be Efficient!
Katana is fork of KDE Software Distribution with emphasis on efficiency. So far
it has proven to be roughly 50% less system resource hungry and significantly
faster.
### Authors and Contributors
Since Katana is a fork of someone else's work, many of the credits go to the KDE
Software Development team. So far there are not much people involved in this
project but we hope that the number will increase.
Software can always be improved, and the Katana team is ready to do so.
However, you - the user - must tell us when something does not work as
expected or could be done better. You do not have to be a software developer
to be a member of the Katana team. You can join the national teams that
translate program interfaces. You can provide graphics, themes, sounds, and
improved documentation. You decide!