https://github.com/old-storyai/shipyard_app

WIP opinionated ECS set up for Shipyard
https://github.com/old-storyai/shipyard_app

ecs game-development shipyard

Last synced: about 2 months ago
JSON representation

WIP opinionated ECS set up for Shipyard

• Host: GitHub
• URL: https://github.com/old-storyai/shipyard_app
• Owner: old-storyai
• License: apache-2.0
• Created: 2020-08-27T12:59:42.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2022-01-03T15:56:12.000Z (about 3 years ago)
• Last Synced: 2023-03-11T18:53:55.051Z (almost 2 years ago)
• Topics: ecs, game-development, shipyard
• Language: Rust
• Homepage:
• Size: 300 KB
• Stars: 8
• Watchers: 0
• Forks: 3
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE-APACHE

Awesome Lists containing this project

README

        
# shipyard_app

`shipyard_app` aims to provide a standardized "Plugin" interface on top of the [`shipyard` ECS crate](https://github.com/leudz/shipyard).

This allows for codebases to more easily divide up many systems and workloads without having to declare all systems in one big workload builder in the root of an application.

Example [from test/tree.rs](https://github.com/storyai/shipyard_app/blob/master/src/test/tree.rs)

```rust

use shipyard_app::{AppBuilder, Plugin};

...

/// Registers

#[derive(Default)]

pub struct TreePlugin;

impl Plugin for TreePlugin {

    fn build(&self, app: &mut AppBuilder) {

        app.update_pack::("update in response to ChildOf changes");

        app.add_system(indexing::tree_indexing);

    }

}

```

## Usage

At the moment, shipyard_app is based off the master branch of https://github.com/leudz/shipyard, so until the updates to WorkloadBuilder are published, you must be on the master branch of shipyard.

The initial interface takes a lot of inspiration from [bevy_app]. Thanks @cart!

[bevy_app]: https://github.com/bevyengine/bevy/tree/b925e22949ee1ca990dfc6a678d8e4636cae5271/crates/bevy_app

#### License



Licensed under either of Apache License, Version

2.0 or MIT license at your option.








Unless you explicitly state otherwise, any contribution intentionally submitted

for inclusion in this crate by you, as defined in the Apache-2.0 license, shall

be dual licensed as above, without any additional terms or conditions.