Re: Pages 4.3 and Mavericks - Can't export as PDF
Re: Pages 4.3 and Mavericks - Can't export as PDF
- Subject: Re: Pages 4.3 and Mavericks - Can't export as PDF
- From: Shane Stanley <email@hidden>
- Date: Tue, 05 Nov 2013 09:48:10 +1100
On 5 Nov 2013, at 3:38 AM, Paul Berkowitz <email@hidden> wrote:
> It's still a fairly recent "shortcut" that we could ever save in a string.
> In older AppleScript you had to save in a file too, or it could depend on
> the application doing the saving.
That's right.
> I gathered that using a string (valid
> filepath) was closer to what other programming languages did so maybe made
> some new AppleScripters comfortable
I suspect it was largely accidental, a byproduct of how Cocoa scripting works. If an application specifies a type of "file" in its scripting definition file, Cocoa scripting will automatically accept either a file or a path, and pass the developer an NSURL. Presumably the NSURLd built this way lack the security scoping of files built by AppleScript itself.
I see some dictionaries now seem to be going back to the nonsense of claiming to save to aliases -- I don't know if it's related.
--
Shane Stanley <email@hidden>
<www.macosxautomation.com/applescript/apps/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden