Re: Transliteration, TextCommands osax
Re: Transliteration, TextCommands osax
- Subject: Re: Transliteration, TextCommands osax
- From: has <email@hidden>
- Date: Thu, 20 Nov 2008 18:47:24 +0000
Paul Berkowitz wrote:
TextCommands is not an osax, it's an app.
What Paul says. Like OS X's own Keychain Scripting and URL Access
Scripting 'additions', it's a faceless background application (FBA)
with a scripting interface designed for use as an 'extension' to the
AppleScript language.
has doesn't like osaxen
They inject arbitrary Apple event and coercion handlers into processes
and inject arbitrary keywords into AppleScript's global namespace,
both of which can cause all sorts of hidden and hard-to-identify
problems (up to and including creating a serious security hole in OS
X). Originally a quick-n-dirty kludge, osaxen are completely the wrong
way to implement a _language_ extension mechanism. Even Apple
recommend implementing 'AppleScript extensions' as scriptable FBAs
rather than osaxen when practical. That's not to say there aren't some
situations where the practical advantages of using them may outweigh
their disadvantages (even I've written the odd osax to meet a
particular need), but for most tasks a scriptable FBA is simpler,
safer and/or more capable.
That all said, the reason TextCommands is an FBA is purely practical:
it's written in Python, and packaging Python code as a scriptable FBA
is much quicker and simpler than packaging it as an osax.
Regards,
has
--
Control AppleScriptable applications from Python, Ruby and ObjC:
http://appscript.sourceforge.net
_______________________________________________
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