Re: [dev] QuickLauncher: how to configure
Peter Eberlein wrote: Hi Mathias, Mathias Bauer schrieb: Peter Eberlein wrote: Or can it be started without appearing in the Systray? What is the point in having the QuickLauncher running but not being visible? You can achieve the same result (faster start of the first Office instance called by the user) by inserting soffice -nologo -nodefault instead of soffice -quickstart into your autostart folder. Perhaps that helps? The drawback of not having a visible quicklauncher running is that OOo will be removed from memory if all documents are closed. But if you don't wait hours for the next document it will start fast again. Yes, the goal is the fast loading of documents, even if all documents have been closed. If that shall be efficient even if meanwhile all OOo code has been swapped out of the disk cashe then you indeed need a running quicklauncher. We won't keep OOo in memory without any means to terminate it. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] QuickLauncher: how to configure
Peter Eberlein wrote: Hi, we intercepted the open/save commands because of restricted access to the file system (documents are stored in a database). Is there a way to configure the context menu of the QuickStarter and if No, it's not configurable. not: how do I deactivate it in the OptionsDialog.xcu without hiding the whole Memory page? The Single Option node oor:name=Memory oor:op=replace oor:finalized=true node oor:name=Options node oor:name=Quicklauncher or:op=replaceoor:finalized=true prop oor:name=Hide valuetrue/value /prop /node /node /node doesn't work. Or can it be started without appearing in the Systray? What is the point in having the QuickLauncher running but not being visible? You can achieve the same result (faster start of the first Office instance called by the user) by inserting soffice -nologo -nodefault instead of soffice -quickstart into your autostart folder. Perhaps that helps? The drawback of not having a visible quicklauncher running is that OOo will be removed from memory if all documents are closed. But if you don't wait hours for the next document it will start fast again. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] QuickLauncher: how to configure
Hi Mathias, Mathias Bauer schrieb: Peter Eberlein wrote: Or can it be started without appearing in the Systray? What is the point in having the QuickLauncher running but not being visible? You can achieve the same result (faster start of the first Office instance called by the user) by inserting soffice -nologo -nodefault instead of soffice -quickstart into your autostart folder. Perhaps that helps? The drawback of not having a visible quicklauncher running is that OOo will be removed from memory if all documents are closed. But if you don't wait hours for the next document it will start fast again. Yes, the goal is the fast loading of documents, even if all documents have been closed. Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
