format library contains support for different file-formats for the Haxe programming language.
Currently supported formats are :
- ABC (Flash AS3 bytecode format)
- AGAL (Adobe Shader Assembler for Stage3D - writer only atm)
- AMF (Flash serialized object)
- AS1 (Adobe ActionScript1-2 bytecode in SWF - reader only atm)
- BMP (Bitmap Image format)
- FLV (Flash Video)
- GZ (compressed file)
- JPG (Image file format - writer only atm)
- MP3 (compressed audio)
- NEKO (NekoVM bytecode)
- PBJ (PixelBender Binary file)
- PDF (only generic file structure and partial decryption)
- PEX (particle effect format)
- PNG (image file format)
- SWF (Flash file format)
- TAR (Archive)
- TGZ (TAR+GZ Archive)
- WAV (Raw sound)
- ZIP (Compressed Archive)
- GIF (Image file format - writer don't have tools)
- TGA (TARGA Image file format; Reader/Writer does not support developer data chunk; Writer does not support RLE encoding)
Available on haxelib, simply run the following command :
haxelib install format. To use the library, simply add
-lib format to your commandline parameters.
Each format lies in its own package, for example
format.pdf contains classes for PDF.
format.tools package contain some tools that might be shared by several formats but don't belong to a specific one.
Each format must provide the following files :
Data.hxfile that contain only data structures / enums used by the format. If there is really a lot, they can be separated into several files, but it's often my easy for the end user to only have to do one single
import format.xxx.Datato access to all the defined types.
Reader.hxclass which enable to read the file format from an
Writer.hxclass which enable to write the file format to an
- some other classes that might be necessary for manipulating the data structures
It's important in particular that the data structures storing the decoded information are separated from the actual classes manipulating it. This enable full access to all the file format infos and the ability to easily write libraries that manipulate the format, even if later the Reader implementation is changed for example.
We're accepting contributions if they are following the package structure rules (see above), please send them as Pull Requests.