Configure MegaZine3 GUI

Dozens of parameters can be adjusted to fine tune the look & feel of MegaZine3. In fact, there are more than hundred parameters that can be used. Sounds scary, but the good news is: All parameters use default values and in most cases never have to be touched.

For those who want to make use of the full power of MegaZine3, access to all parameters is provided in an easy way with mz3Tool.
Nevertheless, it is helpful knowing about the general way how to use such parameters. Soplease read on…

Background information: XML files

Those parameters are added to the central configuration file defining the Mz3 Title, your “book”. This “mz3” file, how it is often called because its extension “.mz3”, is built by mz3Tool automatically, based on the selected features and settings made with mz3Tool. This mz3 file follows the rules of XML, an “extended markup language” like HTML, which is used to define internet pages.

Leaning to the wording used describing different parts of such an “XML file”, those parameters are called “attributes” or sometimes “properties”. Attributes are directly added to the “tag”, which in our case defines the scope of such attributes; like <book> or <page>. Another option adding data/values to a “tag” is putting them in “child elements”, which again are tags, included within a pair of “parent” tags.

The general structure of a “tag”, which defines the kind and content of certain data is like this:

<parent-tagname attribute1-name=”attribute1 value” attribute2-name=”attribute2 value” …>
<child elementname />
</parent tagname>

Or as “real” example of a “mini book” with just 2 pages:

<book pageheight=”600″ pagewidth=”800″ plugins=”gestures,navigationbar,keyboardnavigation” >
<img src=”path to image” />
<page />

Child elements are embraced by their parent tags, i.e. the start tag and the end tag. The end tag starts with a “/” character. Child tags again can have another child tags, which results in a nested, hierarchical structure of definitions. An empty tag can be abbreviated like <page />, i.e. the tag name followed directly by the end-tag-character “/”.

With mz3Tool those details in most cases are hidden, and the configuration files are created automatically. But sometimes it can be helpful and is easier/faster, to have a look into those files with any text editor. Special editors capable of understanding the XML syntax like “Sublime Text” or “notepad++” offer better comfort since different elements are highlighted in different colors. Which better shows the structure and improves readability.

Documentation: WIKI

All such parameters are listed and explained in the central MegaZine3 documentation, the WIKI.
The WIKI is listed as one source of information in the answer in the FAQ area on the question: “What kind of documentation is available?”
In the WIKI you find links to the main book attributes, and another link to a list of special/new attributes:


Read the description of those attributes and you’ll get an idea about what all is possible.

The names and the possible value and value ranges of all supported attributes can be found under:

Setting Attribute Values

To make use of specific attributes those must be added to the “mz3 file”, which can be done with mz3Tool easily. There is a panel called “Book Attributes”, where some key attributes can be set directly, and all others can be defined as a pair of “attribute name” and “attribute value”:

bookAttributes    bookAttributeSetting

This way you can make use of all attributes available to configure the look&feel of MegaZine3. Once you changed or added an attribute, the Mz3 Titles will be created again, showing the results.

For those interested in the details and seeing a “real XML file”: click the little “XML” button on the bottom right: Your editor linked with the “.xml” file extension will open and show the configuration file with all book attributes. These attributes will go into the final mz3 file when “Create” is started.

 “Book” versus “Page” attributes

As the name implies, the scope of book attributes is the whole book, whereas page attributes define parameters used for a specific range of page numbers.
Example of a page attribute: foldfx
This attribute defines the strength of the fold effect, i.e. the “shadow” in between the left and right page. You e.g. can increase that effect for a certain range of pages.
The range can be defined as a list of page numbers like: 3, 7, 15
Or as a range like: 5-15, 19-23
The first and last page are represented by a “-” character.
Setting the range to include all pages between the first page and page 3 and addititonally all pages from page 10 to the last page can be done this way: -3, 10-


Categories: Technical and Tips & tricks.