Version: (using KDE KDE 3.5.2) Installed from: SuSE RPMs Since the KGet is really tiny&handy tool it would be useful to have such option so the user could configure the KGet behaviour entirely within it.
If you let KGet open when you exit KDE, KGet will start automatically at the next KDE start. Is that not enough?
As a workaround, sure. But the explicit option is rock-solid evidence of the user preferences. Ask yourself -- the KGet was not running on KDE exit, does this _really_ mean the user doesn't want to get KGet running on the next KDE start? Those things are not related (for example I could close all apps to preserve memory while doing some complex computations) -- so the answer could be yes and no.
kget is started automatically if konqueror integration is enabled, so you only need to start it if you want to use the drop target, AFAICS. And you can also simply put it into your .kde/Autostart folder. Together with session management, these are enough options to get kget started automatically, IMHO.
Those are just workarounds. Putting scripts in .kde/Autostart is a nasty thing, because you force user to know internals of KDE.