Overview Photo Book (manually)

WIKI: Lnik to the start page of the collection of articels about all MegaZine3 topics

This tutorial is a step-by-step guide that shows how to create a photo book in a manual way, using text and XML editors. This way of creating a MegaZine3 title (i.e. the megazine.mz3 file) is possible with all systems, MAC/OSx included. All steps are explained in detail. Throughout this "project" the basic concepts of MegaZine3 are explained and therefore are also helpful for those using the MZ3-Tool.

At the end a working photo book is built. A simple one, with one image per page and without any other sexy elements like videos. And it is not the fastest way and most comfortable approach to create such a book; but ideal to learn the basic concepts of MegaZine3. This background knowledge will be a big help in avoiding mistakes and identifying potential problems.

Demo: "quickly" adding images

A more comfortable and faster approach is offered with the demo packages, available for download at our download page. Those include the MZ3-Tool and a specific version of the MegaZine3 Software for the respective use cases. The MegaZine3 software is free for use and licensed as MZ3-FREE.

If you are interested in more details about the features and options of MegaZine3, please see the Wiki and other tutorials; like e.g. those about useful tools, or the general MegaZine3 basic concepts.

Remark

The folder structure used for this simple photo book is only suitable for a single title/book. For another title, the complete folder could be duplicated.

Disadvantage: every single title would have its own copy of the complete MegaZine3 software. A waste of space; and also painful in case of updates/upgrades.
Also different versions of one title are not supported with this structure neither. The demo packages with the MZ3-Tool introduce and support a more complex folder structure, that helps to manage many titles and different versions in an easy way.

The advantage of this simple structure is:

  • the default index.html file can be used without changes
  • absolute path names can be used, and with that
  • the risk of running into security problems (see sandbox problem) is minimal.