On 3.11.2011, at 17.57, James Brooks wrote:
> The sandbox is to protect users from malicious developers. There is no way Apple is going to sandbox FCP-X, it would never work, and is not necessary, as they control the code.
>
> Cheers, James
>
> On Thu, Nov 3, 2011 at 11:35 AM, Christoph Vonrhein <
email@hidden> wrote:
> If Apple would restrict their own applications in such a way that these apps are not going to load external binaries, like our plugins, then this would mean that FCP X and Motion completely lose the plugin functionality. I don't think that this is how it is going to turn out.
>
> Can anybody from Apple give us some more inside on this topic?
>
> Christoph Vonrhein
>
www.chv-plugins.com
>
>
> On Nov 3, 2011, at 11:08 AM, Patrick Sheffield wrote:
>
>> But Final Cut X and Motion are sold via the App store. This implies that they will not be allowed to load external binaries (i.e. our plugins).
>>
>> Patrick Sheffield
>> Sheffield Softworks
>>
>> On Nov 3, 2011, at 8:06 AM, Christoph Vonrhein wrote:
>>
>>> As far as I understand it does the limitation only affect the Mac App Store. You can still continue to sell your plugins through your own website. Only Apps sold through the App Store need to be sandboxed and only there you have to justify why your plugin works the way how it works.
>>>
>>> Christoph Vonrhein
>>>
www.chv-plugins.com
>>>
>>>
>>> On Nov 3, 2011, at 4:04 AM, Pauli Ojala wrote:
>>>
>>>> Apple has announced that as of March 1, 2012, all apps on the Mac App Store will be required to run in a "sandbox":
>>>>
>>>>
https://developer.apple.com/devcenter/mac/app-sandbox/
>>>>
>>>> A sandboxed app doesn't have direct access to any real paths on the system, and it must require entitlements for potentially dangerous things. (These include showing an Open dialog to the user, and loading data over the network. Entitlements are not granted by the user, but by Apple's App Store curators, so app developers will need to justify their need for these "advanced" features.)
>>>>
>>>>
>>>> It seems to me that the sandbox completely bans loading binaries from shared locations. This, of course, is how plugins are typically installed and loaded.
>>>>
>>>> How does this ban affect FCP X and Motion 5? I don't see a way how these apps can continue to support plugins within the sandbox.
>>>>
>>>> Since the Mac App Store is now the only way to get FCP and Motion, they'll have to be sandboxed next year. Will that be the end of FxPlug?
>>>>
>>>> --
>>>> Pauli Ojala
>>>> Lacquer oy/ltd
>>>>
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
>>
>
>
> _______________________________________________
> 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
>
>
>
>
> --
> James Brooks, CTO
> Drastic Technologies
> Tel:
+1 416 255 5636, ext 226
> <vcard>
http://www.drastictech.com/contacts/james.vcf</vcard>
> _______________________________________________
> 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