mountainlion,wwdc2012
Latest
Apple updates OS X to protect 'advanced UNIX users' from Shellshock
Although OS X is among the systems listed as vulnerable to the recently-uncovered Shellshock / Bash security flaw (still not sure what that is? Let us explain.), Apple has said it isn't a problem for most users. For those potentially vulnerable due to enabling certain UNIX services, 9to5Mac reveals the company has just pushed patches for the Mavericks, Lion and Mountain Lion versions of its desktop operating system. You can download the updates from Apple's website now, and it should be available via software update soon. [Image credit: Robert Graham, Twitter]
Apple selling $20 Lion and Mountain Lion redemption codes for older Macs
Apple has begun selling redemption codes for OS X 10.7 Lion and OS X 10.8 Mountain Lion on Apple.com. Each code costs US$19.99 and allows the buyer to redeem that code inside the Mac App Store so they can download the OS. At first, the move may seem an odd one since anyone can download OS X 10.9 Mavericks for free, but as TechCrunch notes, the sale of the older OSes compensates for the lack of availability of those versions of OS X on the App Store: We did some asking around about the thinking behind this particular arrangement and the nut of it is that Apple only offers one version of OS X at a time for purchase on the Mac App Store: the current one. But OS X Mavericks, though it does support some devices as far back as 2007, still has a lot of compatibility gaps for old Macs. If you've previously purchased either Lion or Mountain Lion, these are freely downloadable from the Mac App Store, but this new arrangement allows customers who may not (for some reason) have owned either one to purchase new copies. This will also allow users who have old Macs running Leopard or Snow Leopard to upgrade to 'new-er' versions of OS X. After a buyer purchases a code, they will receive it via email. Buyers can then copy and paste that code into the Redeem section of the Mac App Store and their download will commence.
Apple updates OS X to 10.8.5 with WiFi, Mail and screen saver fixes in tow
Apple has just rolled out version 10.8.5 of OS X in order to remedy a number of recent issues with Mountain Lion. The update packs fixes for WiFi file transfers over 802.11ac, message display issues in Mail and unwanted screen saver appearances, along with the usual less-specific tweaks. If you haven't already seen the App Store notification in your Dock, a quick trip to that repository should reveal the fix after a required restart.
Tim Cook: 28 million copies of Mountain Lion shipped, more than any other Mac release
Cupertino has been known to share a stat or two during its WWDC keynotes, so it's hardly a surprise that the company just dropped some sales figures for its Mountain Lion. According to Tim Cook, 28 million copies of the OS have shipped, making it the best-selling Mac release of all time. Cook also said that about 35 percent of users have updated, compared to less than five percent for Windows 8. And Apple wasn't just talking Mountain Lion to brag; those numbers were part of a build-up to announcing the latest desktop-based software: OS X Mavericks. Hit up that link for more info. Follow all of our WWDC 2013 coverage at our event hub.
Twitter for Mac 2.2.1 brings Notification Center support, various bug fixes
It's certainly been a long time coming, but the latest version (2.2.1) of Twitter for Mac finally brings support for Notification Center in OS X Mountain Lion. Aside from the side-pane pings for your @replies and DMs, a number of fixes have been implemented that should stabilize your experience some more. Most notably, Growl users on Lion and Mountain Lion can enjoy receiving notifications again. The update is available directly from the Mac App Store right now, so hit the source link if you're interested.
Extract App Resource Icons with AppleScript
Whether I'm preparing for a demo or writing an article, blog post, book, or technical documentation, I often find myself performing the same set of repetitive steps. I need to navigate into an app's packaged resources folder, find one or more icon files, occasionally convert them to PNG and scale them, and add them to my document, Keynote presentation, etc. Fortunately, this doesn't need to be a manual process each time, thanks to the following AppleScript. Creating the Script 1. Launch AppleScript Editor (in /Applications/Utilities) and create a new script document. 2. Enter the following script into the document. NOTE: If you have any trouble following along, you can download the completed script here. 3. Run the script from AppleScript Editor, save it as an app, or add it to your script menu. Running the Script When you run the script, you're first asked to select an app from which to extract icons. Make your selection and click Choose. The script looks inside the app's /Contents/Resources folder for any files with an extension of .icns. If multiple files are found, it allows you to select the ones you want to extract. The default is all of them. Next, the script gives you the option to extract the .icns files themselves, or PNG versions. Click the button to make your choice. If you click the PNG button, then you're given a choice of sizes to create. You might not need the full sized icons, for example. You might only need 256x256 icons. Depending on the options you chose, the script extracts the .icns files, or it converts the .icns files to PNG and scales them, as needed. You're notified when the icons have been extracted, and they're displayed in the Finder for you. Now you can simply drag them to your document, presentation, file, etc., and you're good to go! Happy Scripting!
Upcoming Macs may have 802.11ac WiFi, according to OS X Mountain Lion beta code
Code in the latest 10.8.4 beta version of Mountain Lion discovered by a 9to5 Mac tipster shows OS X support for 802.11ac WiFi, meaning next-gen Macs might contain the tech. Also dubbed 5G, 802.11ac brings speeds as high as 1.3Gbps thanks to beamforming, while also offering more range and robustness compared to its 802.11n predecessor. To date we've seen oodles of routers packing the still-uncertified wireless format, but only a single notebook with the tech has passed through our doors -- the Asus G75VW gaming notebook. That might change with a reference to the standard in the "WiFi-frameworks" folder in Mountain Lion's latest beta, 10.8.4, which was recently sent to developers. Of course, until we see a real Cupertino product packing such a radio, it's just that -- code. [Image credit: 9to5 Mac]
Triggering AppleScripts from Calendar Alerts in Mountain Lion
AppleScripts are great tools for increasing your daily productivity. They're even better when they can be set to run unattended, at night, on weekends or during downtime. In Lion, iCal included a handy option for attaching a script to a calendar event. Just create an event, add a Run Script alarm, point it to the desired script and you're good to go. Things changed in Mountain Lion, though. Presumably for security reasons, the Run Script alarm option was removed from the Calendar app. Despite its removal, however, there are still some ways you can trigger scripts from Calendar events. iCal event alarm choices in OS X 10.7 Lion Calendar event alarm choices in OS X 10.8 Mountain Lion Use Automator to Trigger Your AppleScript Although Apple removed the Run Script alarm option in the Calendar app, Automator's ability to save Calendar Alarm workflows wasn't removed. And, since Automator workflows can trigger AppleScripts, they offer a quick and easy workaround for scheduling scripts. Start by launching Automator and creating a new Calendar Alarm workflow. To schedule an Automator workflow, choose the Calendar Alarm template. To Trigger an AppleScript App If your script is an app, you just need to set the workflow to launch it. Add the Launch Application action to the workflow. From the application popup menu, choose Other... and navigate to your saved AppleScript app. The Launch Application action can be used to launch an AppleScript app. To Trigger AppleScript Code If you'd rather not create an app (an app + your Automator workflow means more files to manage), you can embed compiled AppleScript code right within your workflow. Find the Run AppleScript action and drag it to the workflow. Then, insert the desired script code into the action. The Run AppleScript action can be set to run code embedded in your Automator workflow. To Schedule the Script Once you've got your workflow configured, go ahead and save it. Automator automatically adds it to an Automator calendar (which is created if it doesn't exist yet) in the Calendars app. An Open File alarm is added to the event and set to run the workflow. Now, adjust the start date of the event as needed, put it on a repeating schedule, etc. Open File alarms are used to trigger Automator Calendar Alarm workflows. Use AppleScript to Create a Scheduled Event If you create an event in the Calendars app and add an Open File alarm, you should find that you're unable to select a saved AppleScript app. You can select a compiled AppleScript file, but this is essentially useless because when the event triggers, the Open File alarm simply causes the compiled script to open in AppleScript editor. Not what you need. What you really need is to open a saved script app. AppleScript to the rescue. To work around the limitation, just run the following script. It asks you to select a saved AppleScript app. It then creates an event at the current date and time on an AppleScripts calendar, which it creates if it doesn't exist already. The script then adds an Open File alarm to the newly created event and sets it to open your selected script app. Yep, that's right. Although you can't manually set an event to open a saved AppleScript app, you can script the process. NOTE: You can download the complete script below here. So, there you go. A number of workarounds for triggering scripts from Calendar events in Mountain Lion. So, schedule away! Happy Scripting!
OS X Mountain Lion v10.8.3, Security Update 2013-001 now available
Apple has released OS X Mountain Lion 10.8.3 and the first security update of 2013. The update includes a number of good improvements including: The ability to redeem iTunes gift cards in the Mac App Store using the built-in camera on a Mac. Boot Camp support for installing Windows 8 and Macs with a 3 TB hard drive. Various fixes for issues that cause a URL to quit apps unexpectedly, that might cause Logic Pro to become unresponsive and stuttering audio on 2011 iMacs. The update also includes Safari 6.0.3. The update is available via Software Update or through the Mac App Store. You can find the full support document on Apple's support site.
OS X 10.8.3 update arrives with official Boot Camp support for Windows 8
We've some good news to share for Mountain Lion users: OS X 10.8.3 is now available for download. As you'd expect, the new software brings a number of fixes and enhancements, but in a delicious twist of irony, the most substantial may very well be for Windows users. That's because version 10.8.3 introduces official support for Boot Camp with Windows 8, and it also brings compatibility for Boot Camp on Macs with hard drives larger than 3TB. Meanwhile, OS X users will benefit from Safari 6.0.3 and the ability to redeem iTunes gift cards in the Mac App Store by using the built-in iSight camera. OS X 10.8.3 is also said to resolve an audio stutter issue for 2011 iMacs and correct any unresponsive plugins that Logic Pro users might've noticed. You'll find the complete list of improvements after the break, but while you read, you might wanna dig into that Apple menu and get downloading.
Tips for Troubleshooting Automator Workflows
Automator's great for streamlining time consuming and repetitive tasks on your Mac. It's easy. Just launch it, find a few actions, and string them together to form a workflow. Then, run your workflow anytime you want to perform that series of tasks again. What happens if your workflow doesn't run as you expect, though? Finding and solving problems in Automator is often easier said than done. Suddenly, the simple tool that's supposed to make your life easier has become a real pain in the neck. This week's post covers some things you can do to troubleshoot a finicky Automator workflow, track down the problem, and hopefully solve it, so you can get back to work. 1. Run Saved Workflows in Automator Automator workflows are saved and run in a variety of ways - as apps, iCal alarms, print plugins, and more. When a saved workflow encounters a problem, however, it may be next to impossible to figure out what went wrong. This is because saved workflows don't really include any diagnostic tools. In some cases, the workflow may even fail silently, without alerting you that something is wrong. Your only indication of a problem may be a lack of the end result you were expecting. Not very helpful, especially in a longer multi-action workflow. When you encounter a problem with a saved workflow, your best bet is to open up the workflow in Automator, and try running it there. By doing so, you'll gain access to some of the techniques described below. 2. Fake Workflow Input When you run a workflow app or plugin within Automator, you may see an alert indicating that the workflow will not receive input. An Automator Input Alert for a Text Service Workflow This is because, often, saved Automator workflows expect input for processing. For example, a workflow app may expect dropped files or folders as input, a service workflow may expect text as input, or a print plugin may expect PDF files from the print system. In any case, just dismiss the alert and add an action to the beginning of the workflow to retrieve the required type of input. If your workflow processes files, for example, add a Get Specified Finder Items action. If your workflow processes text, add a Get Specified Text action. Whatever you add, just be sure to remove it once you're finished troubleshooting. Get Specified Text at the Beginning of a Text Service Workflow 3. Check Action Results Automator works by passing information to actions for processing. Most actions perform a very specific function. As such, they accept specific types of information as input. And, they produce different types of output. The New TextEdit Document action, for example, wants text as input. It then adds this text to a new TextEdit document, and passes the document as output for further processing. Often, when a workflow fails or produces an undesired result, it's because actions aren't receiving or producing the expected types of information. To diagnose this problem, click the Results button beneath each action in your workflow. Then, when you run the workflow, you can see exactly what information is being passed from action to action. Suppose, for example, I have a workflow that should take the contents of a text file and add it to a new TextEdit document. I may try creating my workflow with the following actions: Get Specified Finder Items - Configured to get a text file Filter Paragraphs - Configured to look for non-empty paragraphs New TextEdit Document All the actions appear to link up properly, and the workflow may even run without an error. But, the result is not what I want. Rather than the content of the text file being added to the new TextEdit document, the path of the document is added. A Misbehaving Text Workflow An Undesired Workflow Result By displaying the result area of each action in the workflow, I can see that a file path was passed to the Filter Paragraphs action as input. I can also see that the same file path was output by the action, rather than the paragraphs I was expecting. This tells me that there's something wrong with the Filter Paragraphs action. Action Results Indicate Potential Problems Checking the action's description area provides additional clues. It tells me the action expects text as input, not files. Action Descriptions Specify Input and Output Types So, in this case, the fix is to insert an action that outputs text, rather than files, before the Filter Paragraphs action. NOTE: Surprisingly, Automator doesn't include an action for reading text from a file. There are third-party actions available that can do this. Or, as a workaround, you can try using the Combine Text Files action, which receives one or more files as input and outputs their text content. 4. Check Automator's Log Checking the results of an action doesn't always tell you what went wrong. You may glean a little more information by consulting Automator's log area. Press Command+Option+L or choose View > Log to display it. When you run a workflow, the log area tells you which actions ran, and often indicates problems that were encountered along the way, such as an action that wasn't supplied with the appropriate type of input. Automator's Log Area Indicates Successes and Failures Sometimes, the log tells you that information was converted from one type to another. This is because, in some cases, Automator tries to make incompatible actions work together. This doesn't always work, however, and can result in an error. So, be on the lookout for failed conversions. 5. Step Through Workflows Running a workflow and checking action results is great, but it's even more useful to check the results of each step of your workflow as it happens. You can do this by stepping through the workflow step by step. Click the Step button in the workflow's toolbar or select Workflow > Step from the menu bar. Automator's Step Button The above techniques may not resolve every problem you encounter with Automator, but they will certainly help you to more easily identify solutions for some. Happy Scripting!
AppleScript Productivity > Create OmniFocus Followups from Contacts
As an OmniFocus for Mac user, it's important that I can quickly create tasks at any time, in any app. OmniFocus makes this pretty easy, by providing integration with OS X Mail, a keyboard shortcut for clipping content in apps such as Safari, a system-wide Quick Entry window and a Services menu item. One feature OmniFocus lacks, however, is direct integration with the Contacts app. Suppose I am in Contacts, for example, and I need to schedule a followup phone call or email to one of my clients? Sure, I could bring up the Quick Entry window and enter the task, but I want something a bit more streamlined. I can accomplish just what I need by writing some custom AppleScripts. The following two examples demonstrate how to write AppleScript-based plug-ins for the Contacts app, which add OmniFocus followup options right into the email and phone number popup menus of your contacts. Note: If you have any trouble following along, you can download both of the scripts outlined in this post here. Creating the Email Followup Script Plug-In 1. Quit the Contacts app. 2. Launch AppleScript Editor in /Applications/Utilities and create a new script document. 3. Insert the following code: 4. Save it as a script named Contacts > Email Follow Up with OmniFocus.scpt into the ~/Library/Address Book Plug-Ins folder in your home directory. If this folder doesn't already exist, go ahead and create it. Saving the Script into the Address Book Plug-Ins folder The Address Book Plug-Ins folder in ~/Library Creating an OmniFocus Email Followup Task To give your new plug-in a try, launch the Contacts app and go to a contact. When you hover over the email address field, it becomes highlighted. Click it and choose Follow Up with OmniFocus from the popup menu that appears. The OmniFocus Quick Entry window appears, and it contains an email follow-up task for the contact, including a note with a clickable email link. Creating the Phone Call Followup Script Plug-In The process to create phone call followup plug-in is essentially the same. 1. Quit the Contacts app again. 2. Create another AppleScript Editor document. 3. Insert the following code this time: 4. Save the script as a script named Contacts > Phone Call Follow Up with OmniFocus.scpt into the ~/Library/Address Book Plug-Ins folder in your home directory. Creating an OmniFocus Phone Call Followup Task Launch the Contacts app again. This time, click on a contact's phone number field and choose Follow Up with OmniFocus from the popup menu. Again, OmniFocus' Quick Entry window is displayed. This time, it contains a phone call follow-up task and a note containing the phone number. Voila, you now have quick OmniFocus integration with Contacts, and you can use it anytime you need to schedule a follow-up. Until next time, Happy Scripting!
AppleScripting Dates > Elapsed Time Calculator
Since Valentine's Day is this week, I thought I would take this opportunity to share an AppleScript I wrote to calculate how long my wife and I have been married. With this baby, I'll never be accused of forgetting how long it's been when our anniversary rolls around. The script determines the elapsed time between now (the current date and time), and a prior date and time (such as our anniversary). It then displays the result in seconds, minutes, hours, days, weeks, months and years. Note: If you're into the whole "traditional anniversary gift" thing (I'm not), you can find a list of gift categories on Wikipedia. Creating the Script Note: If you have any trouble following along, you can download the complete script here. 1. Launch AppleScript Editor in /Applications/Utilities and create a new script document. 2. Insert the following code: Some notes about this script... * I used some of the number calculation handlers in the Essential Subroutines section of macosxautomation.com, although, I made some slight modifications to them for the script. If you're interested in learning more about AppleScript, there are some other useful handlers there, as well, and I encourage you to check them out. * The final display dialog sets as its icon the FavoriteItemsIcon icon file, which is embedded in the CoreTypes bundle in /System/Library/CoreServices. It is, coincidentally enough, a heart. Using the Script To use, just run the script within AppleScript Editor, or save it as an application to be launched and run whenever you wish. First, the script asks you to enter a date and, optionally, a time. Next, the script does its calculations and displays the result. Just take a screenshot of the dialog and send it along to your significant other. Until next time, Happy Scripting and Happy Valentine's Day Week!
OS X camera RAW compatibility update adds Sony RX1, Nikon D5200 and more
Apple's 'Digital Camera RAW Compatibility Update 4.04' is out, and although we rarely report on these frequent releases, there are a few notable shooters named in this particular version. Available for Macs running OS X Lion 10.7.5 and above, or Mountain Lion 10.8.2 and above, the update now allows RAW snaps from Sony's compact Cyber-shot RX1 and Nikon's D5200 SLR to play nice with Aperture and iPhoto software. Plenty of other cameras are also on the changelog: Leica's X2, V-Lux 4 and D-Lux 6, as well as Pentax's Q, K-30, K-5 II and IIs. A quick trip to the App Store will get you on the latest version and have you cooking something up in Aperture before you can say "medium-rare." Bon appétit.
AppleScripting Notification Center > Scheduling Do Not Disturb
Mountain Lion's Notification Center is great for keeping you in the loop, but it can be a huge distraction when you need to get stuff done. Sometimes, a little peace and quiet is all you need to stay productive. As you may know, iOS 6 includes a handy Do Not Disturb feature, which can be turned on to disable notifications. It can even be set to automatically enable/disable itself at scheduled intervals. Mountain Lion also lets you disable Notification Center. Just open Notification Center and drag down to access a Show Alerts and Banners toggle switch. Note that this is a temporary setting, and disabled notifications automatically re-enable at midnight. Unlike iOS 6, though, Mountain Lion doesn't give you an option for enabling/disabling notifications on a schedule. At least, it doesn't provide a built-in option for this. With a little customized help from AppleScript, Automator, and the Calendar app, it is possible. In this post, you'll create two Calendar Alarm Automator workflows, which can be configured to run at scheduled times to enable or disable Notification Center alerts and banners. Note: If you have any trouble following along, you can download the completed AppleScripts and Automator workflows here. Building a Workflow to Enable Do Not Disturb (i.e. Disable Notification Center Alerts and Banners) 1. Launch Automator (in your /Applications folder) and create a new Calendar Alarm workflow. 2. Search the action library for the Run AppleScript action and drag it to the workflow area. 3. Replace the pre-filled AppleScript code in the Run AppleScript action with the following: The script writes to Notification Center's property list file and enables Do Not Disturb mode. It then quits and relaunches Notification Center in order for the change to go into effect. 4. You're finished building the workflow, so go ahead and save it as Enable Do Not Disturb. 5. When you save the workflow, Automator puts it where it needs to go (the ~/Library/Workflows/Applications/Calendar folder). The Calendar app launches and a new event is created in an Automator calendar, which Automator creates if it doesn't already exist. The event should be configured with an Open File alarm that's set to run the workflow. Schedule the event for the desired time, such as every weekday morning at 6 AM. Now, every time the event occurs, the alarm should launch the workflow and Notification Center should be disabled. As I mentioned earlier, Notification Center automatically re-enables each day at midnight. So, if you plan to schedule Do Not Disturb overnight, then you'll need to create an additional event that disables it again at 12:01 AM. Building a Workflow to Disable Do Not Disturb (i.e. Re-Enable Notification Center Alerts and Banners) Now that you've got a workflow to disable Notification Center, you probably want one to re-enable it. 1. Create another new Calendar Alarm workflow in Automator. 2. Search the action library for the Run AppleScript action again and drag it to the workflow area. 3. This time, replace the existing placeholder script in the Run AppleScript action with the following code: This code updates Notification Center's property list file to disable Do Not Disturb. Then, it relaunches Notification Center for the change to take effect. 4. The workflow is done, so save it as Disable Do Not Disturb. 5. The Calendar app should launch again and another event should be added to the Automator calendar. This event should be configured with an Open File alarm that's set to open the Disable Do Not Disturb workflow. Set it to run on the desired schedule, such as every weekday morning at 9 AM. If everything has gone according to plan, you should now have Do Not Disturb workflows that disable and re-enable Notification Center alerts and banners at the desired times. Use your alert-free time wisely. Until next time, happy scripting!
Obscure OS X Mountain Lion bug makes many apps crash
TUAW reader Don McC pointed us to this Next Web write-up about an obscure Mountain Lion crash. If you type File: followed by /// in many apps, they will crash. There are 8 characters in total and the F must be capitalized. I tested this and managed to crash a bunch of apps. Echofon, QuickTime, Safari, and Notes all fell before the 8-character text, although Firefox did not . Most amusingly, when I attempted to open the crash logs in TextEdit, the logs killed the app! So what's going on? Here's what my system log reports: Feb 2 22:18:37 Esopus-Spitzenburg.local TextEdit[8417]: assertion on /SourceCache/DataDetectorsCore/DataDetectorsCore-269.1/Sources/PushDown/DDResultExtraction.c:1576 "CFStringHasPrefix(urlVal, CFSTR("file://"))" failed :wrong extraction: File:/// As the Next Web explains, it's an issue with a built in assertion. Assertions allow programmers to mandate expected behavior, validating input to assure its correctness. In this case, automated data detectors see what appears to be a malformed URL and send off an application exception reporting the internal inconsistency. The exception crashes the application because there's no built-in handler. I tried out the recommended solution (disabling spelling correction and symbol substitution) but it didn't work for me personally. TUAW submitted a bug report to Apple.
20" iMac G4 updated to Ivy Bridge
Apple's iMac went through several design permutations before the company settled on the current "all-in-one computer and display on aluminum arm" configuration. One of the most iconic designs was that of the iMac G4, which held the electronics of the device -- including an optical drive -- in a desktop half-sphere with a 15-, 17- or 20-inch LCD panel suspended on an arm. Modder "Dremel Junkie" (Jonathan Berg) has been bringing classic iMac G4s up to date with new hardware for a while, and his latest work brings a 20-inch iMac G4 into the Mountain Lion era with an Intel Ivy Bridge CPU. The system uses an Intel NUC (Next Unit of Computing) system neatly implanted into the heart of the iMac G4. It's not just as simple as plugging the Intel NUC into the base of the iMac; Dremel Junkie goes through detailed descriptions of all of the steps taken to make sure that this device remains true to the exterior lines of the iMac G4 while providing the latest in high speed I/O. Of course, since the Intel hardware isn't "official Apple," the device is incapable of running Mountain Lion without resorting to a Hackintosh solution. Dremel Junkie used an off-the-shelf copy of Mountain Lion and tonymac's Unibeast/Multibeast install method to get OS X running smoothly. If you have an old iMac G4 sitting around collecting dust and you're handy with a soldering iron and Dremel Moto-Tool, this may be a fun winter project to work on. Two videos are embedded below (about 30 minutes total) that explain the project.
Mountain Lion is king of the OS X jungle
As noted by Macworld UK, Apple's OS X Mountain Lion has clawed its way to the top of the OS X jungle. It was released on July 25, 2012 and as of this past December it's installed on 32 percent of all Macs online. That percentage is according to Net Applications, a web-measurement firm that tracks operating system usage by analyzing visitors to 40,000 websites. That number represents a 3 percent increase for the OS from November, when 10.8 was running on 29 percent of all Macs online. That gain came mostly at the expense of OS X 10.7 Lion, which sank from 30 percent to 28 percent. Mountain Lion also stole one percentage point from OS X 10.6 Snow Leopard, which is now actually in second place, accounting for 29 percent of all Macs. Interestingly, Computerworld has compared Snow Leopard to Windows XP, noting its strong staying power. They attribute this to the stability of the OS and the ability of Snow Leopard to run PowerPC apps. Net Applications doesn't expect any future Mac operating system to ever crack a 50 percent share. That's due to Apple's new annual OS X update cycle. If OS X 10.7 and 10.8 are any indication, Apple should announce the 10.9 beta some time this spring with the official release coming in July.
Preparing high-res icon files with Automator
This week's post is for all those Mac app developers out there. If you're not an app developer yet, it's a new year, and I'm sure becoming an app developer is at at the top of your resolution list. In any case, if you plan to develop apps, then you need to prepare icons for those apps. Apple provides very specific requirements for generating high resolution icons, which you can find listed on the Apple Developer Connection website. In the past, Xcode came with a tool named IconComposer, which could be used to generate icon files. This tool, however, didn't generate high res icon files, so Apple now discourages its use. Instead, Apple provides instructions for generating icons using an iconset, a folder of image files that can be converted to an icon file using either Xcode or the iconutil command line tool. There are, of course, other ways of creating icons. In this post, however, we'll focus on an iconset. To manually generate an iconset folder, you start by creating a square image to serve as your icon. Next, you generate versions of the image scaled to 16x16, 32x32, 128x128, 256x256, 512x512. These scaled versions are to be named as follows: icon_16x16.png icon_16x16@2x.png icon_32x32.png icon_32x32@2x.png icon_128x128.png icon_128x128@2x.png icon_256x256.png icon_256x256@2x.png icon_512x512.png icon_512x512@2x.png You place all of these images into a folder named FolderName.iconset. Then, you can process it with iconutil to generate an icns file. Sure, creating scaled images and processing them isn't too difficult, but it's a lot of repetitive work. If you create icons regularly, it can get tedious. You're probably thinking, surely, Automator can be used to streamline the process. It can. Here, we'll create an application workflow you can run anytime you want to convert an image to an icon file. Let's get started... Note: If you're an iOS developer, feel free to adjust the workflow below accordingly. Creating the Workflow Launch Automator and create a new Application workflow. Next, insert and configure the following actions. Note: This workflow is pretty long and repetitive. It's easy to get lost. If you get stuck, don't worry, you can download the complete workflow here, along with a sample icon image. 1. Ask for Finder Items - Set this action to ask for an image file at least 1024x1024 in size. 2. New Folder - Set this action to create a folder named MyIcon.iconset on your Desktop. 3. Set Value of Variable - From the popup menu in this action, choose New Variable and create a variable named iconset folder. 4. Get Folder Contents 5. Change Type of Images - Set this action to convert images to PNG format. 6. Scale Images - Set this action to scale the image to a size of 1024 pixels. 7. Rename Finder Items - Set this action to name a single item's basename only to icon_512x512@2x. This represents a 1024 image (i.e. a Retina display ready size) when the icon is created. Note that this action's title changes in the workflow to reflect the type of naming, in this case Name Single Item. 8. Duplicate Finder Items 9. Scale Images - Set this action to scale the image to a size of 512 pixels. 10. Rename Finder Items - Set this action to name a single item's basename only to icon_512x512. 11. Duplicate Finder Items 12. Rename Finder Items - Set this action to name a single item's basename only to icon_256x256@2x. 13. Duplicate Finder Items 14. Scale Images - Set this action to scale the image to a size of 256 pixels. 15. Rename Finder Items - Set this action to name a single item's basename only to icon_256x256. 16. Duplicate Finder Items 17. Rename Finder Items - Set this action to name a single item's basename only to icon_128x128@2x. 18. Duplicate Finder Items 19. Scale Images - Set this action to scale the image to a size of 128 pixels. 20. Rename Finder Items - Set this action to name a single item's basename only to icon_128x128. 21. Duplicate Finder Items 22. Scale Images - Set this action to scale the image to a size of 64 pixels. 23. Rename Finder Items - Set this action to name a single item's basename only to icon_32x32@2x. 24. Duplicate Finder Items 25. Scale Images - Set this action to scale the image to a size of 32 pixels. 26. Rename Finder Items - Set this action to name a single item's basename only to icon_32x32. 27. Duplicate Finder Items 28. Rename Finder Items - Set this action to name a single item's basename only to icon_16x16@2x. 29. Duplicate Finder Items 30. Scale Images - Set this action to scale the image to a size of 16 pixels. 31. Rename Finder Items - Set this action to name a single item's basename only to icon_16x16. 32. Get Value of Variable - Set this action to get the iconset folder variable you created way back at the beginning of the workflow. You also need to set this action to ignore its input, so it doesn't continue processing the 16x16px image from the previous action. Select Action > Ignore Image. 33. Run Shell Script - Set this action to pass input as arguments. Then, enter the following command: iconutil -c icns "$@" Preparing the Run the Workflow Before you begin running the workflow, you need an image you can convert to an icon. Note that iconutil requires this image to be square. So, make sure it is. If you really want to be sure it's square, you can insert a Crop Images action between steps 5 and 6, and configure it to crop to 1024x1024, scaling to the shortest side before copping. However, if your image contains transparency, this action will remove it. So, it's best to prepare your starting image as a square. Running the Workflow When you run the workflow, you're first asked to choose an image. Select the desired image and click Choose. The workflow runs, an iconset folder is created on your Desktop and passed to iconutil, which generates an icns file. You're ready to plug your icns file into your app. Now, any time you need to generate an icon, just create a square image and trigger your workflow. Happy New Year and Happy App Developing!
Send Keynote presenter notes to Evernote with AppleScript
We've all been there before. You've prepared a Keynote presentation on the Internet phenomenon of cat videos for your local Mac user group. You've finished editing your slides. You've added presenter notes. Next, you want to extract the notes from your slides and bring them into Evernote so you can look them over and maybe use them as the basis for your forthcoming newsletter article. You open your presentation in Keynote and select File > Export. Then, it happens. You remember that Keynote doesn't have a feature for exporting presenter notes. Sure, you could copy them one by one into Evernote, but that will take a while. Fortunately, you know this can be done quickly and easily with AppleScript. Here's how you'll do it... Creating the Script First, you need to write a script. NOTE: If you have any trouble following along, you can download the complete script here. 1. Launch AppleScript Editor (in /Applications/Utilities). 2. Create a new script document, and enter the following code: 3. Save the AppleScript Editor document in Script format to your Desktop as Send Keynote Presenter Notes to Evernote.scpt. AppleScript Editor documents can be saved as Scripts or Applications. Save your document as a Script. Enabling the Script Menu Next, you need a quick and easy way to trigger the script. You can use the handy system-wide script menu. If it's not enabled on your Mac already, here's how you can turn it on. 1. Choose AppleScript Editor > Preferences... 2. Ensure that the Show Script menu in the menu bar checkbox is selected. Once enabled, you should see a script icon appear in your menu bar. The script menu is turned on in AppleScript Editor's preferences window. Installing the Script Next, you're ready to add your newly created script into the script menu. This way, you can quickly trigger it whenever you're in Keynote with an opened presentation. 1. Go into Keynote. 2. From the script icon in your menu bar, select Open Scripts Folder > Open Keynote Scripts Folder. The script menu provides quick and easy navigation to your scripts folder. 3. Copy the Send Keynote Presenter Notes to Evernote.scpt file from your Desktop into the ~/Library/Scripts/Applications/Keynote folder that opens. The Keynote Scripts folder is created automatically if it doesn't already exist. Running the Script Now that your script is installed, it's ready to run whenever you need it. 1. Open a Keynote presentation containing presenter notes. The presenter notes area is located beneath your slides. If this area isn't visible, choose View > Show Presenter Notes. 2. From the script menu, choose Send Keynote Presenter Notes to Evernote. Application scripts are contextual and automatically appear in the script menu when the target app is frontmost. 3. When prompted, specify whether you would like to extract slide content, in addition to the presenter notes. The AppleScript can extract presenter notes and/or slide content. The choice is yours. The script extracts the slide titles, presenter notes, and, if necessary, the slide content from your opened Keynote presentation. Next, the script reformats the extracted content as HTML, brings Evernote to the front, and creates a new note. An Evernote note containing extracted Keynote notes. Your notes are now ready for review in Evernote on your Mac. Assuming you've got Evernote's iOS app too, your notes are also synced to your iPhone and/or iPad. As you ride the train to work and excitedly begin working on your newsletter article, feel free to share your knowledge of cat videos with the person next to you. Happy scripting!