{"id":186,"date":"2008-12-19T15:51:56","date_gmt":"2008-12-19T20:51:56","guid":{"rendered":"http:\/\/vgable.com\/blog\/2008\/12\/19\/undocumented-automatorframework-goodness-actions-library\/"},"modified":"2008-12-19T15:51:59","modified_gmt":"2008-12-19T20:51:59","slug":"undocumented-automatorframework-goodness-actions-library","status":"publish","type":"post","link":"https:\/\/vgable.com\/blog\/2008\/12\/19\/undocumented-automatorframework-goodness-actions-library\/","title":{"rendered":"Undocumented Automator.framework Goodness: Actions Library"},"content":{"rendered":"

In Leopard, Apple introduced AMWorkflowView<\/code><\/a> and AMWorkflowController<\/code><\/a>, which let you easily add automator-editing capabilities to your application (modulo bugs!<\/a>)<\/p>\n

Obviously, for editing a workflow to be useful, you need to be able to add actions to it. And to do that, you need to be able to browse and search actions. But the current Automator.framework has no official support for doing this.<\/p>\n

But there are undocumented private APIs, which Automator.app (link launches it)<\/a> uses…<\/p>\n

How to Find Them<\/h3>\n

class-dump<\/a> is an amazingly useful command-line tool that lets you generate headers from a compiled Objective-C binary. Download it, and point it at \/System\/Library\/Frameworks\/Automator.framework\/Automator<\/code>, to see everything Automator.framework really<\/em> lets you do.<\/p>\n

Instant Library Panel<\/h3>\n

The most useful definition I found was,
\n@interface NSApplication (AMLibraryPanel)
\n- (void)orderFrontAutomatorLibraryPanel:(id)sender;
\n@end
<\/code><\/p>\n

Calling [NSApp orderFrontAutomatorLibraryPanel:nil];<\/code> will show a panel with the same action-library view Automator has.
\n<\/strong><\/p>\n

This is what I’m using right now in IMLocation<\/a> to let people find actions for workflows. I don’t like the idea of using private APIs. But I like the idea of implementing my own AMLibraryView<\/code> replacement even less. It would be a lot<\/em> of work to make it as good as the real thing. Any differences give users a fractured experience — one way to do something in Automator, another in my program. And I would get dismal ROI, because I expect Apple to expose this functionality in the (near) future.<\/p>\n

(I also wouldn’t be so bullish on using private APIs if I didn’t have workarounds in place right now. The only way orderFrontAutomatorLibraryPanel:<\/code> gets called is if a user presses a “Show Actions” button on the toolbar. That same toolbar has an “Open in Automator” button that opens the worklfow in Automator, where they can edit it without bugs. So even if orderFrontAutomatorLibraryPanel:<\/code> stopped working tomorrow, users could still do everything they could before — albeit less elegantly).<\/p>\n

Looking Just Like Automator<\/h3>\n

I don’t recommend doing this<\/strong>, but I’ve been able to embed an AMLibraryView<\/code> in an NSSplitView<\/code> next to an AMWorkflowView<\/code>, to get a more Automator.app-like appearance.<\/p>\n

Here’s how I did it, given the IBOutlet<\/code>s workflowViewAndLibrarySplitView<\/code> which is an NSSplit<\/code> view with an AMWorkflowView<\/code> in one side, and the other side’s view connected to the outlet workflowLibraryView<\/code>,<\/p>\n

[workflowViewAndLibrarySplitView replaceSubview:workflowLibraryView with:[[AMLibraryPanel sharedLibraryPanel] _libraryView]];<\/code><\/p>\n

Will put the library view inside your split view.<\/p>\n

Of course this screws up orderFrontAutomatorLibraryPanel:<\/code>. And I would not expect it to work in two windows. And it’s using an underscore-private method of an already private and undocumented API. That’s just to too risky for me; so I stick with the panel. It gets the job done with one line of code, and that’s good enough for me.<\/p>\n","protected":false},"excerpt":{"rendered":"

In Leopard, Apple introduced AMWorkflowView and AMWorkflowController, which let you easily add automator-editing capabilities to your application (modulo bugs!) Obviously, for editing a workflow to be useful, you need to be able to add actions to it. And to do that, you need to be able to browse and search actions. But the current Automator.framework […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,38,3,5,4,93],"tags":[260,261,258,75,73,255],"class_list":["post-186","post","type-post","status-publish","format-standard","hentry","category-cocoa","category-interface-builder","category-macosx","category-objective-c","category-programming","category-reverse-engineering","tag-amlibrarypanel","tag-amlibraryview","tag-amworkflowcontroller","tag-amworkflowview","tag-automator","tag-bad-idea"],"_links":{"self":[{"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/posts\/186","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/comments?post=186"}],"version-history":[{"count":0,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/posts\/186\/revisions"}],"wp:attachment":[{"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/media?parent=186"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/categories?post=186"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vgable.com\/blog\/wp-json\/wp\/v2\/tags?post=186"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}