Re: links

This sounds like exactly what I would like to see. :)

But if you had this file in every directory you would need
to have someway in which if a file was moved that the .EA
files were updated.

Mark Eaton
ICQ 1779385
-----Original Message-----
From: Paul Hepworth <>
To: '' <>
Date: Thursday, 12 February 1998 10:31 am
Subject: RE: links

>> From: Mark Eaton[]
>> I disagree. I use ln -s blah blah blah all the time and
it is exellent
>> yes. I wish I could use it under Windoze. But it doesn't
do what say
>> kdelnk does. It doesn't store gui info such as icon or
tooltips. It
>> doesn't let you setup up parameters to be passed when
run. There are
>> lots of things that say a glnk could do that linking
can't. I think
>> that having both would be the best solution.
>I'd say let the user attach icon/tooltips/parameters and
other extended
>information to ANY file, not just to a link.  If I want
>(comments) and specific icons for certain folders, my
executables, and
>specific data files (in addition to sym links to programs),
I should be
>able to do this.  It would be simple to add extended
attributes without
>filesystem support (since we don't have fs support) using
either DFM's
>one-file-database-in-home-dir or (my preference) in a .EAs
file in each
>directory that contains files with extended attributes.
>The .EAs file could be text editable looking something like
>"A filename that has EAs associated with it" {
>  icon=hideous.xpm
>anotherFile.dat {
>  mimetype="some mimetype to override the extension-assumed
>  tooltip="A piece of text to quickly describe the
>  icon=cool.xpm
>  doc="man:manpage"
>  #doc=""
>  run="$x -d4 $f"
>  # $x is system-wide program associated with this mimetype
>  # $f is filename (of this file)
>  # $p is full pathname of file
>  # $1, $2, $* etc. represent dropped files
>  # $1p, $2p, etc. represent full path names of dropped
>  # $c is current working directory
>  # $? would suggest that the shell prompt the user for
>  # default for non-executable files is run="$x $f"
>  # default for executable files is "$f $*"
>  paramsDefault="untitled.text"
>  # default paramsDefault is "$f" for non-executable, "$*"
>  paramsPrompt="Enter filename(s):"
>  # default prompt is "Enter parameters for $x:" for
>  # default prompt is "Enter parameters for $f:" for
>"aJavaProg.class" {
>  icon=neato.xpm
>  doc="some prog.html"
>  run="java thePackage.theSubPackage.aJavaProg"
>  # needed because an association isn't sufficient to run
>  #   a java class that's in a package
>  #   (alternatively, the standard program launcher could
>  #     the class file for package name as well as for the
>  #     of main() or "extends Applet")
>"some text file" {
>  tooltip="third letter to my mother requesting that raise
to my
>  run="preferedEditor $f":"altEditor -lineNumbers
$f":"yaEditor -f $f"
>  # will run preferedEditor by default (double click),
>  #   but context menu, for example, would contain the
other options
>  print=preferedEditor:"text2ps $f | lpr"
>Any program (not limited to desktop or file managers) could
use the
>GetEA() API via C/C++/Guile/CORBA.
>Because these attributes could be attached to any file,
this has a big
>advantage over .lnk files.  Using this facility in
conjunction with
>symbolic links accomplishes what the .lnk ppl want, but in
a more
>flexible way.  This also permits adding attributes to
folders, files,
>I'm not sure what the best way to internationalize these
settings would
>         To unsubscribe: mail
>                       "unsubscribe" as the Subject.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]