Blender_bevy_components_wor.../testing/bevy_registry_export/basic
Mark Moissette 20b6fa6077
feat(bevy_components): set of fixes & improvements (#128)
* fixed issue with "reload registry" not clearing previous data
 * added watcher/ poll system to automatically updated the registry & components list when the registry file has been changed
* BREAKING CHANGE ! changed internal representation of components, incompatible with v0.1, breaks UI values.
* added buttons to regenerate UI to account for/fix the above and to offer the ability to regenerate UI values from custom property values
* lots of cleanups
* added tests 
* closes #127 
* closes #124 
* closes #121 
* closes #130
2024-02-18 17:14:31 +01:00
..
assets feat(bevy_components): set of fixes & improvements (#128) 2024-02-18 17:14:31 +01:00
src feat(bevy_components): set of fixes & improvements (#128) 2024-02-18 17:14:31 +01:00
Cargo.toml feat(bevy_components): set of fixes & improvements (#128) 2024-02-18 17:14:31 +01:00
README.md feat(bevy_components): set of fixes & improvements (#128) 2024-02-18 17:14:31 +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.