RE: IPTC info
RE: IPTC info
- Subject: RE: IPTC info
- From: Roger Howard <email@hidden>
- Date: Tue, 07 Mar 2006 13:32:03 -0800
On Tuesday, March 07, 2006, at 01:18PM, Stockly, Ed <email@hidden> wrote:
> >>>Roger>>>I sent you a detailed response pointing toward another solution; not sure why it wasn't listed here .... Exiftool ... a command line wrapper around a Perl module
>
>
>Well, this is the AppleScript users list and the question was for an AppleScript solution. Personally I wouldn't know where to start with a "command line wrapper around a Perl module" and I wouldn't suggest shell scripts or terminal scripts or Perl modules when there's a perfectly good AppleScript solution.
There are *daily* posts showing the power available through the integration of APpleScript and shell tools; I thought this is perfectly well suited to this list based on that, and am happy to provide examples to help you or anyone else through this learning curve.
I didn't mean to intimidate by using foreign terms; I was explaining, for anyone who cares, how the tool Exiftool was developed, but your response made it clear to me that this was about as relevant as me saying "this Scripting Addition was developed using blah blah blah..." - it wasn't relevant to the question, so I apologize for muddying the waters.
>
>>>>my philosophy is that if you're comfortable writing code then a command line tool should be pretty easy.
>
>I'm not sure that philosophy is shared by everyone on this list. The AppleScript philosophy, in part, is that you should be able to learn one scripting language to control a multitude of Applications and technologies.
I've never seen that stated before - AppleScript is glue that ties many systems together, including GUIs, various shell languages, other scripting languages, etc. Idon't think it's meant to be "vanilla AppleScript or nothing". But even with your description I think this tool fits perfectly - Applescript to control ExifTool, which is one of the multitudes of applications available for scripting. It's just an app, there's no other scripting language to learn. Think of a command line tool as being very similar to using a third-party Scripting Addition - in fact this is why (I thnk) we see fewer Scripting Additions today, and more talk of command line tools on this list.
I'm not trying to be combative Ed, several folks at LA Times have used this tool to great effect in the past (via Vicky McCargar) and I thought I would continue to share what I believe is the best tool for the job. With a very small leap it would be useful to you and others too.
>
>Also, it's a pet peeve of mine when AppleScript is referred to as "code". By definition the word "code" implies a communication that is designed to be understood by a select group. That may describe Perl and other scripting and programming languages, but not AppleScript!
Well you can be peeved by that all you want but it's a perfectly common use of the term; this is scripting, and a boddy of expressive commands in any scripting or programming language is referred to as code. Code does not imply "cryptic" in this context.
Sorry I seemed to upset you. I think you'd be most impressed by the power and ease of the tool I suggested, and I'm 100% positive it's in scope of this list, but I'll avoid stepping on your toes in the future.
_______________________________________________
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