Mandelbrot Madness JAVA!
Version 3.1 -- Introduction to the MOB File Format
[Return to README]
What is this MOB file stuff anyway?
In version 3.1, I introduced the new MOB file format. "MOB" stands
for "MandelObject," the Java class that internally maintains all the
parameter and palette information. A MOB file is
a compressed binary file that combines the parameter information of the
.MMJ file with the palette information of the
.PAL file. This way, everything you need to
recreate a given fractal image is combined in one small file, instead of having to
maintain two separate files for parameter and palette information. This means less
hassle, less drive space, and just plain easier use. However, there are drawbacks to
this new format. Below, we'll discuss the pros and cons of the MOB, and then
let you decide for yourself if it's a good thing or not.
Advantages of the MOB file:
- One file instead of two: You no longer have to keep track of both a parameter
file and a palette file; both are incorporated into one file.
- Smaller files: MOB files take up less space than a MMJ/PAL
file combination, mostly because they are compressed. In addition, since there's only
one file, it takes up less space on the disk because of the way disks allocate space
for files.
- Easy conversion to MMJ/PAL file pair: Using the
command-line utilities or the
Main Dialog Command menu, you can easily convert
MOBs to MMJ/PAL file pairs and back.
Disadvantages of the MOB file:
- Not backward compatible: Versions of MMJ! earlier than 3.1 cannot read
the MOB file format. MOBs can, however, be converted to older formats
using the command-line utilities.
- Parameter files cannot share palettes: Since the palette information is
stored within the MOB file, palettes cannot be shared between files. Before,
several .MMJ files could share a single .PAL file. You can't do that
with MOBs. If you create a palette you really like, you must first save the
parameters as a .MMJ to force it to create a .PAL, then save it as a
MOB.
- Conversions may not be completely accurate: Most of the time, conversions
between MOBs and MMJ/PAL file pairs works perfectly. On some
occasions, however, you may lose information. This occurs especially if you are using
the command-line utilities (not the GUI) and create a custom
palette that wasn't saved to a file independently. In this case, the palette could be
lost to the .MMJ file and it may default to the Rainbow palette. All other
conversions seem to work perfectly, so long as MMJ! can see all the proper
files needed.
Because the MMJ/PAL file pair is the older and more familiar file format,
support will be maintained indefinitely. The MOB format is more an alternative
than a replacement. Use whichever you feel most comfortable with. I plan to maintain
each.
[Top]
Working with MOB files
MOB files are extremely easy to use, even more so than our traditional
.MMJ parameter files. MOB files can be opened from the
Main Dialog File menu and can be saved from the
Image Window File menu. You can easily
convert them to traditional MMJ/PAL file combinations using the
command-line utilities or the
Main Dialog Command menu, or you can convert
MMJ/PAL file pairs to MOBs just as easily. So it's more a matter of
choice for you. In fact, you may find times to use them both!
[Top]
[Return to README]
© Copyright 1999, Jeffrey T.
Darlington. All rights reserved.