<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:itunes="http://www.itunes.com/DTDs/Podcast-1.0.dtd">
	<channel>
<title>Otto&#x27;s Garage</title><link>http://homepage.mac.com/jkevinwolfe/otto/index.html</link><description>Mac Automator Mechanics</description><dc:language>en</dc:language><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:rights>Copyright 2005 Kevin Wolfe</dc:rights><dc:date>2006-01-05T06:10:48-05:00</dc:date><admin:generatorAgent rdf:resource="http://www.realmacsoftware.com/" />
<admin:errorReportsTo rdf:resource="mailto:jkevinwolfe@mac.com" /><sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
<lastBuildDate>Thu, 05 Jan 2006 06:26:53 -0500</lastBuildDate><item><title>Spark adds shortcuts to call your Automator apps.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2006-01-05T06:10:48-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/index.html#unique-entry-id-292</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/index.html#unique-entry-id-292</guid><content:encoded><![CDATA[<div class="image-left"><img class="imageStyle" alt="Left" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry292_1.png"/></div>Automator gives use so many ways to launch it: workflows, applications, contextual plug-ins, startup items etc. Well, here's another: With <a href="http://chezjd.free.fr/Creation/logiciel.php?id=3&lang=1" rel="self">Spark</a> you can set up hotkeys to launch apps. These can be single or multiple keys. It also offers the ability to program in AppleScripts to a key. I haven't played much yet, but it also looks like you can launch your Automator apps on waking from sleep, when you log out, and when the screensaver activates. You can also assign hotkeys so your apps can only be called up from within an app. I see a lot of use for setting up my TextEdit Automator Apps this way. Spark can also launch documents, so you can probably directly launch Automator workflows as well. The app is fairly intuitive. Double click on a list on the left and you can create a hotkey. Best to use hotkeys with multiple presses, since single presses are more likely to interfere with existing hotkeys. To make sure, just check the menu to see if a shortcut is already assigned.<br /><br />]]></content:encoded></item><item><title>Combine Mail Messages action works.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-12-30T09:41:46-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-291</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-291</guid><content:encoded><![CDATA[There's a lot of talk that the Combine Mail Messages action fails every time. Not true. I haven't had it fail yet. The key is you must put a Display Mail Messages Action before it in the workflow. <br /><br />You'll find other useful actions quirks <a href="page3/page1/page1.html" rel="self">here</a>.]]></content:encoded></item><item><title>Hiding files.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-12-23T11:28:32-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-290</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-290</guid><content:encoded><![CDATA[Automator can hide files for you. It's a 1 action workflow:<br /><img class="imageStyle" alt="HideFiles" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry290_1.png"/> <br />Save this as a Script plug-in. Highlight the file you want to hide and control click to call up the workflow. This puts a period in front of the file name. The file will be grayed and then disappear when the finder is launched next. To hide the file immediately, you can follow this in the workflow with a <a href="page3/page8/page8.html" rel="self">Run Shell Script</a> action to hide finder items.<br /><br />The file will be in the same folder, just invisible. To view it, you'll need to to create a shell script that will show it. I have a show and hide action in my script menu and can call up these files anytime. Security is not flawless, but it's a simple step that can hide a few private files right on your desktop. They also become invisible to Spotlight.]]></content:encoded></item><item><title>Replacing existing files.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-12-23T05:05:12-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-289</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-289</guid><content:encoded><![CDATA[Both the Move Finder Items action and the Copy Finder Items action have a "replace existing files" option. It doesn't make the actions redundant, as it may seem. When you check this, it replaces the existing files in the destination folder. So basically it determines whether is will overwrite a file with that same name or not.]]></content:encoded></item><item><title>Saving workflow PDFs.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-12-23T04:32:40-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-288</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-288</guid><content:encoded><![CDATA[Though Automator is all about simplicity, some of my experimental workflows can push 20 actions. "Reading" the workflow to see what it does is harder than reading code. These workflows seem fragile and occasionally an action will get misplaced and I can't easily figure where it went. That's where having a PDF printout comes in handy. When done building the workflow, just press Apple-P, click the PDF button, and choose Save As PDF. This creates a printout of the actions, insertions and order. You can maintain a notebook of hard copies of your important workflows or keep electronic versions to figure out what went where.<br /><br />One of the other issues with Automator is that sometimes these workflows that were run a lot in experimenting as you built, seem to rely on old action caches that are incorrect and throw off the workflow. (One of mine would crash each time it reached a certain action.) From a printout, you can easily rebuild a virgin copy of the workflow. ]]></content:encoded></item><item><title>Getting the Log to appear.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-12-22T06:37:29-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-287</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-287</guid><content:encoded><![CDATA[The log can be useful for troubleshooting your apps, but it's not a convenient part of Automator to get to. To make it a little easier, go to the View menu and choose Customize Toolbar. Drag the log icon onto your toolbar. Now when you want to see the log, just click the button on the toolbar. Now the problem is that the log in down into the doc and not readable. Click the window plus button on the top left of Automator and window and log will both be repositioned to both be visible.]]></content:encoded></item><item><title>Shrinking your Automator apps.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-12-19T04:51:07-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-286</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-286</guid><content:encoded><![CDATA[Many are shocked to find a workflow converted to an app can be substantially larger than the workflow itself: Somewhere around a meg or 2. One of my simple apps weighed in at 856K. That doesn't seem that large, but the workflow itself is only 8K. Mail a few of these to someone and you may be over their email size limit. <br /><br />Why so large? When Automator builds an app, it follows a generic file structure. Inside the app package are some files you most likely will not use. If you control-click on the app's icon and open the Contents folder and the Resources folder, you'll find the "Iproj" folders. These are a basic mac app structure in 15 different languages. Most of us only need the English folder. If your app is written on a Mac using another language, you might need that language's Iproj folder to, but the rest are likely to be unnecessary. You can drag all these files to the trash. When I removed these from the app mentioned above, it shrunk to 184K. Note to delete only the excess iProj folders, nothing else. <br /><br />And of course, you can use the Move to Trash action to automate the process of removing these files from your Automator apps.]]></content:encoded></item><item><title>Mass Mailing</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-12-15T05:05:38-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-285</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-2.html#unique-entry-id-285</guid><content:encoded><![CDATA[I'm happy to report that Automator is not a good Spam tool. I'm sure apple designed it that way. But for many of is, there are legitimate reasons why you would want to send an email to more than one person or why you would want to resend the same email. Maybe you send the same informational email out on a regular basis. Or maybe you send out a newsletter from your Mac to multiple recipients. We've already the discussed Automator's limitation of not being able to send existing mail messages, but don't let that stop you from putting the power of mail to use. As email becomes the preferred method of business communication, Automator's Mail actions will become more and more useful.<br /><br />First off, you <strong>can</strong> send an existing message. It's just not in your drafts folder. There are two ways to get content in a New Mail Message action. The first is to put the action in a workflow and type the email there. You can open the workflow and modify it before sending. The other is to pass a TextEdit document to the action. <br /><br />Get Specified Finder Items (set it to the document)<br />Get Contents of TextEdit Document<br />New Mail Message<br /><br />The text (but not images) will appear in the body of the email. This allows you to modify the text document so you don't have to modify text in the workflow. If you want the document itself attached to the email:<br /><br />Get Specified Finder Items (set it to the document)<br />New Mail Message<br /><br />Now the document is an attachment. Using TextEdit, you have the option of saving and sending at RTF, Word, Html, Word XML, RTFD (with images) or a WebArchive (with images). <br /><br />Another option, is to send a PDF. The formatting is more stable than a TextEdit rtf or a Word doc. Apple already built this workflow for you. Open the TextEdit document and press Apple-P. This calls up the Print dialog. Click the PDF button and choose Mail PDF. The disadvantage of this method is that you can't pre-address. But you can create your own pre-addressed workflow that with turn your document into a PDF. It is called up from the same list in the print dialog. The workflow is:<br /><br />New Mail Message<br />Send Outgoing Messages<br /><br />Then save this as a Printer plug-in. You can pre-address this to a group or individuals, set the subject line and add body text. If you'd like the option to modify anything before sending, check the Show Action When Run option. <br /><br />One other feature of automator is that you have two ways to mass mail: send one email to everyone. Or send an individual email to each person. To send one email to everyone, click on the Address Book icon in the New Mail Message action and choose your group. This is faster, since only one email is sent.<br /><br />But if you want to send an individual email to everyone on the list, you have the option of adding an individual greeting before the text with the Group Mailer action. It also is not obvious you're sending the email to more than one person. (Using BCC will not hide this.) The disadvantage of this method is that Mail will take the time to send 100 emails individually if there are 100 in the group. When you have an attachment, this can take a while. The workflow is:<br /><br />New Mail Message<br />Group Mailer<br />Send Outgoing Messages<br /><br />If you want to greet each recipient in the body of the email, but don't want "Dear" in front of their name, make sure "Add Greeting" is checked, but leave the greeting field blank. <br /><br /><br /><br /><br /><br /><br /><br />]]></content:encoded></item><item><title>Poster disguised as a contact sheet.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-29T06:52:46-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-283</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-283</guid><content:encoded><![CDATA[<div class="image-left"><img class="imageStyle" alt="Contact" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry283_1.png"/></div>Playing around with Automator, you'll find the actions that look useless at first glance are some of the best. Like the New PDF Conact Sheet action in the PDF Library. It produces such a high-quality image that you can print it as a poster. (It appears images are 300 dpi.) Whatever images are passed to the action are laid out in a PDF. You have the choice of how many images you want to fill the sheet: <br />3 columns - 12 images<br />4 columns - 20 images<br />5 columns - 30 Images<br />6 columns - 48 images<br /><br />The easiest way to layout your poster is to create a Poster album in iPhoto and drag the specified number of images there. Then change the width of the album window to match the column width. This shows you how your sheet will look. Just drag the images to rearrange them. Square format will fill the most whitespace, but original size can be fun to work with. When the workflow calls these images from iPhoto using the Ask for iPhoto Items action, they will remain in this order.<br /><br /><div class="image-left"><img class="imageStyle" alt="Poster" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry283_2.png"/></div>It takes  a while to build this PDF. And it can be up to 250 megs when finished. You can shrink it by opening it, clicking Apple-P, clicking the PDF button and choosing Compress PDF from the list. This can shrink it by up to 90% and still retain decent image quality. Your workflow can post-process this poster with any of the PDF actions. You also can open the image in Preview and add captions with Annotate. <br /><br />The downside is that the poster will have some edges at the right and bottom you'll have to trim. And you're stuck with the white background.<br /><br />So what's the poster quality like? I'll report back as soon as I get this one from Kinko's. <br /><br />I also should note that the net's current "life poster" frenzy was caused by <a href="http://www.mikematas.com/2005/01/how-to-make-life-poster.html" rel="self">Mike Mattas</a>. <a href="http://automatoractions.com/files/lifeposterfortiger1.2.html" rel="self">Jim Heid</a> has created an Automator action that does this as well. These posters hold more images than the one above and are printed through Mac's Kodak print service. Just thought I'd give you some more options.<br /><br /><span style="color:#ff0b20;">UPDATE:</span> Got the color poster back. It's about 18 by 24 and printed on a thin-but-sturdy polypropylene. The cost was $24 dollars at Kinkos. Result: Print quality is good. A few photos look a little grainy, but all are sharp. Looks like if you opt for the 4x5 layout, images should be at least 2mp and if you're opting for the 3x4 layout, images should be at least 3mp. The disappointing thing is the printed surface is a little more fragile than I hoped. Probably equivalent to a paper print, but still, it's waterproof.<br /><br />Staples offers a similar service at about the same price. <br /><br />]]></content:encoded></item><item><title>Catch up on your SOAP.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-21T09:15:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-255</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-255</guid><content:encoded><![CDATA[<div class="image-left"><img class="imageStyle" alt="runweb" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry255_1.png"/></div><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">A powerful feature of Automator is the Run Web Service action. You may have overlooked only because it looks complex to use. It can do great things, like check the weather, traffic and stock quotes for you. To play with it, just go to the Automator Library and drag the Run Web Service action into an empty workflow. Test button. This should give you the current traffic conditions on I-280 in California.<br /><br />Here's something a little more practical. Change the action to these settings:<br /><br /></span><p style="text-align:center;"><br /></p><p style="text-align:left;"><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Don't worry about the Test field. Now click the Test button. (You'll need to be web-connected.) This gives you the current price of Coca-Cola stock. And since the true indicator of the status of life on Earth is the current price of Coke stock, this can be really useful. The number in the Test field is what the action passes to the next action.<br /><br />How does it work? It's called SOAP. It's a Microsoft invention for Fetching web data. The action creates a request, sends it and returns the result.<br /><br />What's the practical application? You could follow this with a New Message and Send Outgoing Message action to email data to your cell phone. If you save it as an iCal plugin, the process could be done automatically. This could also be used in a workflow to create a screensaver that changes hourly. Or hourly appended to a TextEdit document to keep a running track of data. Since you can do a lot more than just stock prices, I'm sure you'll com up with a few.<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="http://xmethods.net/" rel="self">XMethods</a></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> has more for you to play with. Please tell us at the Garage of your successes so we can share them. </span></p>]]></content:encoded></item><item><title>Search added to Otto&#x27;s Garage.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-16T06:01:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-249</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-249</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Thanks to the folks at FreeFind, we've added a search feature to Otto's. It's updated daily, so you should get a very accurate return. As the information here grows it will make it a lot easier to find what you're looking for.</span>]]></content:encoded></item><item><title>Shared workflows: Troubleshooting.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-14T05:32:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-238</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-238</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Sharing your workflows and apps is a kind thing to do. However, once an Automator project leaves your machine, a lot can go wrong. Here are the common culprits of workflows that don't work. Ask:<br /><br />1. Is Tiger installed? (10.4) Automator wasn't there on earlier OSs.<br />2. Is it the latest version? Many Automator fixes have taken place since the first version of Tiger.<br />3. Is the app the workflow needs installed? If QuickTime Pro is not there, the actions that come with QuickTime Pro will not work on QuickTime.<br />4. Is the app the workflow needs the latest version? Older versions will not have Automator actions. This includes apps  from Apple, like the iLife suite (iPhoto, iTunes, etc).<br />5. Are all third party actions needed installed on their computer? If you've installed and have included the Convert Tracks action in your workflow, then they must install it on theirs too. If it's a workflow, they get a warning message telling them which action is missing. If an app, no such luck.<br />6. Does your workflow contain any AppleScriplets that require UI Scripting to be enabled? It will need to be enabled on their machine as well. An Automator helper app to do most of the process is </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="page3/page4/page5/page5.html" rel="self">here</a></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">.<br />7. When the workflow is run, which step has the red x below it? This tells you where the workflow is failing.<br />8. When the workflow is run, have them check the Automator log for more details on what's going wrong. The red error message will be the most helpful to you.</span>]]></content:encoded></item><item><title>Irritated by all the theme changes at Otto&#x27;s?</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-11T14:01:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-241</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-241</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">This one is tolerable. I think I leave it alone for a while.</span>]]></content:encoded></item><item><title>Workflow and app packager.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-10T07:25:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-105</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-105</guid><content:encoded><![CDATA[<div class="image-left"><img class="imageStyle" alt="testflow" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry105_1.jpg"/></div><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Automator offers a poor man's development environment. But that doesn't mean distribution has to look rinky dink. Even though you may be sharing your workflows with just a friend or colleagues, it may get passed on to others. Professional packaging makes it easier on the user(s) and you, since you won't get as many "now what do I do with this?" emails. Here's a very simple way to share your workflows and apps that's right under your nose. Specifically, on your Dock. <br /><br />TextEdit offers a great way to share apps with an interactive document. You can easily put images, icons, screenshots, documentation files, workflows and apps into a new TextEdit document just by dragging them where you want to appear in the document. The links feature in TextEdit allows you to add active Web links. And what's really cool is that the user can launch a workflow or app right from the document by clicking on it. <br /><br />TextEdit offers some very capable layout options. You can use any font available on your system, color it and add shadow. You also now can create tables and lists in TextEdit and color the page. You have many tools that allow you to layout instruction with your app very logically. A lot more logically that many professional apps you download. This is especially useful if the user has to install more that one file. So instead of having some unknown files pop up on their desktop, those you share your workflows with will see the box above.<br /><br />If you're including further documentation with your file, it's best to save it in TextEdit format, not PDF. TextEdit has a habit of opening PDFs within the page and not showing them as icons. <br /><br />Can you create a workflow in the document that installs another workflow in the document to the users applications folder? This proves tricky, but I think it can be done. More after a little tinkering.<br /><br /></span>]]></content:encoded></item><item><title>Buy our crap.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-10T06:00:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-223</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-223</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">If you think Otto's Garage is a slick looking and highly informative site, apparently (judging by the ranking in Google) you're not alone. But I have to come clean, it's not a massive effort of thousands of top coders and tech writers secretly funded by a huge grant from Steve Jobs. It's just me. I'm learning Automator by reading the </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="http://discussions.info.apple.com/tiger.automator/" rel="self">Apple board</a></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">, googling my fingertips off, and by writing my findings on the prestigious </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="http://bbs.applescript.net/viewforum.php?id=22" rel="self">MacScripter</a></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">. If the site looks slick, it's because it's developed with </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="http://www.realmacsoftware.com/" rel="self">RapidWeaver</a></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">, the first rapid development environment for Mac (or any OS for that matter). When I say this site's main purpose is for me to go to the Web and look up what I've forgotten from yesterday about Automator, that's the truth. If the writing is good, I'm glad you think so. I have been graced with the luck of being a full-time professional writer since I was asked to leave college. <br /><br />This labor of love has become a success in just over a month. A lot of hours go in. The response from readers is a wonderful reward. But it doesn't pay for the Turkish coffee I sip at 4 am while I obsessively writing this. I've decided not to put banner ads up on Otto's Garage. The reality is, they don't pay enough for readers to put up with their annoyance.<br /><br />So I've added a "Buy Books" tab to the menu. I figure if you're going to buy books on Automator, AppleScript and UNIX, you may as well get steered towards the best titles. If you click on the book's icon to buy it, Amazon gives Otto's Garage a little kickback for it. Guess I should also mention I put a link to my eBook </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="http://booksthatdontgobad.com/EditinginiPhoto.html" rel="self">Serious Editing in iPhoto 5</a></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> there as well. Not that it has anything to do with Automator. I just want to sell eBooks.<br /><br />By buying the book through this site, I get a little something, you get a good reading material that will further your Automating and most likely you will get it at a better price than you can anywhere else. Everybody wins. Okay, maybe your local bookstore looses out. If they're one of those big chains, who cares. But if it's a small place owned and run by an ex-hippie named Rainbow with a mood ring through her nose, at least keep buying your Feng Shui books there. We need to keep those places in business. And ask her if she has a daughter named Moonbeam and how she's doing. I think I dated her once.<br /><br />Thanks for doing your business at Otto's,<br /><br />J. Kevin Wolfe</span>]]></content:encoded></item><item><title>Renaming Tricks</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-06T21:06:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-153</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-153</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">The Rename Finder Items feature is very flexible. It seem like it only has a few options. But you just have to out-think its limitations. You can save most the following workflows to applications and you can just drop files onto the icons to change their names.<br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; "><br />Change Extension</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> This changes both htm and html to txt. Useful for revealing html code. To change an xml extension, you only need one action and set Find field to "xml". Note this is just changes the extension, so a jpg is still a jpg, even if you name it tif.<br /></span><p style="text-align:center;"><img class="imageStyle" alt="renamhtml2txt" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry153_1.png"/><br /><br /><br /></p><p style="text-align:left;"><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">Rename for Web </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">This will turn file names websafe. The first Rename finds underscores and changes them to dashes. The second finds spaces and changes them to dashes. The third lowers the case of all letters, including the extension.</span><br /></p><p style="text-align:center;"><br /><img class="imageStyle" alt="WebName" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry153_2.png"/><br /><br /><br /></p><p style="text-align:left;"><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">Deleting Extensions</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> Deleting extensions sometimes reveals what's inside a package. This one is to reveal the images inside a TextEdit rtfd file. You can also delete ".app" to get access to the innerworkings of applications. The Copy Finder Actions is placed here to make sure you don't destroy working apps or files. Just make sure you don't drop a file already in the desktop. It needs to be in a different location so it doesn't overwrite the file.<br /></span><br /></p><p style="text-align:center;"><img class="imageStyle" alt="droprtfd" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry153_3.png"/><br /><br /></p><p style="text-align:left;"><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">Renaming a File You Don't Know the Name of</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> This is more useful in a workflow when you don't know the name of the finder item. In these instances the Replace Text option will not work. The Make Sequential option will rename any file but will also but a "-1" after the name. The second Rename action will delete it by leaving the replace field untouched. This will only work on one file .</span><br /><br /></p><p style="text-align:center;"><img class="imageStyle" alt="ChangeName" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry153_4.png"/></p>]]></content:encoded></item><item><title>Congratulations&#x2c; it&#x27;s a domain.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-06T21:05:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-154</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-154</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Nope. Site hasn't moved. But now you can access Otto's Garage through an easier-to-say url: ottosgarage.us</span>]]></content:encoded></item><item><title>Ways to save your workflows.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-06T21:01:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-204</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-204</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Apple has set up workflows to launch in many different ways. This gives us a lot of flexibility in crafting workflows for many different uses. Here's a quick list of the ways you can save your workflows. (If ya got any other bright ideas, email them my way. It would be nice to figure out how to do one when Mac quits.)<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">as a Workflow </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">This is the basic Automator script that calls up Automator when it's double clicked. This is the easiest and best while developing and for on-the-fly creation. When saved, you can click on the workflow's icon on the desktop or from any folder and it launches in Automator. You press the run button and you're off.<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">as a Finder Plugin</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> Puts your workflow on the contextual menu. Control click on a file or folder and call up your workflow from the Automator option. Your file will be processed by the workflow. Makes your workflow available for launch at any time without having to click the workflow's icon. ex: Change a file name to Web compatible.<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">as an iCal Plugin</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> Launches your workflow via a calendar event. ex: clean desktop and empty trash every morning at 3 am.<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">as a Folder Action</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> The workflow processes any file moved to the folder. ex: copy file to public folder on iDisk<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">as an Image Capture Plugin</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> Launches when a camera is connected to the Mac. Useful for your own photo downloads routine. ex: burn raw files to disk and save them in iPhoto on import.<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">as a Print Workflow Plugin</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> The workflow will reside in the PDF menu of the Print window. When launched the files to print are converted to PDF and then sent to the workflow. ex: compile iPhotos into a single PDF and email it.<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">as a Script Menu Plugin</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> The workflow will appear as a menu item under the Script menu which will appear on your toolbar. Makes your workflow available for launch at any time without having to click the workflow's icon. ex: Change the desktop picture quickly.<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">as an App</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> The workflow becomes a standard Mac app. Can be kept on the dock and launched with a Mighty Mouse button. It will launch from the desktop or any folder it's in. Also allows you to drag and drop files onto it for processing. ex: convert JPEGs dropped onto the app to TIFFs.<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">as a Startup App</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> Workflow is saved as an App and then set to run when the computer is turned on or when the user logs in. This is set in Preferences/Users/Startup. ex: get inbox mail and combine text into one file and save to iDisk.<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; font-weight:bold; ">as a Mail Rule</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> </span><span style="font:11px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">(thx to </span><span style="font:11px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="http://mac-help.com" rel="external">Ric Latham</a></span><span style="font:11px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">) </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Workflow is saved as an app. An new mail rules is set to Run Applescript with the following script: <br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; color:#2e8d2e;">tell application "your workflow.app" <br />activate <br />end tell <br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">The app is triggered by a qualifying email. ex: Received email with keyword in subject line starts app that mails set images to a set address.<br /></span>]]></content:encoded></item><item><title>The 2 confirmation icons.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-05T05:07:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-164</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-164</guid><content:encoded><![CDATA[<p style="text-align:center;"><img class="imageStyle" alt="ConfirmIcon1" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry164_1.png"/><img class="imageStyle" alt="ConfirmIcon2" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry164_2.png"/><br /></p><p style="text-align:left;"><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">The confirmation screen offers you a choice of icons. Two is still considered a choice, isn't it? Click on the icon and it changes. Might be a way to modify this to custom icons, but realize that it would only work on your computer and not when your workflow is shared. <br /></span></p>]]></content:encoded></item><item><title>Saving as PDF</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-02T05:29:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-110</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-110</guid><content:encoded><![CDATA[<div class="image-left"><img class="imageStyle" alt="PDFServices" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry110_1.png"/></div><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Automator doesn't come with an action that will save your files to PDF. But PDF services offers a way to do this. Any workflow stored in the PDF Services folder (HD/Library/PDF Services) will have the file or files passed to it converted to PDF first. So if you "print" a TextEdit doc or bunch of iPhoto photos, they will be saved as one PDF before the workflow initiates. The PDF Services menu already has some workflows in it. <br /></span><p style="text-align:center;"><br /></p><p style="text-align:left;"><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Save your workflow as a Printer plugin. Your workflow will appear on the Print page of every app that allows printing, most notably TextEdit, Preview and iPhoto. </span></p>]]></content:encoded></item><item><title>Fixes for Automator in 10.4.3</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-02T05:24:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-123</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-123</guid><content:encoded><![CDATA[<span style="font:13px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Posted these on MacScripter yesterday. I'm not sure how complete the list is. Found them on a Brazilian Website. I used Automator to filter every paragraph with the word "Automator" in it:<br /><br />- Ask for Confirmation Automator fix <br />- Fixed issue with Create Archive Automator action <br />- Fixed issue with Import Audio File Automator action <br />- Fixed issue with Automator and Workflow documents saved as a plug-in <br />- Fixed Automator 'Show Action When Run' and clipped win??@$!! issue <br />- Improvements to Automator Framework <br />- Fixed Automator issue where missing actions may cause a problem <br />- Fixed issue with 'New QuickTime Slideshow' Automator action <br />- Fixed issue with 'Find Finder' Automator action <br />- Fixed issue with Automator and Spotlight action Show When Run window <br />- Fixed issue with the Automator action, Copy Finder Items <br />- Fixed issue where Automator may not find GIF or PNG file types <br />- Fixed Automator issue where Rename Finder Items may not rename non-ASCII <br />- Fixed Automator action issue when downloading files from a web page <br />- Fixed problem where Automator action Scale Images may not scale to correct <br />- Improvements to Automator Converter <br />- Improvements to Automator action - New iCal Events <br />- Improvements to Automator action - Create Archive <br />- Improvements to Automator action - Build Xcode Project Automator <br />- Improvements to Automator action - Connect To Server <br />- Fixed Automator issue where Rename Finder Items did not prepend '0' <br />- Improvements to Automator action - Import Audio File <br />- Corrected issue with sorting and viewing Automator actions <br />- Fixed issue where deleted Workflows in Automator would still appear <br />- Fixed problem with Automator and one step workflows <br />- Automator Cocoa Action improvements <br />- Fixed issues with the Automator ColorSync profile action <br />- Fixed Automator action - Print Keynote Presentation </span>]]></content:encoded></item><item><title>Find and Filter Fixed?</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-11-01T07:02:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-117</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-1.html#unique-entry-id-117</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Tiger 10.4.3 was released about 2pm Cupertino time yesterday afternoon. It appears that the Find and Filter actions now work correctly  in Apps as they do in workflows. Tests on the Find Finder Items and Find Mail items work fine in apps now. Filter Finder Items works as well. Haven't tested all Find and Filter actions yet. Keep you posted.</span>]]></content:encoded></item><item><title>You&#x27;ve got no mail.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-10-30T04:50:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-58</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-58</guid><content:encoded><![CDATA[<div class="image-left"><img class="imageStyle" alt="BodyMailer" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry58_1.png"/></div><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">To take some of your frustration out of Automating a mail message, I'll admit the deep dark secret: Automator can't send existing emails. It can only send a new message. So if you have a message in your Drafts folder, Automator can't see if as an "outgoing message" to send. Of course, I wouldn't bring this up without a workaround. </span><br /><br /><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Save this workflow as an app. Then, drop a TextEdit file onto the app's icon. The New Message dialog will appear with the TextEdit document's text as the body of the email. Note that any image or text styling from the document will not transfer. At the end of this workflow you can add a Find Address Book Items action and a Group Mailer action to mass mail the email. And you can use UI Scripting in a Run AppleScript action to fill in the To: and Subject: lines if you want to further automate things.</span>]]></content:encoded></item><item><title>Pimp my workflow: 1. Swiping icons for your Automator apps.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-10-30T04:30:00-05:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-93</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-93</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">It's not that Automator's standard icons for workflows and apps look boring after creating so many workflows. It's just that they're not distinctive enough to easily find. These standard icons are important visual cues, since we depend on the visual for quick reference. They tell us what kind of file a workflow is, but when you have 5 Automator apps on your dock, forget it. You can't remember which is which. This is where distinctive icons really help out.<br /><br />You can copy any icon on your mac and use it as an icon for your workflows and apps. These aren't really custom, but they can be much more recognizable than the standard icons. Here's how to do it. All you're doing is copying and pasting a reference to the icon.<br /><br />From the Finder, click once on an icon that you want to swipe. <br />Click Apple-i<br />Click on the icon on the top left of the info screen.<br />Click Apple-C<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">From the Finder, click once on the icon of the workflow or app you want to replace.<br />Click Apple-i<br />Click on the icon on the top left of the info screen.<br />Click Apple-V<br /><br />Here it may seem this cumbersome, but once you have the hang of it, it's a very intuitive process. The one issue is that if you resave an app or workflow, the standard icon is back. You'll just have to paste it again. Later, I'll cover cheap and simple ways to create your own icons. <br /><br />The other issue is that this method only make the switch on your machine. If you share the app it will have the standard Automator app icon on other machines. It appears can can't get a custom icon to be included within a shared workflow...but you can put a custom icon in an Automator app. More in the next episode of Pimp my workflow.</span>]]></content:encoded></item><item><title>Uncorking the Data Flow</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-10-21T17:25:00-04:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-54</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-54</guid><content:encoded><![CDATA[<div class="image-left"><img class="imageStyle" alt="FolderFlow" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry54_1.png"/></div><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Corking of the Data Flow is one of the key causes of Automator apps to fizzle. The Data Flow is shown by the little connectors on the right side of each action. These tell you what type of information an action sends and needs to receive. For the most part, this information is not files, but text. Yes, nothing advanced, just text like: word strings, styled text, numbers, URLs, Address Book data, iCal events, and most importantly; file references. So, it's not really a PNG image on the root of your hard drive that Automator it passing, but a reference to it that looks like this: <br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><br /></span><img class="imageStyle" alt="Reference" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry54_2.png"/><br /><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><br />Automator can do more than one action to the same files by passing these item references on to the next action. A down arrow in the Data Flow means that the information passed should be understood by the following action. <br /></span><br /><div class="image-left"><img class="imageStyle" alt="PhotoFlow" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry54_3.png"/></div><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Sometimes these references are different, but Automator still says they're compatible. This usually indicates that Automator has a conversion action it can do to make the files compatible. It can change the information to the format needed or take the reference and convert the files as needed. <br /></span><br /><div class="image-left"><img class="imageStyle" alt="BlockedFlow" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry54_4.png"/></div><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">When you get red, this is a warning sign the Data Flow is blocked. Automator can't take this information and pass it or convert it. Most likely, but not always the flow will be stopped. There are times you'll want to stop the Data Flow yourself. Your workflow may do an action and then do another action that requires a different set of references. <br /></span><div class="image-left"><img class="imageStyle" alt="IgnoreResults" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry54_5.png"/></div><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Many actions have a little triangle on the input Data Flow. If you click this, you can set whether the data passes or not. The default is that the data from the previous action is passed to the current action. If you want to ignore the data, click on Ignore Results from Previous Action. <br /><br />One of the issues with Automator is that there's no built-in provision to take information from the start of the workflow, ignore it while you're doing an action that requires other data and then use the information from the start of the workflow at the end. The trick is to save the data and then call it up later. There are two third party freeware actions can do this. However, if you share your workflow, app or plugin, the receiving computer must have these actions installed to work. <br /><br />There's a simple way you can do this in Automator. To store references, use the Copy to Clipboard action from System Library. Place this after the results you need to store. Then to call it up, place a Run AppleScript action in the workflow with the following scriptlet before the action that needs the data from earlier in the workflow:<br /></span><br /><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; color:#2e8d2e;">--Return Clipboard Contents to Data Flow<br /></span><span style="font:12px Verdana, serif; color:#2e8d2e;">return (the clipboard)<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">This takes the information stored on the clipboard and puts it back in the Data Flow. </span><br /><br /><br /><br />]]></content:encoded></item><item><title>Creating nested Folders.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-10-21T16:15:00-04:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-53</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-53</guid><content:encoded><![CDATA[Creating new nested folders can be done with Automator and a little trickery. Here's the action: <br /><p style="text-align:center;"><img class="imageStyle" alt="FolderNester" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry53_1.png"/><br />The EscherSketch here is that that folder called "Folder" doesn't exist until the workflow is run, so you can't call up a folder that doesn't exist in the last three actions. The trick is to create a new folder called "Folder" on the desktop, call it up in the necessary actions and then delete it. Having the reference to it and its location is all Automator wants.<br /><br />You can add a Move Finder Items action afterwards to move this where you like. But it must be created in a defined location, like the Desktop or Hard Drive, before moving it. You can also extend this structure, either by creating an action for each folder needed or by using Copy Finder Items and Rename Finder Items actions to put folders full of folders inside folders full of folders.<br /><br />You can custom name folders in each workflow by using the option: Show workflow when run. Don't to offer to much leeway or you'll wind up having to click return for the creation of each folder. </p>]]></content:encoded></item><item><title>Summoning ghost files.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-10-21T06:28:00-04:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-41</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-41</guid><content:encoded><![CDATA[Writing Automator workflows is sometimes plagued by the problem of calling up a specific file that won't exist until an earlier part of the workflow has been run. So if a workflow creates a file called "imagetmp.jpg", the image has to exist before you can reference it later in the workflow. It can't be listed in the Get Specified Finder Items action while you're writing the workflow because it doesn't exist yet.<br /><br />This Catch 22 has a simple workaround: Rename a file "imagetmp.jpg", put it where you want Automator to look for it. Then use the reference to it in the Get Specified Finder Items action. You can delete the file once you have the reference to it in the workflow. Automator has the name of the file to be created, even when it doesn't exist yet. It will rewrite over the file each time the workflow is run.]]></content:encoded></item><item><title>Otto&#x27;s Stash: Where Otto hides your files.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-10-17T12:57:00-04:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-49</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-49</guid><content:encoded><![CDATA[Many times Otto works with covertly with files. Probably the most obvious is when a PDF is created. Use most any of the PDF actions and you'll be quickly confused because the files you make look don't seem to exist. Otto keeps these in a private folder that Spotlight can't see. What good does this do for us if we don't have normal access to the files? Fortunately Automator keeps a reference to these files.<br /><br />So if you call up the Watermark PDF action, follow it with Move Finder Items and set the location as the desktop. Now when you run the workflow, the file will appear on the desktop as a PDF with gibberish for a name. If you add a Rename Finder Items action to the workflow, you can assign it a less-random name.<br /><br />So where is Otto's hiding place? It's a good idea to check it every once and a while to make sure you haven't filled it will a billion files in your workflow experiments that you thought weren't working. To view the folder from the Finder, click the Go menu, choose Go to Folder and then type <strong>/private/tmp</strong>. Most likely it's safe to dump any files in here in the trash. ]]></content:encoded></item><item><title>Getting Automator to jump through loops.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-10-13T10:54:00-04:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-25</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-25</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">The loop: the basic unit of a computer program, is something Automator can't do, or can it? Automator can in fact do loops.<br /></span><div class="image-left"><img class="imageStyle" alt="LoopSS" src="http://homepage.mac.com/jkevinwolfe/otto/files//page0_blog_entry25_1.png"/></div><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">This one is useless, but it works. The workflow asks the user if they want to run it, runs it, and then runs itself. Since I haven't figured out a way to create an "until" statement in Automator to keep the loop from running forever, this one gives the user an out by asking if they want to run it again. The "action" of this loop is an inaction: it just pauses for a second. The Pause action could be replaced with the meat of a workflow. Don't know what you'd do with it. But as Einstein said: "I just came up with a simple formula to release untold energy. You guys in the Manhattan Project want to see if it's worth looking into?" <br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">There are a few tricks to getting this to work. The Run Workflow list will not contain the Loop workflow. Save the workflow before you add the actions. Call the workflow up in the Run Workflow action by clicking on Other and call it up from it's location. Then save it again.  Before running, it's a good idea to exit Automator and restart holding down the option key to clear the cache. <br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><br />Much happy fusion to you.</span><br />]]></content:encoded></item><item><title>Poor traveling companion.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-10-10T15:57:00-04:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-12</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-12</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Automator is the programming environment I've been waiting for. It's simple, quick and easy. I can throw together an app idea in a few minutes, and email a working copy to a friend.<br /><br />But there's a problem with portability: to use any action, it must be installed on the computer the app is run on. So if you have a horde of 3rd party actions you use in your workflows, they won't work on another Mac unless all the actions are installed on that computer. And as we all know, installing actions is beyond the comfort level of the casual Mac user. An though the actions that come built into Automator are extensive, your workflows become limited without the extras. So Automator workflows don't travel well. Sad that Apple didn't rig Automator apps so they could have these action compiled with them. But it's really an intellectual property issue, not a technical issue. And after all Automator is primarily a personal programming environment. <br /><br />So what can we do about it? You could use AppleScript to create an installer that would install the actions as well as your app. But this is almost as much work and requires as much coding as writing an XCode app. The easier option is to find AppleScript snippets that mimic these actions. Written AppleScript is contained within the Run Applescript actions in the workflow or app itself. <br /><br />Some of the 3rd party actions available are so simple they can be mimicked in a few lines of code. You can control click on the actions themselves to show the package contents and possibly see the code that was used. But most developers compile this into machine code that can't be interpreted. (Some of the extra actions that Apple has created are readable.) Fortunately there's a huge number of AppleScripts on the Web that you can learn from and modify for your needs. <br /><br />UI scripting is an extension of AppleScript that allows you to control apps much the way Automator does and allows you access to menu commands in most apps. UI scripting puts a huge amount of programming power in a few simple lines of code that most anyone can figure out without learning AppleScript. Here's one I figured out: </span><br /><br /><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; color:#2e8d2e;">tell application "System Events"<br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; color:#2e8d2e;">tell application "Stickies" to activate<br />tell process "Stickies" to keystroke "v" using command down<br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; color:#2e8d2e;">end tell<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">Paste this into the Run Applescript action you'll find in the Automator library. Click run and this will popup a new Sticky note and paste whatever's on the clipboard in it. Great. But there's one problem: any time you see System Events in AppleScript UI scripting needs to be turned on. UI scripting is off by default. Most likely there's an AppleScript or Shell script that can do that, but it's well beyond my skill. Here's a workaround I modified from a script I found on the Bayport NY Fire Department site:<br /><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; color:#2e8d2e;">tell application "System Preferences"<br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; color:#2e8d2e;">activate<br />set current pane to pane "com.apple.preference.universalaccess"<br />display dialog "Make sure \"Enable access for assistive devices\" is checked for this app to run"<br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; color:#2e8d2e;">end tell</span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><br /></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">This gem calls up the Universal Access pane in Preferences and flashes a dialog that tells the user to make sure the box that enables UI scripting is checked to run the app. This can be inserted into a Run AppleScript action, then saved as an app called "Double Click to Setup the Application." It's easy and you didn't trespass into anyone's system to do it. It's already compiled as an app </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="assets/EnableUIScripting.dmg" rel="self">here</a></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">.<br /><br />I'm compiling a </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="page3/page4/page4.html" rel="self">compendium</a></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> of simple scriptlets that will make applications and workflows more portable. Feel free to send me any you come up with that you'd like to share.<br /></span>]]></content:encoded></item><item><title>A simpler introduction.</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-10-07T06:15:00-04:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-9</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-9</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">The simple introductions to Automator seem confusing. Maybe it's because Automator can do so much that these intros are too far reaching to be understood by someone looking at Automator for the first time. </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="page2/page2.html" rel="self">Auto 100.5</a></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> (not as complex as 101) shows how to build a simple Automator workflow and save it as an application. That's it. But maybe it will whey your appetite to learn more.</span>]]></content:encoded></item><item><title>Welcome to the Garage</title><description></description><dc:creator>jkevinwolfe@mac.com</dc:creator><dc:subject>Tinkerings</dc:subject><dc:date>2005-10-05T09:05:00-04:00</dc:date><link>http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-0</link><guid isPermaLink="true">http://homepage.mac.com/jkevinwolfe/otto/files/archive-0.html#unique-entry-id-0</guid><content:encoded><![CDATA[<span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">A side project of my work with iPhoto and my eBook </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="http://www.booksthatdontgodbad.com" rel="self">Serious Editing in iPhoto5</a></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> has become my "learning" of programming with Automator. I use the word learning loosely. Automator is so easy, anyone can now make Mac utility programs. Many tasks that required tedious work clicking, processing and opening a file in another app before importing it back to the previous app are now history, thanks to Otto. This blog and site will be the diary of my findings and a place to post the apps I've made. <br /><br />In the Toolbox, you'll find a list of </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="page3/page1/page1.html" rel="self">Action Quirks</a></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; ">. These are undocumented incompatibilities and non-functions. There's also an </span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "><a href="page3/page4/page4.html" rel="self">AppleScriptletapedia</a></span><span style="font:12px 'Lucida Grande', LucidaGrande, Verdana, sans-serif; "> of code you can insert in the Run AppleScript action to extend the function of Automator. Downloads has Automator-created freeware.<br /><br />Happy motoring,<br /><br />J. Kevin Wolfe</span>]]></content:encoded></item></channel>
</rss>