Blender_bevy_components_wor.../testing/bevy_example
kaosat.dev 0ca57ba6de feat(bevy_components): continued refactor to use long names instead of short names & co
* changed all various uses of short name to long_name
 * same for type_names
 * also changed bevy_registry_export to output "long_name" instead of "title" for coherence
 * related changes & tweaks
 * still WIP
2024-05-05 22:04:25 +02:00
..
art chore(testing): moved blend files into "art" folder 2024-04-26 23:01:58 +02:00
assets feat(bevy_components): continued refactor to use long names instead of short names & co 2024-05-05 22:04:25 +02:00
src feat(bevy_components): added basic of hashmap/map support 2024-05-03 00:22:51 +02:00
Cargo.toml test(auto_export): 2024-03-20 17:57:06 +01:00
README.md feat(gltf_auto_export): component filtering for exports, bug-fixes and tests(#143) 2024-02-27 00:12:14 +01:00

README.md

Bevy registry export example/demo

This example showcases

  • the use of the bevy_registry_export crate to extract all components & types information into a json file.
  • That file is then used by the Blender addon to create Uis for each component, to be able to add & edit Bevy components easilly in Blender !

Running this example

cargo run --features bevy/dynamic_linking

Running the example also regenerates the registry.json file.