|Jun 3, 2013, 08:35 PM||#1|
How does OS X associate file extensions with apps?
I'd like to make a small utility that makes it a breeze to associate hundreds of file extensions with a single app and to use a single quick look plugin all at once.
My understanding is that there's a property defined in each app bundle's info.plist that says which file extensions it associates with, but then the contents of this property are copied to some master file somewhere from time to time.
Does anyone know where that master file is?
Or should I just modify the chosen app's info.plist?
Battery Status - On the Mac App Store
The only app that'll estimate when your wireless devices will need their batteries changed.
Including the ones paired with other Macs on your network.
|Jun 4, 2013, 08:02 AM||#2|
1) Do not ever modify another apps Info.plist: this will break code signing which will prevent them running if signed.
2) Launch Services maintains the database of associations.
Sponsor me to cycle 100Km round London in the dark
|Jun 4, 2013, 08:05 AM||#3|
I'll look at the link you shared - thanks!
Edit: Quick related question:
Does a file itself contain its own MIME type - or is that some kind of meta data from outside the file?
Last edited by ArtOfWarfare; Jun 4, 2013 at 09:09 AM.
|Jun 12, 2013, 01:27 PM||#4|
To my knowledge, Launch Services can map MIME data to document definitions and/or a UTI. But as far as storing MIME type for a file, it doesn't do that.
Last edited by Madd the Sane; Jun 13, 2013 at 12:49 AM. Reason: completing a thought
|Jun 13, 2013, 12:35 AM||#5|
all of the above is accurate, at least as far as I know.
Just to be complete, my rule of thumb for app associations is:
dos/windows - file name extension.
older Mac OS - resource fork
Unix - pulled from /etc/magic
I just looked in my 10.6.x server, and I don't see a /etc/magic file. I *thought* a magic file was there, maybe in older versions and Apple has more recently pulled it.
Again, on my 10.6.x Server, I do have (2) magic files, one in each of these directories.
Hope this is of some value to you.
|Jun 26, 2013, 07:34 AM||#7|
When a user drags an application into the Applications folder, the system should register it with Launch Services automatically.
See Application Registration in the Launch Services Guide.
|Jun 26, 2013, 09:44 PM||#8|
Some History of File Types on the Mac
Back in Classic Mac OS, each document has an OSType which was a 4 character file type such as "TEXT" for a text file, and file name extensions were just a part of the file name and had no special meaning.
When OS X came out, it was Unix so, file name extensions came into use with Mac OS X. They are hidden by default in the Finder, but they are visible in Terminal.app and they are visible in Finder.app if you go into Finder > Preferences > Advanced Preferences > Show all filename extensions and check this check box.
OS X still has the OSType in application bundles. Application bundles are really just folders with the .app extension. You can open them up in Finder by right-clicking on them and choosing "Show Package Contents" from the context menu. If you look around, you can find a file called "PkgInfo", it contains two OSTypes one is the document type which is "AAPL" which stands for "application" and the second OSType is what's called the "creator signature".
This OSType stuff is a carry-over from the Mac Classic OS era, but it is still around.
I'll echo what somebody else said. Don't change any applications in any way!!!.
In the Classic Mac OS, when a user opened a document from the Finder, the Finder would look at the creator signature to see which document created it and would open that application.
Back in the Classic era, each file was potentially two files in one. 1) a data fork, and 2) a resource fork, and there were some file attributes which were only used on Macs and you could lose the resource fork and Apple's file attributes if you transferred the file to a computer that wasn't a Mac.
Nowadays, OS X apps *can* create documents with a resource fork, but they usually don't or if they do, they don't store anything critical in the resource fork.
Somebody else mentioned "Launch Services". This seems like a "clean" way to go, to go through one of Apple's API functions:
In addition to OSType and filename extension, there is another way to type files that's used now called Uniform Type Identifiers (UTI). Here is a link to that sort of thing in Wikipedia:
So in the history of Mac OS, a text file could be typed in the following manners:
1. OSType of "TEXT"
2. file name extension of ".txt", or ".java", or ".c" or ".cpp", etc, etc, etc.
3. A UTI of "public.text"
Then there's the MIME types which are more specific than just saying that something is text. For example:
So, a file can be typed so many different ways, it can be confusing. When you figure it all out, let me know.
Whatever you do, don't write to one of Apple's files that is somewhere or change an application in any way.
I could really use an application like the one that you're writing to change all text files with whatever extension to open up with BBEdit.
Though, be careful not to annoy people by changing file type associations behind people's backs you want to put the user in charge.
If you need a beta-user or if you have any more questions, you can send me an email. I'd love to hear from you.
|Jun 27, 2013, 08:03 AM||#9|
|Thread Tools||Search this Thread|
All times are GMT -5. The time now is 04:27 PM.