[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: kdeinit
From:       David Faure <david () mandrakesoft ! com>
Date:       2000-04-05 10:42:37
[Download RAW message or body]

On Wed, Apr 05, 2000 at 01:05:37PM +0200, Simon Hausmann wrote:
> 
> 
> On Wed, 5 Apr 2000, David Faure wrote:
> 
> > > I did some little testing and changed Makefile.am to put all code into
> > > libkonqueror (including main() ) and copied libkonqueror.so to
> > > konqueror.so in my $prefix/lib . That made kdeinit dlopen konqueror.so
> > > (instead of exec'ing konqueror) .
> > Didn't you have to change konqueror.desktop too ?
> > (I thought you had to specify the libname there - unless perhaps kdeinit
> > figures it out from the app name).
> 
> AFAIK kdeinit tries to load app_name.la and falls back on
> exec( app_name ) if that fails.

Yup, thought so.

> > > It might be easily possible that I got the wrong impression, but for me it
> > > made the startup approx. 2/3 seconds faster.
> > > 
> > > Could that be possible?
> > 
> > Definitely. Loading all those shared libs takes time, and kdeinit 
> > frees you from that. Commit :)
> 
> There's one problem left:
> KLauncher uses the Exec field to determine the service's command. This is
> passed over to kdeinit.
> 
> That means we cannot launch libkonqueror, and changing the Exec= entry in
> konqueror.desktop to libkonqueror seems wrong, or? ;-)
> 
> (and we cannot rename libkonqueror to konqueror in Makefile.am, as the
> "builtin" views link against libkonqueror (and specifiying konqueror.la
> instead of libkonqueror.la makes libtool bail out)

hihi - stupid naming problem, heh ? :)

> Possible solutions:
> 
> 1) Add a second konqueror.desktop (different name) , with
> Exec=libkonqueror
> 
> 2) Hack kinit to also look for appname.la and libappname.la when trying to
>    dlopen the service.

3) Define a konqueror.so which includes main and links to libkonqueror.so

This is how kdeinit currently intends to find shared libs: they have to
be the same as the app and to include everything the app includes,
but we want libkonqueror.so as a normal shared lib too, so it can't
be the same file. You probably don't want to put a symbol called
main in a real shared lib (one that apps could link against)...

> > And speaking about konqueror startup time:
> > it starts the cookiejar on startup. Shouldn't we do that only when
> > the HTML view is loaded for the first time ? I surely don't need
> > a cookie jar for browsing my local drive !
> > Perhaps putting that in KHTMLFactory (whatever it's called) is the answer ?
> 
> I 100% agree. Perhaps even kio_http should try to launch kcookiejar
> itself?
Hmm, are cookies HTTP or HTML specific ?
I'd say HTML, but OTOH we don't want cookies in an HTML mail, as
somebody pointed out... :)

> Waldo? :-)
I hope he's reading this list again already, but I'm not sure
- recently he told me he was still settling in his new location...

-- 
David FAURE
david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today

[prev in list] [next in list] [prev in thread] [next in thread]