Hmmm. I'm having trouble implementing your suggestions. As far as persistent properites goes, I'm wondering if QS uses executeAndReturnError from the NSAppleScript class to run applescripts. I found a discussion pointing out that this method does not allow for persistent properties.
http://developer.apple.com/documentation/Cocoa/Reference/Foundation/Classes/NSAppleScript_Class/Reference/Reference.html#//apple_ref/occ/instm/NSAppleScript/executeAndReturnError: So I'm thinking that the script could create a text file in /tmp and store the login properties there. As far as getting the php script embedded in the applescript, that's going to take someone who knows php. I tried to escape out from the single and double quotes, and even tried variations of using extra back-slashes, but I could not get it to work. I wonder if when a method containing single quotes is called the quotes need to be triple or extra escaped in someway.... Anyways I'm failing on both counts... Any ideas? On Sep 18, 2:20 am, "Jon Stovell (a.k.a. Sesquipedalian)" <[email protected]> wrote: > That's really cool. Thanks for this. > > Here are two suggestions to make it easier for users who aren't tech > savvy: > > 1. Because Applescripts remember changes to their property values > between executions, it is possible to query the user for necessary > information the first time the script is run. It will only be > necessary for the user to enter it once, and the data will be saved > forever, unless the script is opened and recompiled. > To do this will require adding proper escaping to your php code. > First, Applescript will require you to escape all double quotes ( " → > \" ). Second, because php -r requires single quotes around the entire > argument code block, you will have to escape all the single quotes; > moreover, to prevent Applescript from trying to interpret those escape > sequences, you have to double escape the single quotes ( ' → \\' ). Of > course, this is a simple find and replace operation in your text > editor, so no big deal.
