| WikiProject Apple Inc. / Macintosh | (Rated Start-class, Low-importance) | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||
Packages and bundles[edit]
This page confuses two distinct concepts. In OS X, a directory which is treated as though it was a single file is called a “package” (just as it was in OS 8.5/9); there’s an article on this concept at directory hive, which appears to be relatively rare jargon. A bundle is a directory whose contents have a certain layout. It is possible to be a package without being a bundle (example: RTFD packages), and to be a bundle without being a package (example: a framework). I don’t really have time to rewrite/split it and find suitable references at this time, however. -Ahruman 15:16, 1 May 2007 (UTC)
Se7enline MacBook Pro Case Soft Touch Hard Cover 5 in 1 Bundle Mac Book Pro Accessories for MacBook Pro 13 inch A1278 with Sleeve Keyboard Cover Screen Protector Dust Plug, Turquoise/Hot Blue. 4.3 out of 5 stars 710. Get it as soon as Thu, Oct 15. FREE Shipping by Amazon. Our mission: Finding the best Mac App Bundles and helping you saving hundreds of dollars! There are numerous places and websites where app bundles are offered. We try to simplify your time-consuming efforts to find the latest Mac bundle by providing a one stop. FileSumo is an awesome app to help you discover and clean huge files which are cluttering the disk space on your Mac. Get a list of your top 50 largest files, view them, add them to an exception list, or delete immediately; Search your whole Mac or within selected folders; View files in the Finder or delete permanently within the app.
- A framework is, like other packages, a directory tree treated as a single object in some contexts - try ls -ld /System/Library/Frameworks/Cocoa.framework; ls /System/Library/Frameworks/Cocoa.framework. It doesn't have the Contents subdirectories that, for example, application bundles do. Guy Harris (talk) 23:23, 16 March 2011 (UTC)
- The best reference for this is 'About Bundles' in the Bundle Programming Guide. Guy Harris (talk) 01:30, 17 March 2011 (UTC)
- I've created a Package (Mac OS X) page for the stuff about packages, moved the stuff that pertains to packages in general there, and linked to it where appropriate here. Guy Harris (talk) 03:25, 17 March 2011 (UTC)
Fair use rationale for Image:ITunes Contents.png[edit]
Image:ITunes Contents.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images lacking such an explanation can be deleted one week after being tagged, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.
BetacommandBot (talk) 20:08, 2 January 2008 (UTC)
'Directory bundle' vs. 'application bundle'[edit]
Much of what this page discusses is what I assume the file format infobox is calling a 'directory bundle', or just a 'bundle' in the OS X/iOS sense, i.e. a package containing executable code. As the 'About Bundles' section of the Bundle Programming Guide says, 'A bundle is a directory with a standardized hierarchical structure that holds executable code and the resources used by that code.' (although they do say 'The reason bundles and packages are sometimes considered to be interchangeable is that many types of bundles are also packages. For example, applications and loadable bundles are packages because they are usually treated as opaque directories by the system. However, not all bundles are packages and vice versa.').
In the list of system-declared Universal Type Identifiers, 'com.apple.bundle ' is 'a directory with an internal structure specified by Core Foundation Bundle Services', 'com.apple.application-bundle ' is an 'application bundle', 'com.apple.plugin' is a 'plugin', 'com.apple.dashboard-widget' is a 'Dashboard widget', and 'com.apple.framework ' is a 'Framework'.
The infobox has a redlink to directory bundle; should there be a 'directory bundle' or 'bundle (OS X)' page for the type with a Uniform Type Identifier of 'com.apple.bundle', which would contain most of what's in this page, with the 'application bundle' page describing the subtype of that bundle that is an application bundle? Or should this page be turned into a page about bundles in general, with the infobox changed to describe all the bundle types or to describe just the generic bundle type? Guy Harris (talk) 06:50, 6 June 2012 (UTC)
External links modified[edit]
Hello fellow Wikipedians,
I have just modified one external link on Bundle (macOS). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Added archive https://web.archive.org/web/20071031062502/http://pimpmysafari.com:80/plugins/? to http://pimpmysafari.com/plugins/
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).
An editor has reviewed this edit and fixed any errors that were found.
- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—InternetArchiveBot(Report bug) 19:05, 10 November 2016 (UTC)
- Works; I changed it to use {{cite web}}. Guy Harris (talk) 19:24, 10 November 2016 (UTC)
External links modified[edit]
Hello fellow Wikipedians,
I have just modified one external link on Bundle (macOS). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
- Added archive https://web.archive.org/web/20070831180432/http://www.hawkwings.net/plugins.htm to http://hawkwings.net/plugins.htm
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
An editor has reviewed this edit and fixed any errors that were found.
- If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
- If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—InternetArchiveBot(Report bug) 11:15, 8 January 2018 (UTC)
Mac OS X applications are typically packaged as application bundles which are then distributed in .dmg (disk image) files. This tutorial will show you how to package your XULRunner-based application in a way which is consistent with the expectations of Mac OS X users.
Application bundle layout
Application bundles are essentially just directory structures that conform to a standard layout and naming convention. A XUL application for Mac OS X should follow something similar to this basic directory structure:
Example.app/Contents/Info.plist(Application bundle properties are specified in this XML file.)PkgInfo(This is a simple text file and is created along with the Info.plist file)MacOS/(The MacOS folder will contain your XULRunner executable)xulrunner(This is the xulrunner stub)
Resources/(This is where you place your XUL Application code and support files)application.ini(XULRunner-related application settings)example.icns(This is the icon which will be used by your application bundle)chrome/content/example.xul(This directory contains your application's chrome)
defaults/preferences/app-prefs.js(This provides some default values for preferences)
Application bundle contents
In addition to the standard directory hierarchy that's required of all Mac OS X applications, as shown above in Application bundle layout, there are some specific rules for what content goes where:
- The top-level directory is given a name that ends with
.appwhich designates the whole package as an application bundle. - The first sub-directory is called
Contentsand within that directory you will place several files and folders that are needed by your application bundle. Info.plistandPkgInfomust exist in the Contents directory. The content of these files is covered in the article Deploying XULRunner 1.8.
Examples
These example files are taken from a port of WebRunner which was created to illustrate one method of Mac OS X application packaging.