MacOSX tipsshort URL
Critical: if you update and Fiji does not work anymore, you need to follow these instructions.
- Download the .dmg package from the Downloads page, and then double-click it to open it.
- Create a folder under /Applications/, such as /Applications/Fiji
- Drag the 3 items (Fiji.app, and the plugins and macros symlinks) into the /Applications/Fiji folder.
Fiji is ready to run!
Running Fiji on Java 1.5 (32-bit)
Fiji on intel Macs runs on Java 1.6 (64-bit). If you need to run it in 32-bit mode, use the following code:
arch -i386 /Applications/Fiji/Fiji.app/Contents/MacOS/fiji-macosx
Limited PowerPC (G4/G5) Mac support
Note: There is no Java 1.6 for PowerPC from Apple, meaning that Java comes at a considerable performance penalty on this platform. In addition, we will not be able to support Java versions prior to Java 1.6 at some stage, since that version offers a few features we want to rely on, such as a versatile scripting framework.
You can also install a third party Java 6, part of the OpenJDK project. You will need a working X11 server, that you can find on your OS X disk, and MacPorts.
Execute sudo port install openjdk6 on your Terminal. You can also install the SoyLatte Binaries, as an alternate choice. Then you can proceed with the generic Fiji Installation
Accessing the plugins and macros folders
To access the plugins or macros folders, set the Finder window to either icons or lists mode, not in column mode, and double-click them.
Alternatively, right-click (or control-click) the Fiji.app and select "Show package contents", to open the folder where the actual plugins and macros folders are.
Adding new plugins and macros
For plugins, please follow the instructions about Installing 3rd party plugins. Otherwise, access the plugins folder as explained above and just drag and drop any plugin into the plugins folder, like you would do for ImageJ. Same for macros.
Installing OpenJDK for MacOSX
If you are experiencing problems, say, with AWT-AppKit related crashes, and if you do not mind working with an X11-based graphical user display, you might want to try OpenJDK.
As of mid-April 2011, OpenJDK for MacOSX has basic working support for Aqua, which you have to activate explicitly by passing the Java option -Dswing.defaultlaf=com.apple.laf.AquaLookAndFeel.
Since the development of OpenJDK for MacOSX is driven exclusively by Apple employees, the minimal MacOSX version required to run OpenJDK/Aqua is 10.6. If you require Fiji to run on earlier versions of MacOSX, you will have to go back to SoyLatte, where you will also find an X11-only OpenJDK version that runs on MacOSX 10.5/PowerPC (MacOSX 10.6+ does not support PowerPC). In the alternative, you can put in a considerable effort to "backport" OpenJDK :-).
Running Fiji in the command line
Often it is necessary to run Fiji in the command line, e.g. to pass some command-line options. To do so, start a Terminal (in the Finder, Go>Utilities), and switch to the correct directory using the cd command. Note that the application itself is actually a directory called Fiji.app. For example, if you installed Fiji into /Applications as recommended, do this:
If you unpacked Fiji onto your desktop, do this:
Once you switched to the correct directory, start the Fiji launcher:
Note for Windows users: A backslash is not the same as a slash. So: Contents\MacOS\fiji-macosx will not work.
Now you can pass, say, Java Options:
Contents/MacOS/fiji-macosx -verbose:gc --
Note: to distinguish between options intended for Java and options intended for ImageJ, you need to separate the former from the latter with a double-dash: --. Since the default is to accept ImageJ options, you have to pass a trailing double-dash if you want to pass only Java options.
MacOSX keyboard shortcuts
It is often helpful to use keyboard shortcuts when using Fiji. There are also operating system specific shortcuts which can be quite helpful. For example, pressing Command+Tab and releasing first only the Tab key will allow you to cycle through the running applications, while Command+backtick will do the same for the windows opened by the current application. Dave Polaschek has a comprehensive list.