However, packages hold potential rewards even for "common" end users. Unless you are a developer, you won't have much need to delve inside packages. Simply access the contextual menu (or Action menu, from a Finder window's toolbar) for the desired package item and select the "Show Package Contents" command. Finally, packages maintain a degree of simplicity by facilitating application resources to reside in a single location, rather than spread out in numerous Library folders (although it is not 100% successful in this regard, as there are Library folders, such as Application Support, where such resources are stored).ĭespite all of this shrouding of package contents, if you want to open up a package and examine its contents, it's quite easy to do. The package concept also prevents novice users from easy access to the contents, thereby minimizing the chance that users will "experiment" with the files within and cause unintended trouble. By creating the illusion of a single file, packages make sure that no files are unintentionally left behind when copying or moving the folder/package.
FLAT PACKAGE EDITOR DOWNLOAD MAC OS
Overall, packages have functioned very well in Mac OS X. pkg, for package, extension) are packages/folders that contain the files to be installed by the "document" plus the instructions needed to perform the installation correctly.
Similarly, installer documents (with their. app extensions) are packages/folders, with the "real" application code as well as a collection of related resources contained inside.
The two most common uses of packages are for applications and installer documents. Packages are Apple's name for what are essentially folders disguised as single files in the Finder. What you may not know is that Leopard (Mac OS X 10.5) offers a new type of package called a flat package. If you've spent time peeking under the hood of Mac OS X, you already know about packages.
0 kommentar(er)
