[Nautilus-list] Re: suggestions for redoing the Nautilus script feature

[Darin Adler <darin bentspoon com>]

On 12/14/01 5:32 PM, "Marco Craveiro" <soupdragon clix pt> wrote:

> what i mean is, change the nautilus script to be an xml file with:

The first downside I see for this is that the current Nautilus scripts can
be any executable, and this would make them all incompatible. But we could
combine this feature with the old one perhaps, and make it just execute the
file if the x bit is set, and otherwise look inside to see if it's good XML.

> a) the location of an icon file
> b) a menu entry for the script
> c) a tooltip for the icon
> d) a gtk dialog with all the command line options for the tool. this
> should have an "advanced help" button that sends you (via doc browser)
> to the man page of the tool and a "begginers help" that gives you a
> *simple* overview of the tool. this dialog ideally should be made in
> glade and inserted in the xml file.
> e) the location of the command line tool, which could be located
> anywhere in the disk.
> f) some kind of flag to allow / disallow / warn about using the tool
> on binary files. if this flag is set, nautilus would check the file
> type first before running the tool and take appropriate action.

It seems to me that most of this can be done within the current framework.
You make a script that invokes some kind of tool to show the dialog, and
then call the 'real tool' underneath.

I'd suggest working out the feature that way to prototype it. It should be
relatively easy to integrate into Nautilus if your prototype looks good.

    -- Darin