On Saturday 11 February 2012 20:00:01 Alexander Neundorf wrote: > kded... for what things is this needed when running only a single > application ?
The main reason currently is "so that it watches desktop files and keeps ksycoca up-to-date". The other uses of KDED are on-demand (kssl, timezones, etc.), so these are not the reason for kded being started upfront with the first KDE application. My big plan for KDE Frameworks 5 is to get rid of ksycoca, but there are many steps still to be done for that (done for mimetypes, easy todo for kprotocolinfo, see xdg list for applications, not sure yet for services/plugins, depends on what happens in Qt). > klauncher... this is quite central. I guess there is not much what could be > done... There is. It's related to kdeinit: if we don't start apps via kdeinit, then klauncher's role will be reduced to starting kioslaves, which will make it possible to have klauncher only started on-demand by the first KIO job (at which point the app is ok with multiple processes, obviously). -- David Faure, [email protected], http://www.davidfaure.fr Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5 _______________________________________________ Kde-frameworks-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
