Re: defer loading window using bundles in XCode 3 Leopard
Re: defer loading window using bundles in XCode 3 Leopard
- Subject: Re: defer loading window using bundles in XCode 3 Leopard
- From: "Adam R. Maxwell" <email@hidden>
- Date: Fri, 25 Jul 2008 16:08:16 -0700
On Friday, July 25, 2008, at 03:33PM, "Kyle Sluder" <email@hidden> wrote:
>On Fri, Jul 25, 2008 at 5:28 PM, Adam R. Maxwell <email@hidden> wrote:
>> I don't think this is an abuse of bundles, even though it's may not be that common anymore. If you look at http://www.stone.com/The_Cocoa_Files/Thanks_A_Bundle_.html or the source for CVL [1], I think you'll find bundles used in this way.
>
>Note though that the article you reference is about developing an
>add-in for optional functionality, which is also what CVL uses bundles
>for. A lot of applications do this, especially ones like the Adobe
>CS3 suite. But that's often because the functionality they're
>bundling exists on the same side of the architectural divide as
>third-party plugins.
A main point of Stone's article is that you can decrease launch times and avoid bloating your main code base by using loadable bundles (at least, that's how I read the intro and conclusions). I admit that I may have misremembered CVL's source, but I believe the CVL inspector panels that are implemented as plugins are not really ``optional functionality'' in the way that 3rd party plugins are: they're shipped with it as an integral part. I do think it's a waste of time to force-fit bundles into a design, but the OP can figure out if that's the case.
>>>I *still* can't find mention of
>>>@executable_path in the official documentation, despite its
>>>criticality for certain functionality.
>>
>> Really? http://www.google.com/search?hl=en&q=site:developer.apple.com+@executable_path&btnG=Search turns up a number of relevant things, as does a full-text search of "All Doc Sets" in Xcode. "Dynamic Library Design Guidelines" covers both of these (or at least it mentions them :).
>
>As of a few months ago, there was only one mention of @executable_path
>in the docs, and none prior to that.
Quite possible, but even that's not what you wrote earlier.
--
Adam
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden