This is the iMedia Browser framework that is used by a number of applications (and as the basis for a stand-alone utility). Developers are encouraged to include this in their application as long as there is proper attribution.
iMedia 2.6 and later is compatible with common sandboxing setups, with the following notes:
SANDBOXING
to make sure your app has the entitlements iMedia needsThere is also a longer-term effort in the iMediaSandboxing
fork to farm out parsing to XPC processes.
The same as 2.6, minus support for Garbage Collection.
Out of the box (the v2.6.x
branch), iMedia supports OS X 10.6 Snow Leopard and later. It is suitable for both 32 and 64 bit apps. See above for sandbox compatibility details.
Basically the same as 2.6, minus sandbox compatibility.
For apps still supporting OS X 10.5 Leopard, we continue to support the existing iMedia 2.1 codebase on the v2.1.x
branch.
For the older 1.x branch, which is not being maintained, you can get it from subversion:
svn checkout http://imedia.googlecode.com/svn/trunk/ imedia-read-only
+[IMBConfig registerDefaultValues]
method has been made private. You should have no need to call it in your app as IMBConfig
automatically runs that routine the first time it is usedImageDataListPboardType
on the pasteboard. This allows iPhoto-aware apps to properly handle image metadata without any knowledge of iMedia+[NSImage imb_imageForResource:fromAppWithBundleIdentifier:fallbackName:]
replaces +imb_imageResourceNamed:fromApplication:fallbackTo:
. Apps likely shouldn't use this method anyway as it's fairly iMedia-specific. The new method nicely returns retina-compatible images if a suitable name is specified, like the other Cocoa image APIs.-[NSWorkspace imb_iconForAppWithBundleIdentifier:]
has been removed. Its fallback mechanism was buggy and relied on private implementation details in the OS frameworks, which have since broke. If you are using this method in your app, provide your own implementation insteadDevelopers are welcome to work on enhancements and fixes! Please use the GitHub issue tracker; note that we are not done migrating issues from the old Google Code issue tracker.
There are plenty of things that need to be done, and your help would be appreciated!