ecsly 0.0.1-dev.6

Experimental ECS core for Dart/Flutter (early prerelease).

Changelog

0.0.1-dev.6

• Recorded richer benchmark machine metadata, including Mac model, CPU, and RAM.
• Added game-perspective benchmark metrics for frame p95/p99, render-packet-like extraction, packet bytes, and spawn/despawn churn.
• Updated benchmark docs to map metrics back to prototype perf concerns.
• Bumped package version metadata to 0.0.1-dev.6.

0.0.1-dev.5

• Added a benchmark results ADR and generated-report workflow.
• Expanded benchmark/run.dart with JSON, Markdown, single-pass report files, and limit-scan modes for stronger benchmark evidence.
• Added generated benchmark result artifacts under benchmark/results/.
• Added README/DX FAQ benchmark commands and report-reading guidance.
• Bumped package version metadata to 0.0.1-dev.5.

0.0.1-dev.4

• Removed the remaining internal ecs.dart barrel path from the published archive by renaming it to src/ecsly.dart.
• Updated the public ecsly.dart entrypoint to export src/ecsly.dart.
• Bumped package version metadata to 0.0.1-dev.4.

0.0.1-dev.3

• Fixed license/attribution naming language to consistently use ecsly.
• Removed the legacy package:ecsly/ecs.dart public entrypoint.
• Expanded README with concrete startup + usage guidance from DX_FAQ.md and selected DESIGN_FAQ.md expectations.
• Added two tiny runnable examples:
  • example/basic_world.dart
  • example/scheduled_run.dart
• Updated examples to avoid duplicating game2d_plugin movement components and keep custom extension/object components intentional in the scheduled example.
• Moved quickstart/example rationale into DX_FAQ.md and DESIGN_FAQ.md, keeping README concise for pub.dev.
• Bumped package version metadata to 0.0.1-dev.3.

0.0.1-dev.2

• Package documentation metadata now points to autogenerated pub.dev documentation.
• Updated package readme publish links away from private repository paths.
• Adjusted maintainer workflow notes after docs/publication surface cleanup.

0.0.1-dev.1

• Initial super-experimental early prerelease release.
• API is evolving quickly and may change without semver guarantees until stable.
• Public APIs and diagnostics are provided on a best-effort basis.
• Acknowledgement: ecsly builds on foundational ideas inspired by the open ECS ecosystem, including Bevy and EnTT, and many other developers who advanced data-oriented architecture in game and simulation tooling.