[Open Office] Internal quickstarter

[Jan Uhlir]

Hi Michael and Peter

>  Hi Jan,
> 
> 	Did you mean to CC Peter / the list ?

He is not subscribed in this mailing list? OK, I will send him a copy to be sure.

> > Well, I don't know what your experience with KDE is  - no offence 
> > please! - but KDE enables running Gnome applets for a long time.
> 
> ;-) OTOH KDE applets in Gnome suck badly; AFAIR a WM spec. violation on
> that side.

Anyway, we are the lucky ones. GTK applets runs on KDE reasonably
well, the rest is not OOo business.

> 
> > In my KDE systray are KDE as well as Gnome applets running
> > right now - Gaim and Gnome Network Monitor (it' better than KDE
> > default one, so I'm using it) 
> 
> 	Sure.
> 
> > What I want to say there is absolutely no need to do cross-desktop
> > tweaking of any file. Just make a nice Gnome applet and don't disable
> > it when KDE desktop is detected. Better not to detect running desktop 
> > environment at all. They are all freedesktop.org compatible, 
> > aren't they? ;-)
> 
> 	So - the thing is; if you want to test having Qt and Gtk+ both talking
> to X in the same process, and integrating nicely *And* take the
> performance hit from having both of those in process - that's fine;  but
> there are a ton of people out there with a rather frenzied antipathy to
> any gtk+ on KDE and VV. & I don't want to fight them :-)

Let's concentrate on GTK plugin. 
For GTK people: take it or leave it and use alternative external project.
Just not disable completely quickstarter option.


> It's easy to patch the comparison out; test it - if it works - go for
> it. Of course - more code is really required - to initialize gtk+
> correctly if it has not already been done [ for the right display etc. ]
> - and that is why we just check if gtk+ is inited already; but ... that
> code can be added: but it's work & testing & I don't have a KDE system
> & ... :-)

I will look at it.


> > I suspect, that detection of running environment was "enhanced"
> 
> Not sure; I didn't touch that code for 1.

Dates at patch files are quite new so someone did.
I will look at this.

> 
> > Well I discovered that oowriter runs ooqstarter which runs
> > soffice (shell script) which lanches soffice.bin soffice.
> > I can run soffice.bin stright away. So what is the point of this step?
> > Can I say ooqstarter to skip this step?
> 
> Sure - ooqstart however helps you *a lot* on the 2nd start - that is
> particularly nice wrt. responsiveness - it also gives you the splash
> fast.
> 
> > So my question is how to launch ooffice not to be completely 
> > released form memory when the last window is closed.
> > Without this option any external quickstarter is useles.
>
> Use the systray quickstarter ;->

Sorry I didn't get the point? I'm using systray quickstarter.

Anyway I also tried preloading "manually" using two consoles.
In one:
/usr/lib/OpenOffice.org.2/program/soffice.bin -nologo -nodefault
..to preload OOo
In the other: 
oowriter or oofice or ooqstart -writer or soffice.bin
The first lunch was well acclerated, I get times even under 1s ! Amazing!
But when I close Writer window, preloading instance was also shutted.
So with another Writer launch I got just 'usual' times because nothing 
was preloaded now.
Is this an intended behaving? 
Under such circumstances any external preloader couldn't work :( 

Anyway, I must congratulate to OOo developers team, overall statup times 
are quite good now.

1) preloaded OOo
$time -p /usr/lib/OpenOffice.org.2/program/ooqstart -writer
real 0.72 - COOL !! 

2) preloaded OOo
$time -p /usr/lib/OpenOffice.org.2/program/soffice.bin -writer -nologo
real 1.67

3) nothing preloaded, repeated ooqstart
real 4.83 - GOOD time, but repeated startup has no effect, startup times were the same, roughly around 4.6s, strange

4) nothing preloaded, repeated soffice.bin
time -p /usr/lib/OpenOffice.org.2/program/soffice.bin -writer -nologo
6.5s - 8s
time -p /usr/lib/OpenOffice.org.2/program/soffice.bin -nologo
4s - 5s
 
gcc4.0.2 vanilla, 2Ghz IBM ThinkPad, 512MB RAM