Re: Mac OS X Script Menu
Re: Mac OS X Script Menu
- Subject: Re: Mac OS X Script Menu
- From: Chris Nebel <email@hidden>
- Date: Thu, 04 Oct 2001 11:25:57 -0700
- Organization: Apple Computer, Inc.
John W Baxter wrote:
>
OK, so installing Script Menu creates /Library/Scripts/Basics/ (et al) and
>
the sample scripts.
Actually, /Library/Scripts/<etc> is part of the base 10.1 system -- nothing to do
with Script Menu.
>
If I create a folder Basics in the /Users/john/Library/Scripts/ directory
>
and put a script into that Basics folder, what does happen is that my
>
Basics folder is listed separately (toward the bottom of the menu).
>
>
What *might* happen--I was experimenting to see whether it did
>
happen--would be to merge my Scripts folder with the machine's Scripts
>
folder. "Merge" would presumably mean that in case of name conflicts, "my"
>
script wins over the machine's script.
For what it's worth, Script Runner in 10.1 does exactly what you want. (Of
course, you then have to deal with a floating palette.) Script Menu was written
entirely separately, so it does it differently. There are a couple other minor
deficiencies in Script Menu, so we'll try to get those straightened out.
>
On the same note...is there a potential /Network/Library/Scripts
>
folder? Does it merge with the machine domain's folder? The user's? Neither?
"Potential" is the key word here. :) Creating one requires setting up and
properly configuring a NetInfo network. Doing this without the Mac OS X Server
administation tools is theoretically possible, but definitely not for the faint of
heart or weak of stomach.
As for how it behaves once you've got one, that would depend on the application.
Script Menu probably doesn't try to merge anything; Script Runner would merge all
the domains together. (The standard rule, by the way, is that user overrides
local (aka machine) overrides network overrides system.)
--Chris Nebel
AppleScript Engineering