site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com On Apr 7, 2011, at 9:18 AM, Darrin Cardani wrote:

On Apr 6, 2011, at 6:24 PM, Rainer Standke wrote:

...

should one supply a custom, Apple-issued creator code for an FxPlug bundle?

Nope. The UUID in the Info.plist is sufficient.

...

Also, my bundle gets built with just the regular folder icon - is there something I can do to have it have the plugin icon?

That's a good question. I see this, too. I've asked internally and will let you know what they tell me.

The plugins take on the default icon due to their extension, so supplying a creator won't make a difference. When I've wanted to specify the plugin icon, I've done so by applying a custom icon to the bundle using a target script that runs after the rest of the plugin is built. Here's what I've used. Please note that the source icon is a data fork based resource file containing a 'icns' #-16455 resource. steve ------------------------------------- my $BUNDLE = "$ENV{BUILT_PRODUCTS_DIR}/$ENV{WRAPPER_NAME}"; my $SRCICON = "$ENV{PROJECT_DIR}/path/to/icon.rsrc"; my $DESTICON = "$BUNDLE/Icon\r"; # copy the custom icon to the target's bundle, renaming it to "Icon\r" along the way `rm -f "$DESTICON"`; `ResMerger -srcIs DF -dstIs RSRC "$SRCICON" -o "$DESTICON"`; # make the copied icon file invisible `/Developer/Tools/SetFile -a V "$DESTICON"`; # mark the bundle as having a custom icon `/Developer/Tools/SetFile -a C "$BUNDLE"`; _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... This email sent to site_archiver@lists.apple.com