Re: New iTunes Track
Re: New iTunes Track
- Subject: Re: New iTunes Track
- From: Andrew Oliver <email@hidden>
- Date: Tue, 24 Feb 2004 20:40:43 -0800
On 2/24/04 8:09 PM, "Matthew Smith" <email@hidden> wrote:
>
on 25/02/2004 14:07, Andrew Oliver at email@hidden wrote:
>
>
> On 2/24/04 6:10 PM, "Matthew Smith" <email@hidden> wrote:
>
>
>
>> "... you would need iTunes to be able to notify you when there is a change,
>
>> which it can't do. "
>
>
>
> Change that to "which it doesn't do", not "can't do"
>
>
I am sorry. You and I must see things differently. CAN the current version
>
of iTunes do it? It can't without programming changes. To me, can't and
>
doesn't are the same things as I cannot change the code of iTunes in order
>
to provide that functionality.
We're clearly looking at this from slightly different perspectives. :)
To me 'can not' implies that under no circumstances is something possible.
AFAIK this is not the case with what you're trying to do with AppleScript
and iTunes. What you propose COULD be achieved IF the developers of iTunes
wrote the (relatively few) lines of code to support it.
Could you or I do that? No, but that's not to say it cannot be done.
My statement that iTunes does not notify/call a script that is more accurate
than saying it can not call a script.
In either case, to say that *AppleScript* can not do this is patently
untrue. The earliest releases of AppleScript had the API functionality to
allow applications to provide callbacks to scripts. On that basis,
AppleScript absolutely CAN do what you want, but the iTunes developers (like
so many others) chose not to implement it in their application.
In short, I think your beef is with the application developers, not the
AppleScript developers per se.
>
>
>> "Unfortunately that's not how AppleScript was designed to work."
>
>
>
> Wrong again.
>
>
>
> There's absolutely no reason why an application can't call a script on
>
> specific events. In fact, the original AppleScript specification classified
>
> AppleScript support at various levels ranging from 'basic' (app responds to
>
> events sent via AppleScript), 'recordable' (speaks for itself) and
>
> 'attachable' - I may have the specific names wrong, but the last option
>
> means the application supports invoking scripts within the application
>
> itself.
>
>
>
> The problem you describe is due to the APPLICATION developer not adding the
>
> feature, not an inherent limitation of AppleScript itself.
>
>
>
> There are applications out there that support attachable scripts. iTunes
>
> just isn't one of them.
>
>
What you are saying is that the applications must be written so that
>
AppleScript can do it. I agree. What I am saying is that AppleScript was not
>
designed to do it when an application is not written for it.
That statement makes no sense. AppleScript IS designed to do this, but it
has to be a two-way interaction. AppleScript has done its part, it's up to
the application to do its part, too.
How is AppleScript supposed to circumvent decisions made by the developer?
Again, AppleScript does everything it needs to support this functionality.
If the developer chooses not to take advantage of that it's hardly
AppleScript's fault.
Andrew
:)
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.