<div dir="ltr">I would actually remove the KDED and add a simple and multi-desktop autostart file, but there is no *good* way to manage autostart services in linux: If we install it as an autostart file in a system (root) folder and a user wants to disable it, he has to find the .desktop file in the system and remove or edit it!! and it gets even worse in a cross-desktop perspective, where you have to add flags to launch apps only in certain desktop environments.<div>
<br></div><div>So, meanwhile we do not have a proper KCM to manage autostart services (actually I feel like creating one, but I do not have time for it :( ) I would keep the KDED just to have some user interface (even though that's not the point of the KDEDs). </div>
<div class="gmail_extra"><br></div><div class="gmail_extra">In another hand, as I said before, making the dbus service launch the process if it's not running already is a good thing (and dbus supports it easily) that I think we want to have.<br>
<br><div class="gmail_quote">On Fri, Mar 7, 2014 at 8:48 AM, Yuri Samoilenko <span dir="ltr"><<a href="mailto:kinnalru@gmail.com" target="_blank">kinnalru@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>Good morning!</div><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>> I talking about possibility to start/stop/autostart. How often do you use<br>
> system services in /etc/init.d/ ? I'am using it very rare(once per week),<br>
> but i CAN stop/restart ssh, samba, dedicated virtuaboxes, apache, ntp, bind<br>
> and so on.<br>
</div>For this we can add an option into the kcm, where it will be more discoverable<br>
btw.<br></blockquote><div><br></div></div><div>I'am agreed but I can't uderstand who will start the main daemon to KCM interact with? To prevent misunderstanding: KCM module must interact with someone, whi already started - with who? And who must start this daemon?</div>
<div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div>
> What do you talking about? kdeconnect daemon consumes just about 2.5 mb of<br>
> memory. All other memory(qt/kde libraries) already shared between desktop<br>
> environment. Listening on socket to wait for incoming data/connection is<br>
> not consuming CPU, so CPU usage for kdeconnect when idle is 0.0%.<br>
> ANY plasma/QML applet consumes CPU and memory _much_ more than simple<br>
> daemon that just listen port.<br>
</div>Yeah, we have to add/remove the applet as well when no devices are connected.<br></blockquote><div><br></div></div><div>Agreed.</div><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Then let's add an option in our KCM to make things simple and usable.<br>
We did this in BlueDevil and worked quite nice.<br></blockquote><div><br></div></div><div>Again with whom KCM will interact?</div><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>
> Any dbus service consumes more CPU and memory than simple kdeconnectd<br>
> daemon.<br>
</div>This is incorrect since kdeconnectd is already a dbus service.<br></blockquote><div><br></div></div><div>Ofcourse(you can't drop dbus at all). But it start once. I mean yet another dbus daemon which will spawn "device communication instances" with dbus too. If i understand you right. If not - sorry.</div>
<div>
<div> </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div>
> To use ZERO memory user can completly disable kdeconnectd through KDED<br>
> module by just removing checkbox in systemsettings like many other KDE<br>
> services for example touchpad, remote control, nepomuk(!) and other.<br>
</div>The point is that by using the KDED we can use only a few K of private memory<br>
when no devices are connected.<br>
<br>
Remember that only the shared memory is *shared*, the private is not. In the<br>
case of Qt there is a lot of private memory for things like i18n, l10n,<br>
settings etc that it won't be shared unless you do some dirty hacks like<br>
dlopen (like we do in kdeinit).<br></blockquote><div><br></div></div><div>Ofcourse.</div><div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Depending the Qt/KDE libraries on use the private memory overhead is usually<br>
from 3 to 9Mb. Let's imagine we have an average of 6, that multiplied by the<br>
amount of KDED I have right now running, 30 produces a total memory saving of<br>
180Mb of ram.<br></blockquote><div><br></div></div><div>You tell "in general", of cource ANY application can overhead. But please tell about emmory usage of our daemon not KDED control inteface.</div><div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Anyway, I can see how this complicates things way more than what is desirable,<br>
so I'm going to give it a try and if I can't achieve it on an hour I will drop<br>
the idea.<br></blockquote><div><br></div></div><div>No problem, I hope reach success in it!</div><div><br></div><div>The my main idea is to follow UNIX way - do not make things more complex that neaded to reach the result. By "complex" I mean the number of technology, the amount of code, number of interaction within subsystems and so on. I we can drop KDED and make more universal way to control kdeconnect(ubuntu, LXDE, windows) I will happy!</div>
<div><br></div><div><br></div><div>Best regards.</div><div> </div></div></div></div>
<br>_______________________________________________<br>
KDEConnect mailing list<br>
<a href="mailto:KDEConnect@kde.org" target="_blank">KDEConnect@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kdeconnect" target="_blank">https://mail.kde.org/mailman/listinfo/kdeconnect</a><br>
<br></blockquote></div><br></div></div>