Re: Lion crashed by AppleScript
Re: Lion crashed by AppleScript
- Subject: Re: Lion crashed by AppleScript
- From: Shane Stanley <email@hidden>
- Date: Sat, 23 Jul 2011 12:02:25 +1000
- Thread-topic: Lion crashed by AppleScript
On 23/7/11 7:37 AM, "Luther Fuller" <email@hidden> wrote:
> There seem to be new rules about how System Events is allowed to write a
> preference file.
> I wish I knew what they were.
They are probably not specific to System Events. There are a lot of
security-related changes in Lion, and there's more infrastructure for making
sure multiple apps can't write to a file at once. If you've read about the
way you can add a document as an attachment in Mail, change the original,
and the changed version will then get sent -- implementing that sort of
thing needs more control over who has access to files. And it can only get
more complicated with iCloud.
You may just be hitting a bug, but I'm inclined to think the days of
fiddling with preference files like this are numbered anyway. Security is
becoming a big issue in MacOS, and things like sandboxing introduce all
sorts of limits on what an app can do. The idea is simple in principle: an
app can't do anything it can't make a good case for being able to do. And
the final arbiter of that will be Apple. It's opt-in at the moment, but it
seems it will soon be required for all apps in the App Store.
In that sort of security environment, it's wishful thinking to believe that
AppleScript will come through unscathed longer term, IMO. There are
undoubtedly people at Apple who believe that even a scriptable Finder poses
an unnecessary security risk.
Even the less paranoid are possibly eyeing off scripting additions, and
especially commands like "do shell script". And honestly, I don't know that
I'd fancy being the person given the job of defending them.
Whether this emphasis on security first is good or bad is not really
on-topic for this list, anyway. What is important to understand, I think, is
that hacks are just that. When they break, you can't really complain -- you
either hunt around for another loophole, or thank them for the memories and
move on.
But maybe I'm being too pessimistic...
On the bright side, as back doors are under threat we're getting more access
to the front door. AppleScriptObjC in Lion gains access to a whole lot more
through the ability to call C functions. And Lion lets you take advantage of
AppleScriptObjC in scripts you write in AppleScript Editor, rather than
requiring Xcode.
It's not perfect -- there's no logging, apart from anything else. But
<blatant_plug> you can also use my AppleScriptObjC Explorer, which will give
you logging and a whole lot more -- including the ability do it in 10.6, as
well as Lion <blatant_plug\>.
--
Shane Stanley <email@hidden>
'AppleScriptObjC Explored' <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