zxt:format
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
zxt:format [2021/08/08 09:01] – asie | zxt:format [2021/08/10 13:00] (current) – asie | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== ZXT Extension Format Specification (Draft) ====== | ====== ZXT Extension Format Specification (Draft) ====== | ||
+ | |||
+ | <WRAP center round important 50%> | ||
+ | This page is for draft work! For the latest official version of the ZXT specification, | ||
+ | </ | ||
Version ?.?.? | Version ?.?.? | ||
Line 222: | Line 226: | ||
* Multiple concatenated extension headers may be used as a feature in the future - for example, for faciliating multi-patch application for ZZT worlds. | * Multiple concatenated extension headers may be used as a feature in the future - for example, for faciliating multi-patch application for ZZT worlds. | ||
- | ===== Implementations | + | ===== Future Suggestions |
+ | |||
+ | ==== ZXT 2.0 ==== | ||
+ | |||
+ | ==== ZXT 1.1 ==== | ||
- | This is not a formal | + | * Unified way of handling external file dependencies (for example, large music files). |
+ | * Approach A: Add a bit which signifies that the data of an extension block is actually the filename of the file containing the real data. | ||
+ | * Approach B: Add a single extension with a list of external filenames used by the world. | ||
+ | * Approach C: Add a set of extensions to allocate "asset IDs" or "asset names", | ||
+ | * Approach D: Do nothing. | ||
+ | * Only approach A would need to be discussed as part of a spec update. | ||
+ | * Add a bit which signifies "if this extension is not supported, | ||
+ | * Rationale: For example, multiple charset sizes (8x14, 6x8, 4x6, etc.) for different platforms. | ||
- | ==== ZXT 1.0.x ==== | + | ===== Comments ===== |
- | * [[https:// | + | ~~DISCUSSION~~ |
zxt/format.txt · Last modified: 2021/08/10 13:00 by asie