A library for using blorb files in rust
This library is an implementation of the Blorb 2.0.4 specification. The specification can be found at the following web address. A copy of the specification can also be found in the top level of this repository.
Blorbs are a resource file type used in Interactive Fiction (IF). They bundle together images, text, sounds, and other resources, along with executable code, for IF interpreters to use.
This library gives access to blorb and blorb file types. It provides structures to examine the contents of blorbs and handle them in a logical way. Additionally, it provides a lazy access interface to the blorb contents, allowing interpreters to use blorbs without handrolling their own way to access the file without dumping the entire contents into memory.
There are three primary interfaces to the blorb filetype provided in this library.
- Blorb Reader
- Provides methods for taking a blorb file and loading them into memory in a structured format.
- TODO: This has yet to be implemented.
- Blorb Writer
- Provides methods for taking blorb structures and turning them into blorb files.
- TODO: This has yet to be implemented.
- Blorb Cursor
- Provides methods to access blorb resources in a lazy manner.
The blorb cursor is structure which provides lazy access to the contents of a blorb.
BlorbCursors are created from blorbs, using the BlorbCursor<R: Read + Seek>::from_file(src: R)
function.
The BlorbCursor
object, when built, does validates the structure of the blorb file,
and loads the metadata from the blorb. It provides a BlorbCursor::load_resource(u32)
method which can then be used to lazily load a blorb resource, such as an image or sound.
If the blorb contains an executable resource, it will be returned from calling
BlorbCursor::load_resource(0)
. The returned value from calling this method is a variant of the Chunk
enum, allowing the handling of the loaded resource to be done with a match
.
The Blorb crate can be build using stable rust 1.13 and later.
To build, run the following command:
cargo build
Before any changes are merged in, the following checks should be made:
- run
cargo build
and verify completion without any warnings - run
cargo test
and verify completion without any warnings or test failures - run
cargo doc
and verify completion without any issues - run
rustup run nightly cargo build
and verify completion without any warnings - run
rustup run nightly cargo test
and verify completion without any warnings or test failures - run
rustup run nightly cargo doc
and verify completion without any issues - run
rustup run nightly cargo clippy
and verify completion without any warnings