I worded my post poorly. My point was, if Apple has re-written iTunes in Obj-C, they didn't necessarily re-implement the same scripting interface They may have added, removed or fixed from 10.3 and earlier, or they may have dumped scriptability completely. Based on the posts in this group, visualization and other plug-ins are broken with 10.4 so I don't think it's unreasonable to wonder whether the scripting interface has changed. What I was hoping for was a link to an article I missed on a wonderful new native Cocoa API.
On Jul 21, 2011, at 02:40 PM, Jens Alfke <j...@mooseyard.com> wrote: On Jul 21, 2011, at 7:12 AM, bradgibbs wrote: I've been using Scripting Bridge in one of my apps. Now that iTunes is a native Cocoa app, I'm wondering what effect this is going to have on Scripting Bridge compatibility, Why would it have any effect? Scripting interfaces don’t depend on whether the app is written in C++ or Objective-C or Python or Pascal. —Jens_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
