andre at andregarzia.com
Sun Jul 11 20:38:44 EDT 2010
For your mac os x programming pleasure:
Mac OS X identifies bundles using three ways :
The Finder considers a directory to be a package if any of the following
conditions are true:
* The directory has a known filename extension: .app, .bundle, .framework,
.plugin, .kext, and so on.
* The directory has an extension that some other application claims
represents a package type; see “Document Packages.”
* The directory has its package bit set.
The preferred way to specify a package is to give the package directory a
known filename extension. For the most part, Xcode takes care of this for
you by providing templates that apply the correct extension. All you have to
do is create an Xcode project of the appropriate type.
Most bundles are also packages. For example, applications and plug-ins are
typically presented as a single file by the Finder. However, this is not
true for all bundle types. In particular, a framework is a type of bundle
that is treated as a single unit for the purposes of linking and runtime
usage, but framework directories are transparent so that developers can view
the header files and other resources they contain. " -- quoted from 
I know that the developer tools comes with "SetFile" which allows you to set
a directory as a bundle, maybe there's a way to checkout the package bit or
something along the lines of an hypotetical "isbundle?"
On Sun, Jul 11, 2010 at 7:20 PM, J. Landman Gay <jacque at hyperactivesw.com>wrote:
> Andre Garzia wrote:
>> Bundles can have more extensions than just .app.
> What about checking for a plist inside the bundle? Would that be reliable?
> Do only apps have plists?
> Jacqueline Landman Gay | jacque at hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
http://www.andregarzia.com All We Do Is Code.
More information about the Use-livecode