The fact that AppKiDo isn't built in is one of the reasons I like it. When
you update your docs in Xcode's built-in browser a relaunch of AppKiDo will
cause it to pick up the changes.
Agreed on the loading delay. That's annoying. And it's pretty weak on the
polish side. It does display inherited m
:
>
> On 2009 May 19, at 23:28, Kevin LaCoste wrote:
>
> if we move helper tools into a new Contents/Helpers folder are they
>> covered by codesign?
>>
>
> The answer is that you must invoke the 'codesign' tool to sign the helper
> tool as a separate ste
indow. Time for some testing...
Kevin
On Wed, May 20, 2009 at 1:21 PM, Jerry Krinock wrote:
>
> On 2009 May 19, at 18:21, Kevin LaCoste wrote:
>
> I found some sample code that includes a helper tool and yes, it's in the
>> "Contents/MacOS" folder.
>>
&g
hat I would guess
are the recommended bundle directories. Hadn't noticed that before.
http://developer.apple.com/samplecode/BetterAuthorizationSample/
Kevin LaCoste
On Wed, May 20, 2009 at 9:38 AM, Chris Suter wrote:
> Hi Kevin,
>
> On Tue, May 19, 2009 at 8:04 PM, Kevin LaCoste
>
/Executable" folder?
Bonus question. Is the support directory referred to above the Application
Support folder or is this another additional, optional bundle directory?
Thanks for any clarification!
Kevin LaCoste
___
Cocoa-dev mailing list (Cocoa-d
