Re: AS Library Question
Re: AS Library Question
- Subject: Re: AS Library Question
- From: Chris Page <email@hidden>
- Date: Thu, 17 Dec 2015 06:35:09 -0800
> On Dec 11, 2015, at 3:35 PM, Shane Stanley <email@hidden> wrote:
>
> On 12 Dec 2015, at 10:02 AM, has <email@hidden> wrote:
>>
>> TBH, I'd be surprised if there are very many apps in App Store that provide any sort of Apple event ("AppleScript" automation) interface, never mind support attachability (the ability to run scripts).
>
> I agree. But that also means that the main point you raised about libraries being per component instance is largely moot.
>
> I've no idea why libraries were implemented that way, but you don't seem to countenance the possibility that there were pros as well as cons. Perhaps it's just my naivety showing, but I'm inclined to assume that there was some reason for the decision other than a coin toss or malevolent intent, especially given that it seems a bit unusual. It may have been a flawed design decision -- it might also have been a wise choice. Without knowing all the details -- and I suspect that applies to you as well as me -- it seems a tad churlish to assume the worse.
See my explanation in my earlier reply. The executive summary is that the only interesting thing about libraries is how they're searched for on disk; once they're in the AppleScript runtime they're just like any other script object. The fact that OSA supports creating multiple instances of a scripting runtime is a feature that offers flexibility that you don't have to use if you don't want to. I haven't seen a con described yet. Do you know of one?
--
Chris Page
The other, other AppleScript Chris
_______________________________________________
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