On Jul 5, 2011, at 3:00 PM, email@hidden wrote:
> Send Aperture-dev mailing list submissions to
> email@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.apple.com/mailman/listinfo/aperture-dev
> or, via email, send a message with subject or body 'help' to
> email@hidden
>
> You can reach the person managing the list at
> email@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Aperture-dev digest..."
>
>
> Today's Topics:
>
> 1. Preparing for sandboxing (Clarence Locke)
> 2. Re: Preparing for sandboxing (Fraser Speirs)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 04 Jul 2011 13:27:16 -0700
> From: Clarence Locke <email@hidden>
> Subject: Preparing for sandboxing
> To: "email@hidden List" <email@hidden>
> Message-ID:
> <email@hidden>
> Content-Type: text/plain; charset=us-ascii
>
> I understand Apple's desire to keep new products as secret as possible until they are announced to the public, but sometimes that has a direct effect on the preparedness of third-pary developers. A very good example of this was the release of the 64-bit capable Aperture. While it was good for the user that you provided a "32-bit compatibility relaunch mode", it essentially left all of your third-party developers with a bit of egg on their face and scrambling to get the products back up to par.
>
> I would really prefer (and appreciate) not having to experience that again.
>
>
> So that leads me to my first few questions regarding Aperture and Lion:
>
> 1) Is Aperture currently sandboxed? (My inference from my testing to date is that it is not).
>
> 2) When will it become a sandboxed app?
>
> 3) It is my understanding that sandboxed apps must have their plug-ins converted into XPC services in order to run on Lion. Will Aperture be providing some kind of automatic "wrapper" for exiting third-party plug-ins? or are we going to have to perform the conversion?
>
>
> Clarence Locke
>
> ------------------------------
>
> Message: 2
> Date: Mon, 04 Jul 2011 21:42:07 +0100
> From: Fraser Speirs <email@hidden>
> Subject: Re: Preparing for sandboxing
> To: "email@hidden List" <email@hidden>
> Message-ID:
> <email@hidden>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Very good questions and I concur that it would be highly desirable to
> have some advance warning of the plans. I have established some
> answers to the technical side of how sandboxed applications can load
> plugins in this devforums thread:
>
> https://devforums.apple.com/message/471293
>
> My understanding is that it is _desirable_ but not _required_ that
> sandboxed apps quarantine their plugins via XPC.
>
> There is a deadline set for apps in the Mac App Store to adopt
> sandboxing (it's referred to in the WWDC "Apple Platforms Kickoff"
> video, IIRC) and I assume Aperture will be sandboxed by that time.
>
> The key question is whether Aperture's entitlements will be permissive
> enough to let us do what we need to do as plugin authors.
>
> Fraser
>
> On Mon, Jul 4, 2011 at 9:27 PM, Clarence Locke
> <email@hidden> wrote:
>> I understand Apple's desire to keep new products as secret as possible until they are announced to the public, but sometimes that has a direct effect on the preparedness of third-pary developers. A very good example of this was the release of the 64-bit capable Aperture. While it was good for the user that you provided a "32-bit compatibility relaunch mode", it essentially left all of your third-party developers with a bit of egg on their face and scrambling to get the products back up to par.
>>
>> I would really prefer (and appreciate) not having to experience that again.
>>
>>
>> So that leads me to my first few questions regarding Aperture and Lion:
>>
>> 1) Is Aperture currently sandboxed? (My inference from my testing to date is that it is not).
>>
>> 2) When will it become a sandboxed app?
>>
>> 3) It is my understanding that sandboxed apps must have their plug-ins converted into XPC services in order to run on Lion. Will Aperture be providing some kind of automatic "wrapper" for exiting third-party plug-ins? or are we going to have to perform the conversion?
>>
>>
>> Clarence Locke _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Aperture-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>>
>
>
> ------------------------------
>
> _______________________________________________
> Aperture-dev mailing list
> email@hidden
> http://lists.apple.com/mailman/listinfo/aperture-dev
>
>
> End of Aperture-dev Digest, Vol 51, Issue 1
> *******************************************
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Aperture-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
