On Thu, 2006-10-26 at 09:58 -0400, G. Roderick Singleton wrote: > On Wed, 2006-10-25 at 16:25 +0200, Uwe Fischer wrote: > > Hi, > > > > G. Roderick Singleton wrote: > > > I have asked on dev but maybe one of our members knows. > > > > > > -------- Forwarded Message -------- > > > From: G. Roderick Singleton <[EMAIL PROTECTED]> > > > To: [email protected] > > > Subject: Re: [dev] Quickstarter quirks > > > Date: Wed, 25 Oct 2006 09:20:12 -0400 > > > > > > On Wed, 2006-10-25 at 15:08 +0200, Frank Schönheit - Sun Microsystems > > > Germany wrote: > > >> Hi Gerry, > > >> > > >>> A quick question. Why is the quickstarter enabler kept in a config > > >>> directory outside of the user's OOo stuff. > > >> I suppose that's because this is really about desktop integration: The > > >> desktop probably checks this location for things to, well, quickstart. > > >> Just a guess. > > >> > > > > > > Okay. Sounds reasonable. However, this new feature needs to be > > > documented so I am looking for confirmation that your guess is so. Can > > > someone confirm or direct me to some spec that will explain whether this > > > is *NIX specific, WM specific (e.g. Gnome vs. KDE vs. ...) or mimics > > > Windows integration? > > > > > > > this was fixed in issue > > http://www.openoffice.org/issues/show_bug.cgi?id=57872 > > Sorry, I don't know much more about this feature. > > Works almost as the Windows Quickstarter, with a config setting at the > > same place in Tools-Options. > > Big difference is that on Windows the library files are loaded on system > > startup, while on Unix systems there is an icon in the sys tray. Don't > > have any more info what happens to the lib files, whether RAM is used or > > reserved, or what else it does. May be it is only a convenient way to > > start new documents, while the Unix system cares for the memory needed > > by libraries as usual. > > > > Uwe > > I have been experimenting because no one seems to know more than we do. > So, on FC5, the following happens if you have the quickstarter enabled: > 1. On startup with no qs and the feature enabled, OOo starts > normally > 2. The qs is inserted on the task bar. > 3. only one instance of OOo in the process list > 4. exit Ooo visible window > 5. checking process list shows that the OOo process still exists > and retains the same memory footprint. > 6. re-invoking OOo is quicker because of the resident process. > > I will guess that this is the same for other unices and UNIX window > managers. Looking at the spec for Windows, > http://specs.openoffice.org/appwide/menus/desktop_menu_integration.sxw > sheds little light on the UNIX side.
Forgot to add that under FC5/Gnome, invoking OOo with the -quickstarter commandline argument doenn't work and the usage for soffice does say thin. Do not know why. -- G. Roderick Singleton <[EMAIL PROTECTED]> OpenOffice.org
smime.p7s
Description: S/MIME cryptographic signature
