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

List:       kde-core-devel
Subject:    Re: starting apps from kicker
From:       David Faure <david () mandrakesoft ! com>
Date:       2000-05-09 17:31:09
[Download RAW message or body]

On Tue, May 09, 2000 at 01:06:12PM -0400, pbrown@redhat.com wrote:
> On Tue, 9 May 2000, Waldo Bastian wrote:
> 
> > Seems like a good candidate for "startServiceByDesktopPath( relPath + 
> > fileList[id])" ....
> 
> We really need a canonical example of how to do this in writing
> somewhere.  Right now people use any one of the following methods, and
> sometimes several in the same program!
> 
> 1. fork + exec
> 2. KProcess
> 3. KRun
> 4. startServiceByDesktopPath
> 
> the pros and cons of all of the above should be discussed, preferably by
> those who implemented them.

The first two are for executables only.

KRun is the "I can run anything". Files, executables, desktop files. Anything.

startServiceByDesktopPath can only run desktop files. KRun should be fixed
to use it, and it will be at some point, so for a desktop file, using KRun
or startServiceByDesktopPath will do just the same
(i.e. take advantage of kdeinit).

> I think the list is also ordered by implementation age.  Comments?

Yes. Can we stop getting complaints from you and rather see some fixes to kicker ?
I'm pretty annoyed that KOffice doesn't even show up in my menu simply because
I have a KEdit.kdelnk in ~/.kde/share/applnk/Applications.

> This is really important.  I for one don't really understand what KRun and
> startServiceByDesktopPath truly offer over KProcess.
Read the docs.

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today
See http://www.kde.org/kde1-and-kde2.html for how to set up KDE 2

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