Opening package with LiveCode on OSX

David Bovill david at
Tue Mar 15 06:40:09 EDT 2011

Thanks Terry. Doing some research:

   - Document Packages<>
   - All about Bundles<>

It seems that all that is needed is, as you say, to add some entries to the
plist of the app:

> To register a document as a package, you must modify the document type
> information in your application’s information property list (Info.plist)
> file. The *CFBundleDocumentTypes*<>key stores information about the document types your application supports.
> For each document package type, include the *LSTypeIsPackage* key with an
> appropriate value. The presence of this key tells the Finder and Launch
> Services to treat directories with the given file extension as a package.
> For more information about Info.plist keys, see *Information Property List
> Key Reference<>
> *.
> Document packages should always have an extension to identify them—even
> though that extension may be hidden by the user. The extension allows the
> Finder to identify your document directory and treat it as a package. You
> should never associate a document package with a MIME type or 4-byte OS
> type.
Now finding out exactly what you need to do to the plist is a bit more


"Document is a package or bundle”


Specifies whether the document is distributed as a bundle. If set to true,
the bundle directory is treated as a file. (In Mac OS X v10.4 and later,
this key is ignored if the LSItemContentTypes key is present.)

And then you need to do stuff with the more complicated *

   - Information Property List Key

To edit a plist in LiveCode, you can use
OSX recent OSX systems (post 10.5).

It seems for OSX systems earlier than 10.5, you need to use the command line
utility plutil<>to
convert from binary to XML and back again. Then you can use LiveCodes
function to edit the XML.

   - plutil <>
   - plistbuddy<>

So all we now need is a little recipe to script plistbuddy to add the right

More information about the Use-livecode mailing list