|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
Ed Stockly wrote:
It's simple only on the surface. Does anyone really expect a neophyte
to understand its intricacies? Especially since the documentation
scratches the surface? And the problems aren't just with the language
per se. Are we really expected to depend entirely on the dictionaries
without any supporting documentation? Just one example (of a myriad),
what does iTunes do with "make" from the standard suite? What doesn't
it do? ... I feel abandoned.
Make is the verb. By itself it does nothing. It needs an subject (object) to do anything.
set resultObject to make new newTypeClass ¬ at atInsertionLoc ¬ with properties withPropertiesRecord
You need to tell it what to make and sometimes where to make it and you can define the properties the new objects is made with.
This is one case (of many) where, between the sample scripts freely available, the depth of the scripting implementation and the appleScript community knowlege base, tons of detailed documentation is not needed. In addition, if you master scripting one single scriptable application you can take that knowledge to script almost any scriptable app.
Sorry Ed, but you really are defending the indefensible here.
has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net
_______________________________________________ Do not post admin requests to the list. They will be ignored. AppleScript-Users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: Archives: http://lists.apple.com/archives/applescript-users
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.