Hi Justin, Yes the AppleScript changes you mention will be in ß72 so aren't currently available. Apologies for the confusion, but it'll be released soon!
Unfortunately at this time AppleScripts in Quicksilver can only deal with text representations of Quicksilver objects, and not the actual object itself. As such, if you were to send iTunes tracks to the script, the script would only get a list of names (for each track). This could be changed so that the text representation of an iTunes track (or artist) is something a bit more useful (e.g. the ID of the track or artist) which the script could then use to lookup the actual track object. The main issue is that QS does not send the AS objects to the script, which is something that should be fixed, but probably won't be done soon. It would mean that every plugin would have to be updated to add a method to tell Quicksilver how to convert Quicksilver objects into AppleScript objects. Patrick P.S. I've forwarded this reply to the Support Forum, where hopefully it will be of use to others - and Rob, who's worked the most on the iTunes plugin, incase he's inclined to make the change above :-) Hi Patrick, > > I was looking to create a custom Quicksilver action via an applescript, > and I stumbled on the wiki pages you made. Only after quite a bit of > confusion and experimentation did I realize that these features haven't > made it into a release yet. From what I gather, I'll see these in ß72, > right? > > In any event, having little experience with Applescript, and not being > able to experiment with the improvements yet, I'm not sure if I'll be able > to do exactly what I'm looking for, so I figured I'd run it by you in hopes > of getting some direction. I'd like to make an action that can take a > comma-trick list of iTunes-plugin-indexed songs (or an album), get certain > info from them (like song title, album name, artist name) and then run a > shell command that involves this info and the file locations (I'll be using > lpr to print the mp3s to a remote server with job names that reflect the > song info). I see that the improvements include a com.apple.itunes.track > type, but will I be able to treat such objects as one would treat a "file > track" in an iTunes Applescript? That is, can I use the iTunes dictionary > to get the song info from them? Furthermore, if I pull up an album in the > first pane, or even let's say an artist, would the script understand this > as a list of tracks (as if I had used the comma trick)? My intuition leads > me to believe the answer is 'no', so I'm not quite sure how I'd precede to > write the script I have in mind. > > I'd greatly appreciate any thoughts you could share. > > Best, > Justin > -- You received this message because you are subscribed to the Google Groups "Quicksilver" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/blacktree-quicksilver?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
