| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Nov 7, 2007, at 12:21 PM, Matt Neuburg wrote:
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
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
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.