Summary

At the moment fetching is currently forced into a Vec<u8>. This was for easy portability into having dynamic loading in the future, and to not change the API later.

It would be nice to have the ability to actually fetch it as a constant &'static [u8] and since it is loaded at compile-time that is totally possible. Since the future will have dynamic loading though as well, the API will be Option<&'static [u8]> where Some(T) will be for all compile-time loaded variants that actually have a static lifetime and None will be returned for the other cases.

Summary

Currently, Asset doesn't implement a trait on the type being derived on. This is necessary to have for type portability (trait objects, trait bounds, etc).

The internal structure has to shift a little bit, but the main API will remain the same. the Asset trait will be both derivable with the macro still and can be manually derived as well if so desired.

As for implementation of this... getters should stay in the main enum's impl, but the fetch method should maybe be moved to the trait? I have ideas for a custom loading setup for the future, so I have to figure out what fit's best here.

I'm all ears as always.

Summary

Added static fetching of resources via a new Asset trait method fetch_static which will return an Option<&'static [u8]> when called on an Asset derived type.

This feature is somewhat larger, crate is now 0.1.3.

Firstly, the entire repo had to be restructured because proc-macro crates with cargo are a genuine pain to work with so 2 crates at minimum are required to be able to use them effectively.

This all being said... here is what was changed/added:

• #4 : Asset Trait added.
• Licenses moved from GPL-3 to a dual license of MIT and Apache-2
• Repo restructured to house 2 crates.
• Crate added for internal macro.

Summary

Add asset-derive support to Struct data types as well instead of only enums.

Idea

I realized with the trait addition #4 , it made having struct's being asset's themselves quite simple. Simply derive the Asset trait on it and the struct itself will have its own filename and asset to fetch. It is limitted to just one asset (unless we do fields in the future too) but it wouldn't be restricting to just enums.

Summary

Add an attribute for prefixing all variant filenames.

Idea

Currently, Variant names are just lowercased and used as the filename. You can always specify a filename too on a Variant, but what if you want all filenames to be prefixed, maybe by a random string, maybe by the enum name, up to you.

use asset_derive::Asset;

#[derive(Asset)]
#[asset(prefix = "icon-")] // <-- Default for this enum, all filenames will be prefixed with `icon-`.
enum Icon {
    Select,
    Folder,
    #[asset(prefix = "icon-dim-")] // <-- This Variant will override the default prefix for itself.
    FolderDim,
}

Conclusion

It isn't that useful of a feature, but it definitely is an idea and something that could be added.

Summary

Add support for loading assets at runtime instead of just compile time (in the binary).

Idea

I believe this should be quite simple to implement once compile time loading is fully fleshed out. I have an idea for some sub-attributes that would work for this and they would generate a function load() that will handle the loading.

use asset_derive::Asset;

#[derive(Asset)]
#[asset(load = "static")] // <-- Default for this enum
enum Icon {
    Select,
    Folder,
    #[asset(load = "dynamic")] // <-- This Variant will not be loaded in at compile time, but will get a function to load in at runtime...
    FolderDim,
}

Conclusion

Still more to flesh out, but this sounds solid enough and shouldn't be too difficult to implement.