[PATCH] bug #53345 - startkde

[Stephan Kulow]

Am Saturday 20 September 2003 01:10 schrieb Oswald Buddenhagen:
> anyway ... the kreadconfig/kde-config startup times are worrisome, imo.
> after all, these are batch tools (well, at least kreadconfig can be
> expected to be called several times in a row) - such startup times are
> simply inacceptable. i'd very much vote for implementing these tools in
> plain c (i.e., only one lib dependency) - it's not like _these_ tools
> _need_ a translation framework or something else qt/kde is needed for
> (well, one would obviously have to reimplement some kstandarddirs magic
> and a make a read-only kconfig reader, but this comes close to being
> trivial). it's rather a question of philosophy whether this _has_ to be
> done "the kde way" or some formal cleanness can be sacrified for speed
> (an order of magnitude, btw).
I think, reimplementing neither KStandardDirs nor KConfig are really
sensible in the name of startup time. I have no real idea how to fix it
though. 

For kreadconfig I think it would be pretty easy. Instead of using kconfig,
let kpersonalizer write a ~/.kde/share/apps/kpersonalizer/beenhere
file, that startkde can parse with less costs.

And for your exe paths it's propably easiest to just implement it your own
in startkde (where it really hurts). $KDEDIRS*/bin, $KDEDIR/bin and the 
@kde_bindir@ as present while installing kdebase + $KDEHOME/bin are 
the only paths really being important.

Greetings, Stephan

-- 
Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平
Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini שלום Peoch
Shanti Vrede Baris Rój Mír Taika Rongo Sulh Py'guapy 평화