• 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: Script Objects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Script Objects


  • Subject: Re: Script Objects
  • From: has <email@hidden>
  • Date: Tue, 19 Jan 2010 20:53:47 +0000

Mark J. Reed wrote:

> Thus, my point: such a lack is not really an issue with script objects
> at all, much less the biggest one.  It's an example of them being
> poorly suited to one particular application.

Script objects are ideally suited for use as native language modules, providing easy unmarshalling and [with a little care] reliable namespaces.

The problem with AppleScript is that it lacks a built-in system for loading and managing lots of modules for you.

So while you can use modules in AS, the cost of entry is high (since you need a certain level of knowledge and skills to write your own) and the benefits are limited (since there are almost no third-party modules available to use).

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

  • Prev by Date: Re: Script Objects
  • Next by Date: Re: Script Objects
  • Previous by thread: Re: Script Objects
  • Next by thread: Re: Script Objects
  • Index(es):
    • Date
    • Thread