MacNN Forums (
-   Mac News (
-   -   Most AppleScript commands stripped out of latest iWork apps (

NewsPoster Oct 23, 2013 11:27 AM
Most AppleScript commands stripped out of latest iWork apps
The AppleScript dictionary included with the <a href=" ers/" rel='nofollow'>latest version of the iWork suite</a> has been so stripped down as to be virtually absent, a developer observes. AppleScript lets both developers and individuals automate actions that would otherwise require many repetitive steps. "What I suspect Apple doesn't realize is how much small business and small shops workflow depends upon AppleScript," <a href="" rel='nofollow'>comments</a> the developer, Clark Goble. "Casual use is fine. But a lot of people do more. It wouldn't be so bad were there an alternative."<br />
<br />
Why Apple would strip previously-existing AppleScript hooks is unknown. The company may have felt the code wasn't worth the time and resources, or simply not been able to meet deadlines for an October 22nd release. In the latter case, full AppleScript support could theoretically be restored in a later update.
bobolicious Oct 23, 2013 11:59 AM
I would concur with the linked article - while portability may enjoy some enhancements, this would seem regrettably another reason NOT to sidegrade...

Despite the elegance of the design & many new features (tabbed folders actually RE-introduced from Classic?) the Mac OS & software ecosystem seems to be increasingly a limited & risky workflow investment for professional work...
QualleyIV Oct 23, 2013 12:54 PM
"Mac OS & software ecosystem seems to be increasingly an limited & risky workflow investment for professional work..."

Congratulations on posting the most asinine comment I have read all day. So, one feature (which, it's not clear from your dumb post, you even use) didn't make it into an updated version of Pages. That's hardly supportive of your statement. I love AppleScript, but it's hardly a mainstream feature and there are literally thousands of things that Apple HAS done which would completely contradict your claim.
DiabloConQueso Oct 23, 2013 12:58 PM
"Professional work" computers are rarely updated to cutting-edge software without going through testing and deployment phases first.

Unless, of course, one of two things is happening: 1) It's not really a professional talking, or 2) Someone is completely ignoring best-practice "rules" with regard to updating and upgrading machines in the middle of projects, and/or the moment an upgrade is released.
bobolicious Oct 23, 2013 01:51 PM
"2) Someone is completely ignoring best-practice "rules" with regard to updating and upgrading machines in the middle of projects, and/or the moment an upgrade is released."

Clearly the linked article author may have taken that approach, and 'testing' in this camp is still ongoing since the release of Lion, without real partial ability to get past Snow, save one machine for review, now running Mavericks Server.

I don't use applescript (or inflammatory language in posting an opinion like QualleyIV), but do feel beyond my own needs an empathy for those that may have invested many hours building what was supposed to be a productivity enhancement, now potentially unilaterally abandoned, yet with software tied to hardware forcing compromises and potentially hurting mac sales...

It will be interesting to see adoption rates now that the $20 MacOS upgrade fee has been eliminated...
DiabloConQueso Oct 23, 2013 02:14 PM
If you're of the opinion that the specific language that I used was inflammatory, then it must be extremely difficult to carry on a conversation with you.

While I understand the developer's concerns (and also "empathize" with him, even though it would be me empathizing through him, then empathizing with the fictional straw-men he's created in his argument), he's wrong in stating that there's no alternative... because there is. Simply continue using the applications and workflow they have invested hours into. Nothing that anyone has that was working yesterday is broken today.

If you want to have a complex, custom, automated workflow, and you also want to be on the cutting-edge of software and hardware, then you're going to have to be flexible and accepting of change. It's the same on other platforms as well, and is the same across virtually every industry known to man.

Most cars no longer use surface carburetors, most amplifiers no longer use vacuum tubes, and most computer users no longer use Rosetta. ;) All of those were pretty easy transitions that the majority of people made it through without much fuss, unless they waited half a decade or more to do something about it.

There's no reason to suspect that this potential transition will be any different, unless we're just dealing with a minority of extremely stubborn people.

As for the adoption rate, I can't say whether it's going to be quick or gradual, but the one thing I do know is that Apple's intentions of providing free upgrades all the way back to Snow Leopard and certain Macs back to 2006/7 is more than likely an effort to standardize and equalize the playing field -- in other words, if it's free, then people will likely adopt it, and Apple can rest assured that the majority of their users are using a common OS and set of software. It makes certain things much easier.
Boise Ed Oct 23, 2013 07:02 PM
I use AppleScripts every day. It's bad enough that Apple removed support for cron (UNIX scheduling file) and thus the Cronix program a few years ago. Now they are moving to drop AppleScript??? Bad move, Apple.
elroth Oct 23, 2013 10:30 PM
To DiabloConQueso: He's talking about QualleyIV's post, not yours.
The Vicar Oct 24, 2013 12:42 AM
@Boise Ed:

Apple removed support for Cron because they have another utility which does everything Cron can do and more. You can still schedule things on the command line. (Heck, if you need a graphical editor and can't find one cheap enough for you, use Calendar. You can have events in the calendar trigger program launches, including -- of course -- AppleScript programs which can control other things.)
The Vicar Oct 25, 2013 10:52 PM
Let's see if MacNN will let me actually post this now. (I tried days ago, and the "Submit" button did nothing but put "" above "Add Your Comment"...)


You have to understand: the developers at Apple who came with Next don't like AppleScript. AppleScript support in Cocoa is difficult to set up, and the tools to make Cocoa applications understand AppleScript have always been awful and often buggy as well. From the Next perspective, if you want scripting, you use the command line, and shut up everyone who knows how useful object orientation and structure and syntax which can be tested are. I suspect "Automator" is a not-too-subtle attempt to replace AppleScript with a system the Cocoa crowd likes better, never mind that Automator is mostly pretty useless without AppleScript support. Expect to see AppleScript deprecated more and more as time passes.
All times are GMT -4. The time now is 07:26 AM.

Copyright © 2005-2007 MacNN. All rights reserved.
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2017, vBulletin Solutions, Inc.

Content Relevant URLs by vBSEO 3.3.2