Anniekin wrote:Fatdog control panel is too slow!
Why does it have to load applets?
Why not just make them static links
In my opinion, since I didn't write Fatdog control panel, loading applets makes the panel extensible and customizable. For instance, the optional nvidia driver package for Fatdog-720 adds the nvidia control panel applet to Fatdog control panel.
I think the script changed a bit between Fatdog-710 and 720. In 720 applets are defined in /etc/control-panel-applets and $HOME/.fatdog/control-panel-applets, and in files inside /etc/control-panel-applets.dir and $HOME/.fatdog/control-panel-applets.dir. This is a very flexible, albeit redundant, system that probably aims at being backwards-compatible. Could it be replaced by static links? Probably, but it would be new code for an existing function that isn't broken, so the motivation to do it would be low, I think.
In my informal testing on my hardware, the applet-loading phase takes about 50% of the perceived control panel start time. That is a lot. Interaction with the control panel, once it's running, also feels slow to me. And sometimes double-clicks are lost on an applet icon.
In the past, forum members offered a couple of alternatives to the Fatdog control panel. Smokey's menu comes to mind (search the forum). If you like that kind of approach - a menu based system - you could take a look at my own script, gmenu2-fdcp in my
repo. It takes 152 msec to load the control panel applets on a Core Duo PC.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]