Re: How does the Mac App Sandbox affect FxPlug?
Re: How does the Mac App Sandbox affect FxPlug?
- Subject: Re: How does the Mac App Sandbox affect FxPlug?
- From: Christoph Vonrhein <email@hidden>
- Date: Thu, 03 Nov 2011 11:06:56 -0400
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