Description: Prelaunch is a utility for the Linux desktop which significantly decrease the time needed to launch programs. Prelaunch start the respective program during login, invisible to the user. With this trick the real launch needs no time. During session it is always a new instance ready to show
Hello I recently complied prelaunch v0.05 on my Debian Sid with KDE4 from Debian's Experimental branch, and was able to successfully add apps.
One bug seems to be that I cannot give the full path for the app I want, like:
$ prelaunch-add /usr/bin/iceweasel
because that then tries to create the file:
~/.prelaunch//usr/bin/iceweasel
and that fails. With just using 'iceweasel' the file gets created properly and things seem to work, sorta...
But my main question is, nothing happens once I adjust my icons to launch the new prelauncher script/binary/whatever, and I click my icon. I have to click my icon 2 or even 4 times to get an app to launch, and when it does I get 2 or 3 instances of Iceweasel on the screen at once. I am accustomed to clicking things once, being KDE and all, and I'd prefer to not have a lot start at once.
Any tips or suggestions? Thanks for the app, it looks like it will be useful if I can get it going properly, since I am tired of Firefox (Iceweasel) taking so long to launch.
Am I doing something wrong?
try this:
prelaunch -r application
prelaunch /usr/bin/application --autostart
prelaunch /usr/bin/application
if this is working, the problem is related to missing ~/.prelaunch in PATH or
enabled session managemnt. i will try it out to night.
so tested:
quanta: work, but open some window on startup (do not know to disable it,
make sure splash window is disabled)
kile: does not work, cause it is not possible to disable the splash window
Is there really a point in writing a "KDE enabled" accessory in C / Gtk?
I'm not dead against Gtk, I use a few Gtk applications myself (like Streamtuner and Grip), but I'm not sure I would like it as a part of the system framework.
Note: I haven't tried prelaunch, so maybe I'm totally off...
it is not a KDE app. it has KDE support
(automatic system installation/preparation)
without this support you need to do this by hand (PATH settings, scripts...)
Ratings & Comments
8 Comments
Hello I recently complied prelaunch v0.05 on my Debian Sid with KDE4 from Debian's Experimental branch, and was able to successfully add apps. One bug seems to be that I cannot give the full path for the app I want, like: $ prelaunch-add /usr/bin/iceweasel because that then tries to create the file: ~/.prelaunch//usr/bin/iceweasel and that fails. With just using 'iceweasel' the file gets created properly and things seem to work, sorta... But my main question is, nothing happens once I adjust my icons to launch the new prelauncher script/binary/whatever, and I click my icon. I have to click my icon 2 or even 4 times to get an app to launch, and when it does I get 2 or 3 instances of Iceweasel on the screen at once. I am accustomed to clicking things once, being KDE and all, and I'd prefer to not have a lot start at once. Any tips or suggestions? Thanks for the app, it looks like it will be useful if I can get it going properly, since I am tired of Firefox (Iceweasel) taking so long to launch. Am I doing something wrong?
I will try that. It was not just the splash screen but the whole app launched.
When I logged out and back in the applications I added, Quanta and Kile both started up and appeared on my screen. I used %prelaunch-add "application"
try this: prelaunch -r application prelaunch /usr/bin/application --autostart prelaunch /usr/bin/application if this is working, the problem is related to missing ~/.prelaunch in PATH or enabled session managemnt. i will try it out to night.
so tested: quanta: work, but open some window on startup (do not know to disable it, make sure splash window is disabled) kile: does not work, cause it is not possible to disable the splash window
Is there really a point in writing a "KDE enabled" accessory in C / Gtk? I'm not dead against Gtk, I use a few Gtk applications myself (like Streamtuner and Grip), but I'm not sure I would like it as a part of the system framework. Note: I haven't tried prelaunch, so maybe I'm totally off...
I totally agree with with you. It doesn't really make sense to make KDE (or a KDE program) depend on gtk.
it is not a KDE app. it has KDE support (automatic system installation/preparation) without this support you need to do this by hand (PATH settings, scripts...)