Re: Help with the Xcode template
Re: Help with the Xcode template
- Subject: Re: Help with the Xcode template
- From: Darrin Cardani <email@hidden>
- Date: Sat, 12 Aug 2017 10:59:53 -0700
Ben,
At this time I would do all processing within the plug-in. Once we require
FxPlugs to work out-of-process, then I’d expect the work to be done in the XPC.
We are getting there, but have not yet reached that point.
Darrin
> On Aug 12, 2017, at 10:55 AM, Ben Syverson <email@hidden> wrote:
>
> 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 <email@hidden> 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 <email@hidden> 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 (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden