• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Tell Blocks Considered Harmful (was Re: open for access)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tell Blocks Considered Harmful (was Re: open for access)


  • Subject: Re: Tell Blocks Considered Harmful (was Re: open for access)
  • From: Philip Aker <email@hidden>
  • Date: Sun, 14 Dec 2008 05:06:56 -0800

On 2008-12-14, at 03:09:16, Chris Page wrote:

Is anyone aware of applications that actually use an addition loaded into their process to handle scripting commands from other processes, instead of just installing event handlers with their application code?


I wrote an osax for an AppleScript Studio developer to be able to interact with Final Cut Pro in his project scripts. FCP has events but no script level interface.

You mean that FCP handles events but has no terminology dictionary,

Yes, and no concept of an object model either. Strange but true.


so you created an OSAX that contains the terminology?

I mapped every event that the client wanted to a terminology I concocted.



Does your OSAX contain event handlers?

Don't quite understand. It's all event handlers -- I did any necessary coercions directly in code rather than installing handlers for them.


§

A few other osax developers you may wish to forward your question to are Mark Alldrit, the Smile developers, some Japanese guys (Tanaka e.g.), and whoever makes the 24U Appearance OSAX.


What are implications for OSA components?

Sorry, the implications of what?

OSAExecuteEvent() and it's immediate companions to be specific.

Leopard messed up the cursor handling for my OSA components which give applets and droplets additional UI capabilities. I haven't been able to find a shred of documentation about changes in applets at this level. In fact, every OS since 10.2 has involved convoluted workarounds or loss of abilities for OSA components due to changes. So I'm concerned about the implications of the sender vs target topic you've brought up because components can delegate events to the AppleScript component (or override them).


Philip Aker echo email@hidden@nl | tr a-z@. p-za-o.@

Democracy: Two wolves and a sheep voting on lunch.

_______________________________________________
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
  • Follow-Ups:
    • Re: Tell Blocks Considered Harmful (was Re: open for access)
      • From: Chris Page <email@hidden>
References: 
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Shane Stanley <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Chris Page <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Philip Aker <email@hidden>)
 >Re: Tell Blocks Considered Harmful (was Re: open for access) (From: Chris Page <email@hidden>)

  • Prev by Date: Re: What's so great about AppleScript, anyway? (was Re: Tell Blocks Considered Harmful…)
  • Next by Date: Re: Tell Blocks Considered Harmful (was Re: open for access)
  • Previous by thread: Re: Tell Blocks Considered Harmful (was Re: open for access)
  • Next by thread: Re: Tell Blocks Considered Harmful (was Re: open for access)
  • Index(es):
    • Date
    • Thread