Launchd and Folder Actions are two vastly different concepts.
Folder Actions
Folder Actions allow you to attach actions in the form of Apple Scripts folders which get triggered if the content of the folder changes. Typical use cases are e.g.
- a folder to auto-upload photos to a website
- removal of file attributes (e.g. the "downloaded" attribute)
- triggering import into Evernote
- etc.
launchd
launchd is a system-wide feature to run and control system-level background tasks. These can be either running all the time or get triggered by specific events (e.g. a connection request coming in over IP, a changing folder, a specific point in time etc.). OS X makes heavy use of this concept for all kind of things, have a look at the names in /Library/LaunchAgents
and /Library/LaunchDaemons
to get an idea of functionality depending on launchd.
Because launchd is a system service running in the background all the time it can't be accessed by the user directly. To send commands to launchd, the launchctl
command is used.
Answers to specific questions
- Do folder actions use launchd?
Most probably not. You can use launchd to do everything folder actions can do but at least on a level visibile to the user these are two different concepts
- Is one more efficient than the other?
No difference here, both get triggered by OS X upon special conditions.
- Is one more powerful than the other?
launchd is definitively more powerful.
- Is one used more over the other?
In a newly installed system there already is a great number of active launchd scripts but no folder actions. Because the later must be explicitely activated and configured by the user, it's probably a safe guess that launchd is used more often.
AS @lhf comments export/import implies that there is some information lost during one of the processes so that you can't export and then import and get exactly the same document back.
Save usually writes the file in the format that is native to the application or in the same format as the file was opened in.
Some applications e.g. Microsoft Office will not use export as much as this but use save as to allow conversion of the format of the document and possibly lose some information e.g. Excel can save as .csv. (I don't have MS Office here and can't remember if they have an export on the file menu). The do have an import that adds the selected document to the current one so another meaning.
The examples you give are both that the file file format is native to an application ( Open Office and PhotoShop) and the other applications' export converts their own format to these on export.
Best Answer
From Apple's Bundle Programming Guide
Also
In code with bundles and packages are manipulated by the same NSBundle class