zxt:format
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
zxt:format [2021/08/08 09:10] – asie | zxt:format [2021/08/10 13:00] (current) – asie | ||
---|---|---|---|
Line 225: | Line 225: | ||
* Some implementations may store ZZT data in a custom format internally, and removing this requirement can make their code simpler. | * Some implementations may store ZZT data in a custom format internally, and removing this requirement can make their code simpler. | ||
* 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. | ||
+ | |||
+ | ===== Future Suggestions ===== | ||
+ | |||
+ | ==== ZXT 2.0 ==== | ||
+ | |||
+ | ==== ZXT 1.1 ==== | ||
+ | |||
+ | * 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, the immediately following extension may be used as its substitute." | ||
+ | * Rationale: For example, multiple charset sizes (8x14, 6x8, 4x6, etc.) for different platforms. | ||
===== Comments ===== | ===== Comments ===== | ||
~~DISCUSSION~~ | ~~DISCUSSION~~ |
zxt/format.txt · Last modified: 2021/08/10 13:00 by asie