site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bensyverson.com; s=bensyverson; t=1502560551; bh=tJUnA4DEeSlymBRl0Te/qjA9E+kTlJpCd2vPYl3XI5Q=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=2pMTscms8UYa8Cua+TvvVdh4J/DUDHhQW1csmggcq02vRiiG0zv+0T9hYdAtQzaIi m+VXJOV6Nyh6OEAfslKu40JVEfW5FtydE8gaaG/78RZ4nWC06fi0fWvekKxMBjCHJ5 ItMckuzsa8t7mKiJ5G31ZCbC9F7lm/PJspO+KtdxzYEVcNbkICZXPDpCm6h+FzHeT5 mGFb1yRBzvjEV9Kdd+Q87N0BNmhlbJnOj/6ThyrG9uKB4Kn1+Vz++66mzZwGvST5MS aYu4dKn+z6xvfDYmxwEDbFb4403peFwq21xyyqs2+PYLMMOFpPLMaKPHnIu92G2+w6 gJDQZLTXRLCLw== Darrin, That did help, thanks! Launching it via the Finder made the plugin show up in Motion, although it’s still not listed via pluginkit. Thank you for the background on the template. I get that the XPC is doing some processing for demonstration purposes, but in your opinion, is the XPC the right place for the `addWatermarkTo:` method in production? I ask because my impulse would be to call `validateRegistrationFile` from the FxPlug, and if it’s invalid, draw the watermark within the FxPlug’s `renderOutput:` method. Thanks again, Ben
On Aug 12, 2017, at 12:31, Darrin Cardani <dcardani@apple.com> wrote:
Ben,
If you build the plug-in, the go to the Finder and double-click on the app, does it work after that? I’ve found that between Xcode, Launch Services, and PlugInKit, sometimes there’s a miscommunication. By running it once from the Finder, it seems to fix whatever the issue is.
When we created the template, it was requested that we do some actual processing in the XPC. Doing hardware processing in the XPC in a reasonable amount of time would have required using IOSurfaces which are very poorly documented, and which none of us had used at the time. Also, it would have greatly complicated a template that was intended to be fairly simple. So we went with just adding the watermark in the XPC and doing it in software because it was straightforward and easy to understand.
Let me know if the above helps, Darrin
On Aug 12, 2017, at 10:15 AM, Ben Syverson <ben@bensyverson.com> wrote:
Hi all,
After a few years away, I’m trying to implement some code as an FxPlug. So I created a brand new project from the FxPlug template, built it, and nothing happened. There doesn’t seem to be any documentation about how to use this template, so I’m reaching out for help.
I did try turning on code-signing for the Wrapper, XPC and Plugin.
I also noticed that the Bundle Identifier is set to the product name (i.e. Example), not the full identifier (i.e. com.bensyverson.Example). I changed that, but I’m not clear on whether the Wrapper, XPC and Plugin should have different IDs?
The template seems to generate new UUIDs, but I made new ones anyway, but it still didn’t help.
Running `pluginkit -m` doesn’t show the new plugin, and it doesn’t show up in Motion. No errors are reported in the console, so I’m not sure where to start looking.
(I also noticed that the template builds a plugin which doesn’t implement hardware rendering (!), which is baffling. If there’s only one template, it should either implement both, or just hardware.)
Does anyone have any tips? Thanks in advance!
Ben _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/dcardani%40apple.com
This email sent to dcardani@apple.com
_______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com