There are several types of files and file extensions created in EON Studio that you will need to understand in order to create a variety of projects. When you select Save or Save As from the File menu, you will see only one choice for the type of file to save which is an EOZ file. However, a number of other file formats are used for distributing complete EON applications as well as for saving new prototypes within an application. The types of EON file formats available include:
When you select either the Save or Save As option, your application is automatically saved in the EOZ file format. The resulting EOZ file is a standalone “work-in-progress” package that includes all nodes, prototypes, and both internal and external project resources such as meshes, textures (.jpg, .png, etc.), sounds (.wav and .mp3 files), and video files (.avi, .mov, .wmv, and .mpg4). As you can imagine because all file resources are stored uncompressed and un-optimized, EOZoptimized, EOZ files can quickly develop into very large files. Not until you create a distribution file (Windows, mobile, or VR Device) will the resources be compressed and optimized for size and performance. From a developer’s perspective, the EOZ file bundle makes it easy to move all work associated with a specific project to a new location on your storage devices without the fear of losing files or breaking links to files.
EDZ and EMZ Files
After all work on the project is complete, the EOZ file is condensed into an EDZ file format for distribution to end users. The following sequence of operations occurs when the Build Distribution File command (accessible from the File menu) the following options are offered:
There are three options to choose from when building a distribution file and these will be covered in detail in later chapters. The end result is the same for each option as operations are run that compile and compress the application for sharing in a variety of formats.
Primarily the following occurs when the basic Windows distribution file is created:
- A distribution folder is created to store the distribution files. (The folder’s name is the same as the EOZ files.)
- All internal resource files are optimized, compressed, and then stored within an EDZ archive file, which is placed in the root of the distribution folder.
- All external resource files are placed under the distribution folder in subfolders with appropriate names (resources, textures, etc.)
Because the resources within an EDZ file format are optimized and compressed, the resulting EDZ or EMZ files are much smaller than the original EOZ file, which ultimately improves the end user’s experience by decreasing download time and application load time.
An EDZ file cannot be opened for editing in EON Studio; it can be viewed only, whether in EON Studio, the EON Viewer, or in another host application that can interpret the embedded controls included in the EDZ file. EDZ files are secure and protected, making it a safe distribution format for clients who would like to protect their assets in the application/simulation file. For this reason, it is preferable to generate an EDZ file for distribution to the end users.
EMZ files are EON mobile distribution files. These distribution files are optimized and compiled to run on mobile devices in both iOS and Android platforms. The process is the same as the regular EDZ file but you must select the correct platform to create the proper distribution file.
You will note a couple of differences when you look in the distribution folder that is created when choosing a platform for the distribution file. Located in the associated distribution folder is the .EMZ file for your application and a second folder named Deployment. In this folder you will see additional subfolders containing Icons, Images, and an Output folder. These folders contain files, textures, and specific XML files required for mobile applications. You will learn more about creating mobile applications later in this text and in a supplemental module.
EOP and EMP Files
An EOP file is a project file for a prototype library. EOP files are essentially theessentially the equivalent of EOZ files, but they are used specifically for storing prototype libraries. Each EOP file contains one prototype library that, in turn, can contain a family or set of individual prototypes. For example, there is a 3DShapes prototype library thatlibrary that contains the following prototypes: Cone, Cube, Cylinder, Pyramid, Sphere, Square, Teapot, and Torus.
EMP files are EON Mobile Prototypes. EMP files are prototypes created for use on mobile devices. These are created to make creating augmented reality and touch based applications easier to build in order to reduce build time for the developer.
EOG Files are EON geometry files include mesh or shape node data that create the geometry resources required for 3D objects.