Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Mysterious nulls in NSScriptCommand



On Nov 7, 2007, at 12:21 PM, Matt Neuburg wrote:

Please tell me to go f myself if I'm being obnoxious, but a lot of what
you're asking seems to involve, not an ignorance of Cocoa Scripting, but of
AppleScript. If so, I *have* written a book. I could be misunderstanding
what's giving you trouble, but it seems to me that it is quite clear on most
of the issues that you've raised so far.

To put it another way: I might be wrong, but you are talking like a person
who has never used AppleScript. You can't learn AppleScript from Cocoa
Scripting, or learn them together. You must know AppleScript first, because
you have to understand what the scripting user is going to say and what
that, in turn, is going to mean for your scriptable app.

The book does also have a section that gets you started with making your app
scriptable.

So the funny thing is, I have your book, though, the first edition. Indeed, what I know of AppleScript, the language, I know largely from you. 

That said, while I've written useful things in AppleScript, I'm not an AppleScript programmer, nor will I ever become one. I'm a Cocoa developer, who programs in Objective-C. Like most of my peers, I have a passing, begrudging relationship with AppleScript. I envy its power, I hate its language, and I fear its implementation.

More than anything, though, I want to make my users happy. I want to make sure they have a good experience scripting my application. I even want to make sure they have passable sample scripts, as written by yours truly. But in order to deliver that, I need to have the needs of AppleScript and its users presented in my terms, so I can understand it.

I find the fact that "tell <something> to add <object> to <container>" sends the message to <object> bizarrely illogical. I find the fact that I can't find a way to find out who <something> is to be even worse. Yes, now I see that the direct parameter receives the message. That doesn't make it make it any more sense, nor does it solve the problem.

That's fine. I can deal with it. I just wanted to make sure I wasn't missing some obvious solution. Work continues.

Mike Lee, Major-domo
Delicious Monster Software, LLC

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-implementors mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/applescript-implementors/email@hidden

This email sent to email@hidden



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.