Description: konqlaunch is a small shell script which uses kdialog to allow a user to select a konqueror profile, followed by a URL before launching the program. Profiles are read from the user's kde directory (still need to add system profiles).
I wrote this application for several reasons: * I am learning how to use the scripting interfaces to KDE * I think it is a good concept for konqueror since selecting a starting profile is very awkward at the current time * I wanted to provide a nice demonstration program for using kdialogLast changelog:
version 0.1 - initial release
version 0.2 ----------- * cleaned up the find command * reduced some of the scripting code
version 0.3 ----------- * added system profiles * will not error if missing user profiles directory * cleaned up some of the scripting
It appears the the --profiles flag is only in KDE 3.2 and therefore I cannot use it or test for it since I don't yet have KDE 3.2. I am actually going to update the script to use the system profiles and not to fail if the user profiles directory does not exist.
Please send me your version of the konqlaunch using the profiles and I will check for KDE version and merge it in there.
I also cleaned up the code some in the new version, fixed some bugs regarding passing of directory.
Had nothing better to do, so went ahead and modified the script again to create a desktop link. Pretty simple actually. Anyhow, tell me if you want it, and I'll email it to you.
I just hacked your script to use konqueror --profiles instead of the other setup. If I have enough time, I might also work on getting it to create a .desktop link as well. Anyhow, let me know if you want the modified version, and I'll email it to you or something.
~/.kde/share/apps/konqueror/profiles doesn't exist on my system, and therefore the script has subsequent problems. What if you just had the script run "konqueror --profiles"? Just save the results to a file as in "konqueror --profiles > /tmp/profilelist". This would resolve the prob on my distro (Mandrake 10 Beta 2), and should everywhere else.
Also, although I understand this is a learning project, I don't quite see the practical benefit. I think most people would prefer to simply click/double-click a link on their desktop or kmenu, rather than run a shell script where the run through options. If a person isn't savy enough to define their own link, I could see this script being used to define one for them (i.e have the script generate a .desktop file for them). Other than that, I don't think most users want to sift through a dialog every time they want to use Konqueror.
Ratings & Comments
5 Comments
It appears the the --profiles flag is only in KDE 3.2 and therefore I cannot use it or test for it since I don't yet have KDE 3.2. I am actually going to update the script to use the system profiles and not to fail if the user profiles directory does not exist. Please send me your version of the konqlaunch using the profiles and I will check for KDE version and merge it in there. I also cleaned up the code some in the new version, fixed some bugs regarding passing of directory.
Had nothing better to do, so went ahead and modified the script again to create a desktop link. Pretty simple actually. Anyhow, tell me if you want it, and I'll email it to you.
could you please send me your script that you modified for konqlaunch. I want to try it out. ayudame@linuxmail.org
I just hacked your script to use konqueror --profiles instead of the other setup. If I have enough time, I might also work on getting it to create a .desktop link as well. Anyhow, let me know if you want the modified version, and I'll email it to you or something.
~/.kde/share/apps/konqueror/profiles doesn't exist on my system, and therefore the script has subsequent problems. What if you just had the script run "konqueror --profiles"? Just save the results to a file as in "konqueror --profiles > /tmp/profilelist". This would resolve the prob on my distro (Mandrake 10 Beta 2), and should everywhere else. Also, although I understand this is a learning project, I don't quite see the practical benefit. I think most people would prefer to simply click/double-click a link on their desktop or kmenu, rather than run a shell script where the run through options. If a person isn't savy enough to define their own link, I could see this script being used to define one for them (i.e have the script generate a .desktop file for them). Other than that, I don't think most users want to sift through a dialog every time they want to use Konqueror.