Nicole L
The current method for code generation involves generating the binding code for all schema-defined types in a single Rust source file. While this approach is fairly simple, it has the...
Now that cargo-spatial is (about to be) on the master branch, we should start to discuss what sort of workflows should be supported, and what a good default workflow/setup would...
> ~~This issue is currently blocked by #27.~~ Allow the editor to request that an existing component be removed from an entity at runtime. To do this, add a variant...
> ~~This is currently blocked by #27.~~ Add a way for editors to request that a new component be added to an existing entity at runtime. The editor should specify...
In order to properly support serialization for types that contain an `Entity`, we need a way to create an intermediate type that converts entities and other non-stable data into a...
Add support for allowing the editor to request that a new entity be added to the game world. * Add a new variant to `IncomingMessage` called `CreateEntities` for requesting that...
> This ticket is blocked until #26 and #27 are complete. As defined in #26 and #27, we support syncing Components/Resources that only implement `Serialize`, but in a read-only fashion...
Currently `EditorLogger` only passes log output to the editor, but doesn't log anything to the local console. It would be good to also be able to pass log output through...
The core functionality of this crate, synchronizing component and resource data with an editor, isn't actually specific to Amethyst. Most of the functionality is still useful to projects that use...
Right now we use the user-provided names for Resources/Components to identify them when deserializing update data sent from the editor. While this is an *okay* solution in the short term,...