How issarat/rust-bevy works
This is a small Bevy ECS demo: startup creates four people, then chained systems query their components and print names and employment reports. Person, Employed, and Job define the domain data. The graph reflects the only sampled source file; no README documents additional capabilities.
Main entry points: main.rs App entry
Components 14
Other components
- Console user
- App entry
src/main.rs - Bevy runtime
- PeoplePlugin
src/main.rs - Setup people
src/main.rs - Person
src/main.rs - Employment data
src/main.rs - Job enum
src/main.rs - ECS world
- Print names
src/main.rs - People with jobs
src/main.rs - Ready for hire
src/main.rs - Report jobs
src/main.rs - Standard output
Connections 21
- Console user → App entry: starts
- App entry → Bevy runtime: runs app
- App entry → PeoplePlugin: adds plugin
- PeoplePlugin → Bevy runtime: registers systems
- Bevy runtime → Setup people: dispatches startup
- Bevy runtime → Print names: dispatches startup
- Bevy runtime → People with jobs: dispatches startup
- Bevy runtime → Ready for hire: dispatches startup
- Bevy runtime → Report jobs: dispatches startup
- Setup people → ECS world: spawns entities
- ECS world → Person: stores component
- ECS world → Employment data: stores component
- Employment data → Job enum: contains job
- Print names → ECS world: queries people
- People with jobs → ECS world: queries without employment
- Ready for hire → ECS world: queries without employment
- Report jobs → ECS world: queries employed people
- Print names → Standard output: prints names
- People with jobs → Standard output: prints report
- Ready for hire → Standard output: prints report
- Report jobs → Standard output: prints job titles