• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: defer loading window using bundles in XCode 3 Leopard
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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 14:28:55 -0700

On Friday, July 25, 2008, at 12:40PM, "Kyle Sluder" <email@hidden> wrote:
>On Fri, Jul 25, 2008 at 2:19 PM, julius <email@hidden> wrote:
>> What I have seen on the web seemed to indicate that bundles are a really
>> good way of splitting up code development etc.
>> I like keeping code compartamentalised and bundles looked like a good way to
>> do it.
>
>This is not what bundles are intended for.  Bundles are ways of
>loading code at runtime.  The reasons for doing so are dictated by
>program requirements, not the development environment.  From a
>development perspective, when your code gets loaded into your process
>should be orthogonal to your environment.  Nothing prevents you from
>splitting your code into multiple projects that all get compiled into
>one executable in the end, achieving your compartmentalization without
>abusing the dynamic loader.

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.

>> But I also have the memory of someone else being advised on this list to
>> keep away from bundles.
>> That plus the hastle of working with what to me looks  like out of date
>> documentation....
>
>You may be right; it's certainly incomplete.  One thing it
>historically hasn't addressed well is the use of macros such as
>@executable_path and @loader_path.  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 :).

--
Adam

[1] http://www.sente.ch/software/cvl/
_______________________________________________

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

  • Follow-Ups:
    • Re: defer loading window using bundles in XCode 3 Leopard
      • From: "Kyle Sluder" <email@hidden>
References: 
 >defer loading window using bundles in XCode 3 Leopard (From: julius <email@hidden>)
 >Re: defer loading window using bundles in XCode 3 Leopard (From: "Kyle Sluder" <email@hidden>)
 >Re: defer loading window using bundles in XCode 3 Leopard (From: julius <email@hidden>)
 >Re: defer loading window using bundles in XCode 3 Leopard (From: "Kyle Sluder" <email@hidden>)

  • Prev by Date: Re: NSTableView NSTrackingArea and mouse clicks
  • Next by Date: Can't get NSScrollView to resize properly
  • Previous by thread: Re: defer loading window using bundles in XCode 3 Leopard
  • Next by thread: Re: defer loading window using bundles in XCode 3 Leopard
  • Index(es):
    • Date
    • Thread