RE: iTunes programming question
RE: iTunes programming question
- Subject: RE: iTunes programming question
- From: "Philip Lukidis" <email@hidden>
- Date: Tue, 11 Jul 2006 10:15:13 -0400
- Thread-topic: iTunes programming question
I'll investigate AS and script precompilation in more detail. Maybe then it would be acceptable. I'll know more when I receive the specifications, and then I could do some intelligent prototyping. Since I don't have an experience in scripting AE appealed more to me, but it appears that a fair amount of reverse engineering is required for this.
thanks,
Philip Lukidis
-----Original Message-----
From: applescript-users-bounces+plukidis=email@hidden
[mailto:applescript-users-bounces+plukidis=email@hidden
]On Behalf Of Jon Pugh
Sent: Monday, July 10, 2006 5:44 PM
To: email@hidden
Subject: Re: iTunes programming question
At 1:45 PM -0400 7/10/06, Philip Lukidis wrote:
>I need to control iTunes, though I have not received a precise specification request yet. I know that I'll have to query the library database, find out which track is playing, be notified for library/playlist/track changes, and other similar requests (sorry to be so vague). I thought it preferable to use Apple Events for speed, and while I would guess that this is possible, I have not found any Apple documentation on how to do so. Could anyone point me towards some documentation on this? I'd rather not rely on Applescript if I could avoid it, so as to minimize response times. Apple events would seem to be preferable, at least prima facie.
Personally, I would prototype in AppleScript and implement an OSA runner to make your prototype work with the script. This will be a minimal amount of work and will offer you flexibility while your client changes his mind several times and you determine what you actually need the script to do.
AppleScript response times are insignificant if you load your script once and run it a bunch of times. It's loading and/or compiling that takes time and makes script running slow. However, it's simple enough to avoid that.
Then, after you've determined that this works well enough, you can can relax on the beach. Or, if you've determined that it uses too much memory you can spend a lot of time reimplementing the script in pure AE calls. However, odds are good that if it's too slow, it's not AppleScript's fault.
Jon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden