looks like the built in “open with” behavior only works for gui apps:
is there any reason not to enable the display/usage of this option in a plugin when “standalone plugin” is selected as a target?
looks like the built in “open with” behavior only works for gui apps:
is there any reason not to enable the display/usage of this option in a plugin when “standalone plugin” is selected as a target?
I can’t comment on whether it makes sense or not to enable that option in a standalone plugin, but you could put something like this in the “Custom PList” field to achieve the same effect:
<plist>
<dict>
<key>CFBundleDocumentTypes</key>
<array>
<dict>
<key>CFBundleTypeExtensions</key>
<array>
<string>{first_extension}</string>
<string>{second_extension}</string>
<string>{third_extension}</string>
</array>
<key>CFBundleTypeName</key>
<string>{first_extension}</string>
<key>CFBundleTypeRole</key>
<string>Editor</string>
<key>CFBundleTypeIconFile</key>
<string>Icon</string>
<key>NSPersistentStoreTypeKey</key>
<string>XML</string>
</dict>
</array>
</dict>
</plist>
replacing {first_extension}
, {second_extension}
, and {third_extension}
by what you want.