• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)


  • Subject: Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
  • From: Ed Stockly <email@hidden>
  • Date: Thu, 18 Dec 2008 14:38:21 -0800



It's simple only on the surface. Does anyone really expect a neophyte
to understand its intricacies? Especially since the documentation only
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.

Most applescript commands behave that way.

Here's a few plain and simple examples.

tell application "iTunes"
   --
   make new playlist
   make new EQ preset
   make new user playlist
end tell

Within the app you can send the make command to windows or playlists or the library and create all sorts of itunes objects.

Look here for a ton of very well written AppleScript iTunes examples.

http://dougscripts.com/itunes/index.php

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.

HTH,

ES=
_______________________________________________
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

This email sent to email@hidden
  • Follow-Ups:
    • Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
      • From: Paul Scott <email@hidden>
References: 
 >Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful) (From: "John C. Welch" <email@hidden>)

  • Prev by Date: Re: on blocking target applications' GUIs (was Re: Tell Blocks Considered Harmful)
  • Next by Date: Re: on blocking target applications' GUIs (was Re: Tell Blocks Considered Harmful)
  • Previous by thread: Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
  • Next by thread: Re: on neophytes vs perfectionists (was Re: Tell Blocks Considered Harmful)
  • Index(es):
    • Date
    • Thread