Some apps, however, come with additional resources – such as plug-in folders and PDF user guides – that won't go inside a package. You can open these in Preview or Photoshop, and you could even customise the app by editing them, but this isn't quite as straightforward as it looks (icons are accompanied by masks, for example, that need editing to match).Īs far as uninstalling is concerned, dragging the application to the Trash will delete all of these bits and pieces. It's fun to have a look in Resources, because it houses a lot of the icons and user interface graphics used within the app. Open these in turn, and you'll see a whole load of stuff that probably means absolutely nothing to you. Within this are various subfolders, such as Frameworks and MacOS. You'll first see, tautologically, a folder labelled Contents. To see what's inside the bundle, right-click it (or Ctrl-click with a single-button mouse) and choose Show Package Contents. In many cases, everything the app needs can be stored within this package, which is nice and neat. Its Kind is listed as Application, and if you hit Command+I to Get info you'll see its file extension app. When you open the Applications folder and find the icon that you'd double-click to run a particular app, what you're seeing is a 'package' (also known as a 'bundle') that looks like one file but in fact contains several. Even so, deleting an app's main file (which, as we'll see, isn't exactly a file at all) doesn't always remove it and its effects from your Mac. Mac OS X has no Registry to worry about, and handles apps with a lot less hassle. Even when you correctly use Add/Remove Programs to manage your apps, rather than trying to install or erase them manually, things can still go wrong – and over time they almost invariably do.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |