• 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: [PSA] native AppleScripting support for Swift
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PSA] native AppleScripting support for Swift


  • Subject: Re: [PSA] native AppleScripting support for Swift
  • From: has <email@hidden>
  • Date: Wed, 15 Jul 2015 22:16:52 +0100

Hi Alex,

Thanks for the kind words. I know AEB's off to a hopeful start: I've been using appscript professionally for high-end automation for years[1], and hundreds (thousands?) of other appscript users have beaten the tar out of it over the years too, so the design has already proven itself. OTOH, there's a *lot* of roughness in the packaging and presentation - my Swift/ObjC/Xcode-fu sucks so it could really do with a more experienced hand on that side. And it's based on objc-appscript which was always the least polished and tested of the old appscript bridges, so a wide-spectrum shakedown from experienced application automators is also much needed to check I've not missed any compatibility issues. (Plus the documentation needs a damn good edit, natch; but I'm not going to worry about that until the first two issues are covered as it's in flux till then anyway.)

Basically, I can do the AE-related engineering okay cos I know that narrow problem space better'n anyone, but for everything else it needs other folks to step up and assist. Partly cos those are areas I'm short on skills and time to do it and get it right all on my own; partly cos my failing to get others invested and involved in project development, or work effectively with them to evangelize and support it, was the reason it all cratered last time around. A system's only ever as good as its weakest point, which in AEB's case is the rubbishy non-redundant wetware it's currently running on, so the eventual goal would be to persuade Apple to take it over for inclusion in 10.12 [2], although that's require a heck of lot more folks to throw their weight behind it. So baby steps and bug reports first, and all help and advice is greatly appreciated.

Best regards,

has

...

[1] And still do: http://www.mantasystems.co.uk/docs.html

[2] A not entirely unrealistic goal as Mac::Glue already made it into 10.4, and appscript (alongside RubyOSA and SB) was being considered for inclusion in 10.5, and might have made it in too had dumbass here not been asleep on the job. :/



On 15/07/2015 12:53, Alex Zavatone wrote:
Thanks, Has. This looks great.

Sent from my iPhone

On Jul 13, 2015, at 10:25 AM, has<email@hidden>  wrote:

Hi all,

In light of OS X 10.11 addressing some longstanding deficiencies in NSAppleEventDescriptor, I've been dusting off a fork of my old objc-appscript project, now renamed AppleEventBridge, modernizing and extending it both to take advantage of improvements to ObjC in the last few years and to add native support for Apple's new Swift language:

    https://bitbucket.org/hhas/appleeventbridge/


_______________________________________________
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: [PSA] native AppleScripting support for Swift
      • From: has <email@hidden>
References: 
 >[PSA] native AppleScripting support for Swift (From: has <email@hidden>)

  • Prev by Date: Re: Parsing two dates in Apple Mail for Calendar
  • Next by Date: Re: [PSA] native AppleScripting support for Swift
  • Previous by thread: [PSA] native AppleScripting support for Swift
  • Next by thread: Re: [PSA] native AppleScripting support for Swift
  • Index(es):
    • Date
    • Thread