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

List:       kde-devel
Subject:    Re: unknown .kdelnk field
From:       Andreas Pour <pour () mieterra ! com>
Date:       1999-05-05 16:23:26
[Download RAW message or body]

David Faure wrote:

> On Wed, May 05, 1999 at 10:58:07AM +0200, Stefan Taferner wrote:
> > On Tue, 04 May 1999, David Faure wrote:
> > > On Tue, May 04, 1999 at 01:52:54PM -0400, pbrown@redhat.com wrote:
> > > > On Tue, 4 May 1999, David Faure wrote:
> > > >
> > > > > But it allows to enter several entries ("netscape", "Netscape",
> > > > > "Communicator" (?), whatever), because it's handled like a mimetype.
> > > > > I think this is wrong.
> > > > > Let's rename this field to simply "Application", allow a single entry in
> > > > > it, and we're done.
> > > > >
> > > > > Did I miss something ?
> > > >
> > > > I don't think so.  Makes sense to me.  However, Application is still a
> > > > misleading name.  Let's call it AppBinary?
> > >
> > > To me binary looks like 0 and 1 .... but you're the native speaker, not me ;)
> > >
> > > Ok for AppBinary then ;)
> >
> > How about "Exec" or "Execute" ?
> > AppBinary is still not 100% clear to me.
>
> No, Exec already exists and contains the command line.
> Here we don't want the arguments. We just want the name of the application
> "binary" (or shell!) .... ExecutablePattern ? ;) hmm...

At the risk of making this too simple -- how about just "Pattern="?  It's really the
same principle as in a mimetype file -- files that get the icon specified in the
kdelnk file.  It doesn't have to be an executable -- kfm does no enforce this --
I can choose to have my netscape.help file share the icon as well.  So why use a
different name than "Pattern="?

Regards,

Andreas

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