How packages are recognized...
How packages are recognized...
- Subject: How packages are recognized...
- From: Eric Gorr <email@hidden>
- Date: Tue, 7 Aug 2007 10:17:01 -0400
(not sure what the best mailing list for this question would be...)
I am trying to get a better understanding of how the finder
determines when to treat a folder as a package.
Basically, if a folder has a .app or .mdimporter extension, the
finder takes that as a hint that it should not be treated as a normal
folder. For example, the user needs to use 'Show Package Contents' in
order to see what it contains.
On this page
http://developer.apple.com/documentation/CoreFoundation/Conceptual/
CFBundles/Concepts/BundlesAndFinder.html
it states that
The Finder identifies packages by any of the following mechanisms:
The directory has a known
extension: .app, .bundle, .framework, .plugin, .kext, and so on.
Although, I noticed that while I can give a folder a .app
or .mdimporter extension to turn it into a package, .framework will
not do the same - I'm assuming this is an error in the document. All
the other extensions listed did turn a folder into a package. Other
then .mdimporter, for example, what else does 'and so on' refer to?
The page also lists two other way the finder detects a folder as a
package
The directory has its bundle bit set
The directory has a known structure type indicating it is a modern
or versioned bundle.
For 'The directory has its bundle bit set'...it seems I should know
what this is referring to, but my mind is drawing a blank. How would
one set the bundle bit of a folder to turn it into a package?
For 'The directory has a known structure type indicating it is a
modern or versioned bundle'...what is/are these structures? I assume
in this case, there is no need for the folder to have a recognized
extension.
Thank you.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden