• 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: telling when a directory is really a bundle
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: telling when a directory is really a bundle


  • Subject: Re: telling when a directory is really a bundle
  • From: Martin Redington <email@hidden>
  • Date: Mon, 22 Oct 2007 15:53:28 +0100


I think they're OR'd rather than AND'd - this is implied, but not clearly stated, in the link I referenced.


I believe that the CFBundleDocumentTypes entry in Info.plist (which maps to the Document Types table in Xcode's Info for the target) allows you to inform the OS about new package types for your app. Presumably it adds these to some internal list used by the Finder at first launch.

I think that the behaviour you're seeing is as intended. I haven't played around with the bundle bit, buts its possible that you can set this to get the bundle recognized as such. My quick test indicated that its rarely set, at least on .app's. The docs imply that its only valid for files in any case, which would account for that, and rule out it's use in your case.



On 22 Oct 2007, at 14:19, Dirk Stegemann (Mailing-Lists) wrote:

Hello,

Am 22.10.2007 um 15:35 schrieb Martin Redington:

http://developer.apple.com/documentation/CoreFoundation/Conceptual/ CFBundles/Concepts/BundlesAndFinder.html#//apple_ref/doc/uid/ 20002127-BAJIBGGC

A directory is a package if:

1) it has a known suffix .app, .bundle, etc.
2) it has the bundle bit set
3) it has a known structure indicating its a bundle

I wonder about suffices which are known on one system but not in the other...


For example, I copied an .xcodeproj bundle to a system which didn't have the Xcode tools installed. The Finder treated the bundle as ordinary folder; is this intended behaviour?

Following the requirements list given above (and assuming the three requirements are AND'd), it would be correct behaviour, because the .xcodeproj bundle type is unknown on that system.
Still, it would be nice if that bundled document would have been recognised as "some bundled document" with unknown corresponding application...


Best,
Dirk Stegemann






_______________________________________________

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: telling when a directory is really a bundle
      • From: Uli Kusterer <email@hidden>
References: 
 >telling when a directory is really a bundle (From: Martin Redington <email@hidden>)
 >Re: telling when a directory is really a bundle (From: "Dirk Stegemann (Mailing-Lists)" <email@hidden>)

  • Prev by Date: Re: telling when a directory is really a bundle
  • Next by Date: Re: telling when a directory is really a bundle
  • Previous by thread: Re: telling when a directory is really a bundle
  • Next by thread: Re: telling when a directory is really a bundle
  • Index(es):
    • Date
    • Thread