Re: ACGI form parsing in OSX?
Re: ACGI form parsing in OSX?
- Subject: Re: ACGI form parsing in OSX?
- From: Paul Berkowitz <email@hidden>
- Date: Sat, 02 Feb 2002 23:14:36 -0800
On 2/2/02 10:30 PM, "Stephen Swift" <email@hidden> wrote:
>
At 2/2/02 5:39 AM, email@hidden (email@hidden) Wrote:
>
>
> tell application "greet"
>
> set niceword to "hello"
>
> set responseIgot to greetwith(niceword)
>
> end tell
>
> display dialog responseIgot
>
>
>
> Got it now? : )
>
>
Yes, but why would anyone need to use that? Pass variables from one script
>
to another that is.
>
One reason would be to use one script as a prefs-setting script for another,
especially when the main script is run that runs automatically. In OS 8/9
you could change properties (set prefs) by requiring Jon's or Akua, and run
the script with a modifier key or two down, which the osax could detect, and
run a handler for resetting the properties. You can't do that in OS X now.
(And some people didn't like to require osaxen either.) So the prefs script
loads the main script and sets its properties. Not just telling, as above.
But I've had to do that too: I had a compiled script that needed to run from
within an application, and to emulate key-pressing (via Sigma's Additions)
to run an unscriptable command from a keyboard combo. the trouble was - the
app is designed (correctly) to ignore menu and keyboard input while it's
running a script. So the script called an applet elsewhere on the hard disk,
which launched in the background and emulated the keystrokes that controlled
the menu item in question in the front app. The compiled script also needed
to send the applet a current value so it would know what to do this time. It
did something like Jeff's script above.
--
Paul Berkowitz