42 releases

new 0.11.5 Apr 15, 2024
0.11.4 Mar 20, 2024
0.11.3 Feb 29, 2024
0.11.0 Dec 30, 2023
0.1.3 Mar 23, 2020

#19 in Caching

Download history 121/week @ 2023-12-25 176/week @ 2024-01-01 296/week @ 2024-01-08 380/week @ 2024-01-15 589/week @ 2024-01-22 603/week @ 2024-01-29 607/week @ 2024-02-05 695/week @ 2024-02-12 866/week @ 2024-02-19 1212/week @ 2024-02-26 675/week @ 2024-03-04 520/week @ 2024-03-11 750/week @ 2024-03-18 588/week @ 2024-03-25 436/week @ 2024-04-01 102/week @ 2024-04-08

1,930 downloads per month
Used in 7 crates (6 directly)

MIT/Apache

255KB
6K SLoC

Assets-manager

Crates.io Docs.rs Minimum rustc version

This crate aims at providing a filesystem abstraction to easily load external resources. It was originally thought for games, but can of course be used in other contexts.

Original idea was inspired by Veloren's assets system.

This crate follow semver convention and supports rustc 1.70 and higher. Changing this is considered a breaking change.

Goals

This crates focuses on:

  • Good performances:
    Crucial for perfomance-oriented applications such as games.
    Loaded assets are cached so loading one several times is as fast as loading it once. This crate was thought for use with concurrency.

  • Hot-reloading:
    Hot-reloading means updating assets in memory as soon as the corresponding file is changed, without restarting your program. It may greatly ease development.
    Your time is precious, and first-class support of hot-reloading helps you saving it.

  • Pleasant to use:
    A well-documented high-level API, easy to learn.
    Built-in support of common formats: serialization, images, sounds.
    Can load assets from a file system, a zip archive, or even embed them in a binary.

  • Lightness:
    Pay for what you take, no dependency bloat.

Example

Suppose that you have a file assets/common/position.ron containing this:

Point(
    x: 5,
    y: -6,
)

Then you can load it this way (with feature ron enabled):

use assets_manager::{Asset, AssetCache, loader};
use serde::Deserialize;

// The struct you want to load
#[derive(Deserialize)]
struct Point {
    x: i32,
    y: i32,
}

// Specify how you want the structure to be loaded
impl Asset for Point {
    // The extension of the files to look into
    const EXTENSION: &'static str = "ron";

    // The serialization format (RON)
    type Loader = loader::RonLoader;
}


// Create a new cache to load assets under the "./assets" folder
let cache = AssetCache::new("assets")?;

// Get a handle on the asset
// This will load the file `./assets/common/position.ron`
let handle = cache.load::<Point>("common.position")?;

// Lock the asset for reading
// Any number of read locks can exist at the same time,
// but none can exist when the asset is reloaded
let point = handle.read();

// The asset is now ready to be used
assert_eq!(point.x, 5);
assert_eq!(point.y, -6);

// Loading the same asset retrieves it from the cache
let other_handle = cache.load("common.position")?;
assert!(std::ptr::eq(handle, other_handle));

Hot-reloading is also very easy to use:

let cache = AssetCache::new("assets")?;
let handle = cache.load::<Point>("common.position")?;

loop {
    // Reload all cached files that changed
    cache.hot_reload();

    // Assets are updated without any further work
    println!("Current value: {:?}", handle.read());
}

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Dependencies

~0.8–37MB
~499K SLoC