From 7574a7287e2e121c9d5c91a5f4ea38c5b3ae2a04 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Sun, 6 Nov 2011 02:28:57 -0600 Subject: Additional kde to tde renaming --- ksmserver/README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'ksmserver/README') diff --git a/ksmserver/README b/ksmserver/README index 1c74111ae..759e57c9d 100644 --- a/ksmserver/README +++ b/ksmserver/README @@ -53,7 +53,7 @@ should be in startup.cpp and going down in that source file should follow the startup order (but note that this is just a documentation which may get outdated, so in case of doubts the source wins ;) ). -The startkde scripts already launches kdeinit, which in turns launches +The startkde scripts already launches tdeinit, which in turns launches KDE daemons like dcopserver, klauncher and kded. Kded loads autoloaded kded modules, i.e. those that have X-KDE-Kded-autoload=true in .desktop files. The exact way autoloading works is controlled by X-KDE-Kded-phase=, @@ -69,7 +69,7 @@ modules. There are three kcminit phases, 0, 1 and 2, controlled by X-KDE-Init-Phase= in the .desktop file, which defaults to 1. Phase 0 kcminit modules should be only those that really need to be run early in the startup process (and those should probably actually use kstartupconfig in startkde -to be done even before kdeinit and daemons). After executing phase 0 +to be done even before tdeinit and daemons). After executing phase 0 modules kcminit returns and waits. When ksmserver is launched, the first thing it does is launching -- cgit v1.2.1