Katana_mirror/kde-workspace
1
0
Fork 0
mirror of https://bitbucket.org/smil3y/kde-workspace.git synced 2025-02-23 10:22:49 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
kde-workspace/soliduiserver/soliduiserver.h

58 lines
1.8 KiB
C
Raw Permalink Normal View History

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
/* This file is part of the KDE project
Copyright (C) 2021 Ivailo Monev <xakepa10@gmail.com>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public
License version 2, as published by the Free Software Foundation.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Library General Public License for more details.
You should have received a copy of the GNU Library General Public License
along with this library; see the file COPYING.LIB. If not, write to
the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
Boston, MA 02110-1301, USA.
imported everything from kde-runtime
2014-11-15 04:16:00 +02:00
*/
#ifndef SOLIDUISERVER_H
#define SOLIDUISERVER_H
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
#include "soliduidialog.h"
imported everything from kde-runtime
2014-11-15 04:16:00 +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
#include <kdedmodule.h>
#include <solid/device.h>
imported everything from kde-runtime
2014-11-15 04:16:00 +02:00
class SolidUiServer : public KDEDModule
{
Q_OBJECT
Q_CLASSINFO("D-Bus Interface", "org.kde.SolidUiServer")
public:
SolidUiServer(QObject* parent, const QList<QVariant>&);
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
~SolidUiServer();
imported everything from kde-runtime
2014-11-15 04:16:00 +02:00
public Q_SLOTS:
soliduiserver: implement methods to mount/unmount devices that are not Solid UDI and adjust to KAutoMount changes this goes with 986a303ff6b8e179aadc85468abcae448711a108 in kdelibs repo Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
2023-06-15 22:11:22 +03:00
Q_SCRIPTABLE int mountDevice(const QString &device, const QString &mountpoint, bool readonly = false);
Q_SCRIPTABLE int unmountDevice(const QString &mountpoint);
Q_SCRIPTABLE int mountUdi(const QString &udi);
Q_SCRIPTABLE int unmountUdi(const QString &udi);
imported everything from kde-runtime
2014-11-15 04:16:00 +02:00
soliduiserver: implement error string getter Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
2023-06-18 01:08:26 +03:00
Q_SCRIPTABLE QString errorString(const int error);
imported everything from kde-runtime
2014-11-15 04:16:00 +02:00
private Q_SLOTS:
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
void slotDeviceAdded(const QString &udi);
void slotDeviceRemoved(const QString &udi);
void slotDialogFinished();
imported everything from kde-runtime
2014-11-15 04:16:00 +02:00
private:
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
void handleActions(const Solid::Device &soliddevice, const bool added);
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
SolidUiActions m_solidactions;
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
QList<SolidUiDialog*> m_soliddialogs;
imported everything from kde-runtime
2014-11-15 04:16:00 +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
#endif // SOLIDUISERVER_H
Reference in a new issue Copy permalink