feat(animation) : Animation fixes and improvements

README-workflow-ui.md

@@ -8,7 +8,7 @@ The workflow goes as follows (once you got your Bevy code setup)
 
 ## Component creation
 
-Setup the Blender [bevy_components](./tools/bevy_components/README.md) add-on
+Setup the Blender [bevy_components](./tools/blenvy/README.md) add-on
 to add & edit your components visually & reliably
 
 ![bevy_components](./docs/bevy_components.png)
@@ -22,7 +22,7 @@ to add & edit your components visually & reliably
         - custom properties
         - cameras & lights if you want a complete level (as in this example)
         ![gltf_export](./docs/gltf_export.png)
-    - or much better, using [gltf_auto_export](./tools/gltf_auto_export/)
+    - or much better, using [blenvy](./tools/blenvy/)
 
 ## Now use your gltf files in Bevy
 

README.md

@@ -2,7 +2,7 @@
 [![License](https://img.shields.io/crates/l/bevy_gltf_components)](https://github.com/kaosat-dev/Blender_bevy_components_workflow/blob/main/LICENSE.md)
 [![ko-fi](https://ko-fi.com/img/githubbutton_sm.svg)](https://ko-fi.com/F1F5TO32O)
 
-# Blender_bevy_components_workflow
+# BLENVY: a friendly Blender <=> Bevy workflow !
 
 ![demo](./docs/blender_bevy.png)
 
@@ -18,8 +18,7 @@ It also allows you to setup 'blueprints' in Blender by using collections (the re
 
 * Useful if you want to use Blender (or any editor allowing to export gltf with configurable gltf_extras) as your Editor
 * define Bevy components as custom properties in Blender (some visually , some using RON, though an older JSON version is also available)
-* no plugin or extra tools needed in Blender (but I provide a [little Blender add-on](./tools/gltf_auto_export/README.md) to auto-export to gltf on save (and more !) if you want !)
-* now also with a nice UI tool to add & edit Bevy components in [Blender](./tools/bevy_components/README.md)
+* now also with an UI tool to add & edit Bevy components, automatically export gltf blueprints & more in [Blender](./tools/blenvy/README.md)
 * define components in Blender Collections & override any of them in your collection instances if you want
 * ability to automatically turn your Blender collections into [gltf Blueprints](./crates/bevy_gltf_blueprints/README.md) for reuse
 * minimal setup & code,  you can have something basic running fast
@@ -45,23 +44,19 @@ bevy_gltf_blueprints to only save a minimal subset of dynamic data, seperating d
 The examples for the crate are [here](./examples/bevy_gltf_save_load/)
     > Note: this uses ```bevy_gltf_blueprints``` under the hood
 
-- [bevy_registry_export](./crates/bevy_registry_export/) This crate adds the ability to export your project's Bevy registry to json, in order to be able to generate custom component UIs on the Blender side in the Blender [bevy_components](./tools/bevy_components/README.md) add-on
+- [bevy_registry_export](./crates/bevy_registry_export/) This crate adds the ability to export your project's Bevy registry to json, in order to be able to generate custom component UIs on the Blender side in the Blender [blenvy](./tools/blenvy/README.md) add-on
 
 
 ## Tools
 
-### Blender: gltf_auto_export
+### Blender: blenvy
 
-- for convenience I also added a [Blender addon](./tools/gltf_auto_export/README.md) that automatically exports your level/world from Blender to gltf whenever you save your Blend file
-- it also supports automatical exports of collections as [Gltf blueprints](./crates/bevy_gltf_blueprints/README.md) & more !
+- an all in one [Blender addon](./tools/blenvy/README.md) for the Blender side of the workflow: 
+    - allow easilly adding & editing Bevy components , using automatically generated UIs for each component
+    - automatically exports your level/world from Blender to gltf whenever you save your Blend file
+    - it also supports automatical exports of collections as [Gltf blueprints](./crates/bevy_gltf_blueprints/README.md) &
 
-Please read the [README]((./tools/gltf_auto_export/README.md)) of the add-on for installation & use instructions
-
-### Blender: bevy_components
-
-- an add-on for Blender to allow easilly adding & editing Bevy components , using automatically generated UIs for each component
-
-Please read the [README]((./tools/bevy_components/README.md)) of the add-on for installation & use instructions
+Please read the [README]((./tools/blenvy/README.md)) of the add-on for installation & use instructions
 
 
 

RELEASE_NOTES.md

@@ -0,0 +1,36 @@
+This new release has a lot of breaking changes in the Blender tooling as well as in the Bevy crates
+Here is a rundown + rationale behing the changes:
+
+
+- Blender add-ons
+    - Auto_export: 
+        - spliting out of gltf exporter settings
+            up until now , the auto export add-on provided a *subset* of gltf settings, causing issues due to lack of features (in particular for animation settings),
+            and it required me to play catch up every time there where added / changed settings
+            the Ui of Blender's gltf exporter is NOT reusable in any form or way inside another add-on . I tried various solutions such as turning the auto exporter
+            into a 'extension' of the standard exporter, but none of them worked in a reliable or 'nice to use' way
+
+            So I decided to split the gltf settings from the auto_export setting, this has multiple advantages:
+                * access to ALL gltf settings
+                * the gltf UI & settings will always keep up with the official releases
+                * less maintenance work
+
+            The only disadvantage is that the standard gltf exporter is a normal exporter, so it generates a 'fake' gltf file that immediatly gets deleted after export, 
+            so you will need to use the new side panel to set your gltf settings:
+             * this is also done to ensure that the gltf settings settings used for auto export are NOT interfering with the ones you might use when exporting gltf files normally
+
+        - change detection :
+        after spending MANY hours analysing the issues with change detection (using some of Blender's built in logic) I came to the conclusion that it was not going to be reliable enough, so I opted for a 'hand made' brute force approach to change detection:
+         * every time you save (& thus export), all your scenes are serialized / hashed and that hashed version is compared to the one from the last save to determine what changed and what did not
+
+        - handling of external/ embeded / split etc collections
+            while adding tests I also realised that the detection of which main scenes & blueprints that needed to be exported was faulty, so I rewrote all the code in charge of that : this means that in general , based on your settings, the add-on will more accuratly export only those levels/blueprints that really NEED to be exported
+
+        - improved handling of multi-blend file projects
+            Up until now, all export paths where relative ** to the blend file itself** which could lead to issues when working with multiple blend files
+            Also for future improvements regarding assets managment, I changed the export paths to be relative to a new "project root" folder which is your *Bevy project's root folder*
+            - the levels/worlds now also got a seperate setting so you can easilly set where to export them too (they are not dumped out into the main export folder anymore), giving you more control over your non blueprint exports
+
+    - bevy_components
+        Up until now , it was not possible to have multiple components with the same name (ie ) as all the logic was based on short names
+        This required completely changing HOW/WHERE components are stored in objects, and they are now stored inside a 'bevy_components' custom property

crates/bevy_gltf_blueprints/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "bevy_gltf_blueprints"
-version = "0.10.0"
+version = "0.11.0"
 authors = ["Mark 'kaosat-dev' Moissette"]
 description = "Adds the ability to define Blueprints/Prefabs for Bevy inside gltf files and spawn them in Bevy."
 homepage = "https://github.com/kaosat-dev/Blender_bevy_components_workflow"
@@ -14,8 +14,8 @@ license = "MIT OR Apache-2.0"
 workspace = true
 
 [dependencies]
-bevy_gltf_components = { version = "0.5", path = "../bevy_gltf_components" }
-bevy = { version = "0.13", default-features = false, features = ["bevy_asset", "bevy_scene", "bevy_gltf", "bevy_animation", "animation"] }
+bevy_gltf_components = { version = "0.6", path = "../bevy_gltf_components" }
+bevy = { version = "0.14.0-rc.3", default-features = false, features = ["bevy_asset", "bevy_scene", "bevy_gltf", "bevy_animation", "animation"] }
 
 [dev-dependencies]
-bevy = { version = "0.13", default-features = false, features = ["dynamic_linking"] }
+bevy = { version = "0.14.0-rc.3", default-features = false, features = ["dynamic_linking"] }

crates/bevy_gltf_blueprints/README.md

@@ -15,9 +15,8 @@ A blueprint is a set of **overrideable** components + a hierarchy: ie
     * just a Gltf file with Gltf_extras specifying components 
     * a component called BlueprintName
 
-Particularly useful when using [Blender](https://www.blender.org/) as an editor for the [Bevy](https://bevyengine.org/) game engine, combined with the Blender add-ons that do a lot of the work for you 
-- [gltf_auto_export](https://github.com/kaosat-dev/Blender_bevy_components_workflow/tree/main/tools/gltf_auto_export)
-- [bevy_components](https://github.com/kaosat-dev/Blender_bevy_components_workflow/tree/main/tools/bevy_components) 
+Particularly useful when using [Blender](https://www.blender.org/) as an editor for the [Bevy](https://bevyengine.org/) game engine, combined with the Blender add-on that do a lot of the work for you 
+- [blenvy](https://github.com/kaosat-dev/Blender_bevy_components_workflow/tree/main/tools/blenvy)
 
 
 ## Usage
@@ -101,11 +100,8 @@ fn main() {
     App::new()
         .add_plugins((
              BlueprintsPlugin{
-                library_folder: "advanced/models/library".into() // replace this with your blueprints library path , relative to the assets folder,
-                format: GltfFormat::GLB,// optional, use either  format: GltfFormat::GLB, or  format: GltfFormat::GLTF, or  ..Default::default() if you want to keep the default .glb extension, this sets what extensions/ gltf files will be looked for by the library
                 aabbs: true, // defaults to false, enable this to automatically calculate aabb for the scene/blueprint
                 material_library: true,  // defaults to false, enable this to enable automatic injection of materials from material library files
-                material_library_folder: "materials".into() //defaults to "materials" the folder to look for for the material files
                 ..Default::default()
             }
         ))
@@ -294,7 +290,6 @@ Ie for example without this option, 56 different blueprints using the same mater
 you can configure this with the settings:
 ```rust
 material_library: true  // defaults to false, enable this to enable automatic injection of materials from material library files
-material_library_folder: "materials".into() //defaults to "materials" the folder to look for for the material files
 ```
 
 > Important! you must take care of preloading your material librairy gltf files in advance, using for example ```bevy_asset_loader```since 
@@ -306,24 +301,6 @@ see https://github.com/kaosat-dev/Blender_bevy_components_workflow/tree/main/exa
 Generating optimised blueprints and material libraries can be automated using the latests version of the [Blender plugin](https://github.com/kaosat-dev/Blender_bevy_components_workflow/tree/main/tools/gltf_auto_export)
 
 
-## Legacy mode
-
-Starting in version 0.7 there is a new parameter ```legacy_mode``` for backwards compatibility
-
-To disable the legacy mode: (enabled by default)
-
-```rust no_run
-BlueprintsPlugin{legacy_mode: false}
-```
-
-
-You **need** to disable legacy mode if you want to use the [```bevy_components```](https://github.com/kaosat-dev/Blender_bevy_components_workflow/tree/tools_bevy_blueprints/tools/bevy_components) Blender addon + the [```bevy_registry_export crate```](https://crates.io/crates/bevy_registry_export) ! 
-As it create custom properties that are writen in real **ron** file format instead of a simplified version (the one in the legacy mode)
-
-
-> Note: the legacy mode support will be dropped in future versions, and the default behaviour will be NO legacy mode
-
-
 ## Examples
 
 https://github.com/kaosat-dev/Blender_bevy_components_workflow/tree/main/examples/bevy_gltf_blueprints/basic