User Tools

Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
expcustom [2018/10/15 16:30]
croft
expcustom [2018/10/16 14:10] (current)
sechrest
Line 8: Line 8:
 =====The Exporter Application===== =====The Exporter Application=====
  
-Custom mesh exporting from the Modeler was designed to be as flexible as possible for the developer writing the exporter. For this reason, temporary files are used to pass data from the application to the exporters. This allows the exporter application to be written in any programming language or frameworksince it is not tied to a specific API/​language/​version that can interface with the Modeler. ​+Custom mesh exporting from the Modeler was designed to be as flexible as possible for the developer writing the exporter. For this reason, temporary files are used to pass data from the application to the exporters. This allows the exporter application to be written in any programming language or framework since it is not tied to a specific API/​language/​version that can interface with the Modeler. ​
  
-These intermediate files are simply raw XML files that contain all the geometry information needed for the exporter, and they can be exported from the Modeler directly, as well. The exporter application needs to be able to take the xml filename on the command-line.+These intermediate files are simply raw XML files that contain all the geometry information needed for the exporter, and they can be exported from the Modeler directly, as well. The exporter application needs to be able to take the XML filename on the command-line.
  
 Custom exporters need only be concerned with the geometry stored in the raw XML file and the final format. All textures are already handled for you by the Modeler. Custom exporters need only be concerned with the geometry stored in the raw XML file and the final format. All textures are already handled for you by the Modeler.
Line 19: Line 19:
 In order for the Modeler to be able to find and run a custom exporter, it must be placed in the <​apps>/​custom_exporters directory. This directory may need to be created. In order for the Modeler to be able to find and run a custom exporter, it must be placed in the <​apps>/​custom_exporters directory. This directory may need to be created.
  
-Additionally,​ a small file describing the exporter needs to be placed with the exporter application. This file is also XMLand needs to have the "​.sme"​ extension. An example of an .sme file and descriptions of each value are shown below.+Additionally,​ a small file describing the exporter needs to be placed with the exporter application. This file is also XML and needs to have the "​.sme"​ extension. An example of an ".sme" ​file and descriptions of each value are shown below.
  
 <​code>​ <​code>​
Line 35: Line 35:
 |  Extension|The final file extension for this exporter | |  Extension|The final file extension for this exporter |
 |  Executable|The file name of the executable application to run | |  Executable|The file name of the executable application to run |
-|  ExtraArguments|Any extra arguments to be passed on the command line to the exporter application. This can allow you have one single exporter application with a number of different exporting features through multiple .sme files. |+|  ExtraArguments|Any extra arguments to be passed on the command line to the exporter application. This can allow you to have one single exporter application with a number of different exporting features through multiple .sme files. |
 |  GameExporter|This value should be true or false, depending on if this exporter is to be a game export | |  GameExporter|This value should be true or false, depending on if this exporter is to be a game export |