add asset source support

[Aqaao]

allow load assets with source, like embedded asset.

embedded_asset!(app, "path/ui.libgdx.atlas");
embedded_asset!(app, "path/ui.libgdx.png");

asset_server.load("embedded://create/mod/path/ui.libgdx.atlas")

[extrawurst]

Oh thats awesome! Could you provide one example that makes use of that please

[Aqaao]

Oh thats awesome! Could you provide one example that makes use of that please

added.

[extrawurst]

I dont think we need new assets for this example, we can just use the existing ones and actually lets animate like in the original example

[Aqaao]

I dont think we need new assets for this example, we can just use the existing ones and actually lets animate like in the original example

I think so too ,but I must copy the existing assets into example folder, because embedded_assets marco only use relative paths, and directly embedding file from assets folder via a relative path will result in generated asset paths that are perplexing.

// call embedded macro in /examples/some_example.rs
embedded_asset!(app, "examples", "../assets/animation_sheet.libgdx.atlas");
embedded_asset!(app, "examples", "../assets/animation_sheet.png");
// generated asset path
asset_server.load("embedded://../assets/animation_sheet.libgdx.atlas")
// if you call embedded macro in /src/some_dir/some_file.rs, it will be even worse.
asset_server.load("embedded://workspace/../../assets/animation_sheet.libgdx.atlas")

That’s also why I didn’t add the example — nobody would use embedded_asset!() in a game development environment. I use bevy_embedded_assets to embed the assets folder, and it creates readable asset paths for me.

I think the best is to just mention in the documentation that asset source works. Adding a confusing example would only make people more puzzled.

[extrawurst]

I think the best is to just mention in the documentation that asset source works. Adding a confusing example would only make people more puzzled.

sounds good to me. can you add that?