Description: i think that kdesktop should be merged with konqueror, like nautilus. nautilus has a much faster startup time (from when you double click on an icon i mean) than konqueror, and this is mainly because gnome's background *is* nautilus so it's already running. if konqueror handled the desktop icons as well, then it's startup time would be shorter. just my 2c.Last changelog:
Though I agree with most that the Windows-like behaviour of using one application (Explorer) for everything is daft. First, it goes completely against the UN*X-ish view of using many small, well-written, stable, and virtually-bug-free applications to accomplish larger goals (i.e. tar to group files, gzip to compress, together to archive), and it also creates a single breaking point - as Windows often clearly demonstrates.
However, I do approve of using a background instance of an application to spawn new instances quickly. If the master process goes down, the children (hopefully) shouldn't, and a new master process should get launched. If this feature is already available in KDE 3.2, I truly can't wait for the release or addition of KDE-CVS to Gentoo's Portage tree. (Yeah, yeah, I'm too lazy to do the CVS/compile myself. ;-P)
[rant] To those that simply say "no" to ideas... you have issues. KDE and Linux are all about options. Options are optional. You can simply decline to use it, but IMHO all ideas that are requested should eventually be added. There is no reason not to (well, with the possible exception of time and effort, but that's different). If one person wants it, there are likely many who don't know they want it yet, but would use it if it was there. ;-) [/rant]
well the startup times for most applications in kde has to do with how uses the shared liberaries.
what you can do to dramatically speed up your start up times is to prelink: http://www.gentoo.org/doc/en/prelink-howto.xml I cut my startup times from maybe 2 sec to about 0.5 sec ;-)
good luck
Actually, In KDE CVS there is already an option called "Konqueror preloading", where you set a number of konqueror processes that always remain in memory.
I've tried it, and it makes konqueror start instantly. Also, for those who don't want it, it can be diabled entirely (which is the default.)
And what do you do of those who use konqueror without KDE?
And I even heard of someone who used kdesktop alone with icewm (or another lightweight wm, not sure).
There's an option in KDE (kcontrol -> components -> file manager -> behavior -> minimize memory usage), which does this.
When you enable this options konqueror willl try to reuse an existing konqueror instance.
So what I do is starting a "konqueror --silent" instance (this is a konqueror instance without a main window, daemon like)when KDE starts, and whenever I try to start a fresh version of konqueror, it will be spawned from the instance already running, which is very fast.
The problems with doing this are:
1: whenever a konqueror program crashes, they all do, because they are using the same memory.
2: when the above has happened you would have to start a new "konqueror --silent".
So there should really be a daemon running in the background, that know's when konqueror has crashed, and starts a fresh background konqueror when that has happened.
This shouldn't be to hard to make, KDE knows when one of its program has crashed (it catches the SIGSEGV signal) and starts that KBug thingy.
Interesting... I am using Mdk 9.1 rc2 and by default kdeinit: konq --silent seems to be running by default!
I see a BIG difference in konq startup time between mdk-8.2 + kde 3.0 and mdk-9.1 + kde 3.1
Don't do this.
Lot's of people use konqueror out of KDE (WindowMaker, FluxBox,...) and they don't need kdesktop.
Nautilus manage the desktop and I HATE this ! When Nautilus crash, all my desktop crash :( When I want to use both Gnome and KDE I can't start Nautilus in KDE or it crash kdesktop. I can unactivate it but I want it on Gnome.
Really, really bad idea
Please do not do this!
This is the worst idea in a long time.
1. I've only got 128 MB in my computer
which is not much considering today's
RAM prices and Konqueror is
starting within 3 seconds.
2. If that's not enough you can just
leave it open over the day and put
it on a seperate desktop if
necessary
If Konqueror crashes the whole desktop
will go with it. It's always annoying
when in Windows i.e the Internet Explorer
crashes and suddenly you have got no
task bar. IMO the desktop is very important
and should always be there even when
a program crashes. If Konqueror
took a minute to start up I might
understand this. There are certainly
better ways to improve the start up
perfomance of an application. If
people are not clever enough to just
leave the application open there might
be an option to make it just invisible
on close instead of really closing it.
thats some of the reasons I hated gnome ... they did a windows mistake
IE is used for desktop, panel and file/web browser .. 1 thing goes down so does 1/2 the system
I was thinking the same... that way any directories/links to other folders would just spring up open, by perhaps forking an existing process.
But what if you have a konq-home icon in the kicker for easy access? In that case you would be starting a new process - not much advantage there.
If I don't remember incorrectly, in KDE 3.2, an instance of konq will remain running in the background, so the problem is solved!
>in that case you would be starting a new >process - not much advantage there.
They already have this working in noatun (the option 'only start one instance'). I thought all that stuff was handled by dcop?
this is agood suggestion, but it is in the wrong place. Your post does not use good english, you have no screenshots, detailed explanation, or even knowledge if this is possible and how it would work.
This should not be posted after so little research, or if posted it should go in the forum.
[sarcasm]yeah... kill all those people who have ideas and lack the knowledge of if it is possible.. oh and not to forget, all those people who can't write in Oxfort-English... kill em![/sarcasm]
Man, there's someone, who has an idea, that might be good (i don't know, i'm not a coder or kde-superhero). And all you do is flame him for putting it in the (perhaps) wrong place.
Thanks a lot
Uh, that can't be good... english is my 'first' language.
hey, it was just a suggestion. konqueror takes about 4.5 seconds to start (compared to windows explorer, which takes about 1/2 a second) whan all i want to do is copy some files.
Me Agree. Peeple wit no good english should be bommed. We only ally with no-subliminimilal peeple dat speek hour lengwitch. The others , espesially de oanz wid oil shoul be exterminayted coss we dunt understand them.
GWB, the global threat factor.
************************
Sorry I could not help myself.
About the idea: Sounds ok to me but I have a konq window running hidden in the background all the the time. I start up additional konqueror with a URL pointing to $HOME. This lets Konqueror open windows in 0.5 sec on my duron 800.
Ratings & Comments
18 Comments
Though I agree with most that the Windows-like behaviour of using one application (Explorer) for everything is daft. First, it goes completely against the UN*X-ish view of using many small, well-written, stable, and virtually-bug-free applications to accomplish larger goals (i.e. tar to group files, gzip to compress, together to archive), and it also creates a single breaking point - as Windows often clearly demonstrates. However, I do approve of using a background instance of an application to spawn new instances quickly. If the master process goes down, the children (hopefully) shouldn't, and a new master process should get launched. If this feature is already available in KDE 3.2, I truly can't wait for the release or addition of KDE-CVS to Gentoo's Portage tree. (Yeah, yeah, I'm too lazy to do the CVS/compile myself. ;-P) [rant]
To those that simply say "no" to ideas... you have issues. KDE and Linux are all about options. Options are optional. You can simply decline to use it, but IMHO all ideas that are requested should eventually be added. There is no reason not to (well, with the possible exception of time and effort, but that's different). If one person wants it, there are likely many who don't know they want it yet, but would use it if it was there. ;-)
[/rant]
well the startup times for most applications in kde has to do with how uses the shared liberaries. what you can do to dramatically speed up your start up times is to prelink: http://www.gentoo.org/doc/en/prelink-howto.xml I cut my startup times from maybe 2 sec to about 0.5 sec ;-) good luck
Actually, In KDE CVS there is already an option called "Konqueror preloading", where you set a number of konqueror processes that always remain in memory. I've tried it, and it makes konqueror start instantly. Also, for those who don't want it, it can be diabled entirely (which is the default.)
And what do you do of those who use konqueror without KDE? And I even heard of someone who used kdesktop alone with icewm (or another lightweight wm, not sure).
First thing I do when I've emerged Gnome is switch off Nautilus.
There's an option in KDE (kcontrol -> components -> file manager -> behavior -> minimize memory usage), which does this. When you enable this options konqueror willl try to reuse an existing konqueror instance. So what I do is starting a "konqueror --silent" instance (this is a konqueror instance without a main window, daemon like)when KDE starts, and whenever I try to start a fresh version of konqueror, it will be spawned from the instance already running, which is very fast. The problems with doing this are: 1: whenever a konqueror program crashes, they all do, because they are using the same memory. 2: when the above has happened you would have to start a new "konqueror --silent". So there should really be a daemon running in the background, that know's when konqueror has crashed, and starts a fresh background konqueror when that has happened. This shouldn't be to hard to make, KDE knows when one of its program has crashed (it catches the SIGSEGV signal) and starts that KBug thingy.
Why don't you write a shell script that is restarting konqueror --silent after a crash? #!/bin/sh while true; do konqueror --silent done
Interesting... I am using Mdk 9.1 rc2 and by default kdeinit: konq --silent seems to be running by default! I see a BIG difference in konq startup time between mdk-8.2 + kde 3.0 and mdk-9.1 + kde 3.1
Don't do this. Lot's of people use konqueror out of KDE (WindowMaker, FluxBox,...) and they don't need kdesktop. Nautilus manage the desktop and I HATE this ! When Nautilus crash, all my desktop crash :( When I want to use both Gnome and KDE I can't start Nautilus in KDE or it crash kdesktop. I can unactivate it but I want it on Gnome. Really, really bad idea
Please do not do this! This is the worst idea in a long time. 1. I've only got 128 MB in my computer which is not much considering today's RAM prices and Konqueror is starting within 3 seconds. 2. If that's not enough you can just leave it open over the day and put it on a seperate desktop if necessary If Konqueror crashes the whole desktop will go with it. It's always annoying when in Windows i.e the Internet Explorer crashes and suddenly you have got no task bar. IMO the desktop is very important and should always be there even when a program crashes. If Konqueror took a minute to start up I might understand this. There are certainly better ways to improve the start up perfomance of an application. If people are not clever enough to just leave the application open there might be an option to make it just invisible on close instead of really closing it.
thats some of the reasons I hated gnome ... they did a windows mistake IE is used for desktop, panel and file/web browser .. 1 thing goes down so does 1/2 the system
I was thinking the same... that way any directories/links to other folders would just spring up open, by perhaps forking an existing process. But what if you have a konq-home icon in the kicker for easy access? In that case you would be starting a new process - not much advantage there. If I don't remember incorrectly, in KDE 3.2, an instance of konq will remain running in the background, so the problem is solved!
>in that case you would be starting a new >process - not much advantage there. They already have this working in noatun (the option 'only start one instance'). I thought all that stuff was handled by dcop?
this is agood suggestion, but it is in the wrong place. Your post does not use good english, you have no screenshots, detailed explanation, or even knowledge if this is possible and how it would work. This should not be posted after so little research, or if posted it should go in the forum.
[sarcasm]yeah... kill all those people who have ideas and lack the knowledge of if it is possible.. oh and not to forget, all those people who can't write in Oxfort-English... kill em![/sarcasm] Man, there's someone, who has an idea, that might be good (i don't know, i'm not a coder or kde-superhero). And all you do is flame him for putting it in the (perhaps) wrong place. Thanks a lot
You misspelled "Oxford". :P
Uh, that can't be good... english is my 'first' language. hey, it was just a suggestion. konqueror takes about 4.5 seconds to start (compared to windows explorer, which takes about 1/2 a second) whan all i want to do is copy some files.
Me Agree. Peeple wit no good english should be bommed. We only ally with no-subliminimilal peeple dat speek hour lengwitch. The others , espesially de oanz wid oil shoul be exterminayted coss we dunt understand them. GWB, the global threat factor. ************************ Sorry I could not help myself. About the idea: Sounds ok to me but I have a konq window running hidden in the background all the the time. I start up additional konqueror with a URL pointing to $HOME. This lets Konqueror open windows in 0.5 sec on my duron 800.