[Open Office] Internal quickstarter

[Jan Uhlir]

Thanks Michael,
you for your reply it was very helpful.

> On Sun, 2006-02-19 at 15:48 +0100, Jan Uhlir wrote:
> > I can see  option 'Load OpenOffice.org during system startup' in
> > 'Options - OpenOffice.org - Memory' but the selection is not
> > stored for a common user. When Options dialog is opened again,
> > checker is gone, not selected again. For root it is possible to
> > store it, but has no obvious effect, OOo is not started
> > as  'ps ax' revealed.
> 
> Ok - that is GNOME only; 

Why!? Is there a technical reason?
Or 'political' Gnome-related? It would be sad.
In previous milestone it worked for me fine even under KDE, so why 'remove' working functionality.

> prolly we should improve the detection of
> whether we should show that option or not.

Wold be better to enable it under KDE and other desktops too ;-)

> 
> > I discovered in programs dir ooqstart executable and library
> > libqstart_gtk680li.so There is even  ooqstart desktop file!
> > But when I tried to launch  ooqstart manually: # ooqstart
> 
> 	Ah - so this is another 'quick-starter' ;-) the 1st works by sitting
> around all the time; the 2nd is just a much more efficient factory
> worker - that is faster in both KDE & GNOME.
> 
> > ** ERROR **: Missing default argument in OOO_EXTRA_ARG
> 
> 	Don't run it directly - run it via 'oowrapper' - which should call that
> with the right environment,

I got it! I was already using it since oowriter executable is basically a simple two-line shell script calling ooqstarter with '-writer' attribute. That's all the magic :-)

> 
> > I had some positive experience with quicksater in milestone
> > 143 it speed up start significantly, but for m151 am currently
> > testing seems to be broken.
> 
> 	Nah ;-) you're just running the wrong thing.
> 
> > How this 'load during system startup' functionality is technically done?
> > Should I put 'ooqstart.desktop' to '~/.kde/Autostart'?
> 
> No - there is some pre-existing KDE quick-starter which you should
> prolly use instead; I forget the details - we ship such a thing with
> OpenSUSE I believe; best to use that I guess.

OK, I can check this. Is it in separate RPM or a part of OOo (Ooo-kde-integration)?
But I really don't mind to run GTK applet on my KDE desktop. I'm not KDE/Qt fanatic at any sence.

> 
> > So there is the internal quickstarter (ooqstart) - GTK based -
> > and the external quickstarter oooqs2 - KDE based. I suppose the
> > internal one would be more efficient then the external one. Am
> > I right?
> 
> Sure - I guess so; by a bit. What is amazing to me though, is that it
> *seems* [random user-feeling starts] that the quick-starter is slower to
> start than the ooqstart launch loading a file on double-click: which is
> odd [/end random user-feeling ;-]

Well, my experience was slightly different. There was a perceivable difference plus no splash, window quickly open in right size etc. Nothing like 200% boost, but every percent counts :)

> 
> > The runtime option -quickstart is said to be unsupported for
> > OOo2. Is that true for ooo-build patched releases too?
> 
> Yes I believe so; the whole session/lifecycle stuff wrt. the
> -quickstart stuff is really broken for OO.o itself.

What about the Windows quickstarter?  It works for m fine too?
Why this feature is possible on Windows for a long time and so problematic in Linux?

Looking forward to the reply
Jan