![]() ![]() You can batch process files, rename and resize multiple images, or fetch Web pages and manipulate the results. ![]() You can use it to set your system to boot up with certain apps open in a particular way, right down to the size, location and content of each window. Even Microsoft uses it, he says (for work on developing Office for Macintosh).īut AppleScript is also well suited for the desktop. Soghoian estimates that four out of five "top-tier" Apple customers use AppleScript for serious automation - his examples include The New York Times generating daily stock charts and software developers testing applications. ![]() at the very start of the script) rather than on a per-project level to avoid the error execution error: Aperture got an error: Can’t get folder naming policy "Project Name".AppleScript's appeal is that it can control both your operating system and your applications, easily passing information among them. One important lesson that was hard to learn is that exportSetting and folderPolicy need to be set in the context of the entire library (i.e. Import importFolder by referencing into proj Set importFolder to exportFolder & "/" & name of proj Set imageSel to every image version in proj where flagged is trueĮxport imageSel naming folders with folderPolicy using exportSetting to exportFolder set exportFolder to (choose folder with prompt "Choose an export folder") Set folderPolicy to folder naming policy "Project Name" Set exportSetting to export setting "JPEG - Original Size" I got it working in the end (everything except deleting the original images after exporting and reimporting but that I can simply do manually by flagging or color-coding all images the script will handle). Naming folders with folder naming policy "Project Name" using export setting ¬ Assuming this is valid, then it might be able to export all images in all projects at once: tell application "Aperture" to export every image version in every project of library 1 ¬ ![]() On a separate note, it looks like (from you script) the export command can be passed a collection of objects as its direct parameter, which you’re doing with export its every image. In fact, projects will be shorthand for every project, so this should already be defined in the way that you want, and simply removing this line completely should be sufficient. Is problematic, because you're attempting to redefine a class object that belongs to AppleScript. Therefore, the following line: set projects to (get every project) multiple) elements that are all of type project. In that case, there will almost certainly be a plural element form named "projects" already defined, which would refer to a collection of (i.e. I don't use Aperture, so I can only take an educated guess:įrom the error message, I can be reasonably sure that project is an AppleScript object, specifically an element that, from your script, I'll assume belongs to a library object. I guess the problem is with set projects to (get every project) but I can't find any examples online from which to figure out what else to write here. However, when I try to run this script, I keep getting the error apertureExportImport.applescript:704:712:Įxecution error: Aperture got an error: Can’t make into type project. "JPEG - Original Size" to (choose folder with prompt "Choose an export folder") Repeat with i from 1 to count of projectsĮxport its every image version naming folders with folder naming policy ¬ I think I almost have the first part, exporting all images. To retain those, I'm trying to write an Apple script that exports all images (with adjustments applied) in my library and reimports them into the same project before deleting the original. Mylio has a great import tool that carries over almost all of the library structure and metadata but loses some of the adjustments. With macOS Catalina dropping support for Aperture, I need to move my library to a different application. ![]()
0 Comments
Leave a Reply. |