in manual mode (when you by using mouse indicates window) kdocker succesfully kick openoffice window to tray, but through command line it did not work by default. by using kdocker or alltray.īut there is a difficulty. I suggest a real method to increase performance of OpenOffice. Need proof? Load OO with default settings for first time and measure load time. The only person with a brainsize worthy of being considered a human one. Maybe one important fact is that I don’t have Java installed for OO.
After boot it took 12 seconds to start it and all consequential startups took 6 secs. I’ve of course tried your settings and measured beaviour for a while but there was NO difference in starting times of Writer (I didn’t measured other parts of OO). In my case OO almost doesn’t touch my hard disk during consequential startups. The main reason for this is the fact that the OO binary and data are wery likely to stay cached in you operating memory. I’m afraid nobody here realized that there always will be a big difference between OO run for the first time after boot and consequential runs.