The problem is Core Data. AppleScript was tough to implement in Journler because scripting is just plain hard. Well, it’s doubly hard with a Core Data application because of “ordered” and “unordered sets.” AppleScript uses ordered sets, but Core Data deals exclusively with unordered sets. For folks who aren’t sure what we’re talking about, think of a bag of apples. AppleScript pulls the apples out of the bag in the same order every time. Core Data just gives them to you in any old order.
Going back and forth between ordered and unordered data is apparently a pain in the butt. I have to implement a middle man which gets the apples in any old order but puts them into the expected order before handing them off to AppleScript. Thankfully a long time coder has provided a sample project which demonstrates how to do it. I already have my hands on the project and have been going over it.
Keep your fingers crossed!]]>
This latest post convinces me that with the AppleScript savvy you discussed once before (one of your proxy plug-in apps, I surmise), Lex will be a must have for Scripters, replacing Daniel Jalkut’s now aging FastScripts and Spotlight for finding stuff. Though FS has an entirely different basis, Lex, with a little scripting, can be made to do everything it does and serve as the basis for your scripting projects. I suspect coders in other languages will feel the same.
Looking forward to it.]]>