5 years ago · 9d74a94d88
--- a/README.md
+++ b/README.md
@@ -1,81 +1,82 @@
 # Svelto Entity Component System 2.8

 =====================================

 Real ECS framework for c#. Enables to write encapsulated, decoupled, maintainable, highly efficient, data oriented, cache friendly, multi-threaded, code without pain. Although the framework is platform agnostic (compatible with c# 7 and .net standard 2.0), it comes with several Unity extensions. 
 Real ECS framework for c\#. Enables to write encapsulated, decoupled, maintainable, highly efficient, data oriented, cache friendly, multi-threaded, code without pain. Although the framework is platform agnostic \(compatible with c\# 7 and .net standard 2.0\), it comes with several Unity extensions.

 ## Why using Svelto.ECS with Unity?

 _Svelto.ECS wasn't born just from the needs of a large team, but also as result of years of reasoning behind software engineering applied to game development(*). Compared to Unity.ECS the main goals and reasons for Svelto.ECS to exist are different enough to justify its on going development (plus Svelto is platform agnostic, so it has been written with portability in mind). Svelto.ECS hasn't been built just to develop faster code, it has been built to help develop better code. Performance gain is one of the benefits in using Svelto.ECS, as ECS in general is a great way to write cache-friendly code, but the main reasons why Svelto.ECS has been written orbit around the shifting of paradigm from Object Oriented Programming, the consequent improvement of the code design and maintainability, the approachability by junior programmers that won't need to worry too much about the architecture and can focus on the solution of the problems thanks to the rigid directions that the framework gives. Svelto.ECS is the result of years of iteration of the ECS paradigm applied to real game development with the intent to be "junior coder proof"._
 _Svelto.ECS wasn't born just from the needs of a large team, but also as result of years of reasoning behind software engineering applied to game development\(\*\). Compared to Unity.ECS the main goals and reasons for Svelto.ECS to exist are different enough to justify its on going development \(plus Svelto is platform agnostic, so it has been written with portability in mind\). Svelto.ECS hasn't been built just to develop faster code, it has been built to help develop better code. Performance gain is one of the benefits in using Svelto.ECS, as ECS in general is a great way to write cache-friendly code, but the main reasons why Svelto.ECS has been written orbit around the shifting of paradigm from Object Oriented Programming, the consequent improvement of the code design and maintainability, the approachability by junior programmers that won't need to worry too much about the architecture and can focus on the solution of the problems thanks to the rigid directions that the framework gives. Svelto.ECS is the result of years of iteration of the ECS paradigm applied to real game development with the intent to be "junior coder proof"._

 ## Official Examples

 * **Mini Examples**: https://github.com/sebas77/Svelto.MiniExamples (including articles)
 * **Unity Boids Simulation**: https://github.com/sebas77/Svelto.ECS.Examples.Boids (including article)
 * **Mini Examples**: [https://github.com/sebas77/Svelto.MiniExamples](https://github.com/sebas77/Svelto.MiniExamples) \(including articles\)
 * **Unity Boids Simulation**: [https://github.com/sebas77/Svelto.ECS.Examples.Boids](https://github.com/sebas77/Svelto.ECS.Examples.Boids) \(including article\)

 ## Official Articles

 **Framework articles:**

 * http://www.sebaslab.com/introducing-svelto-ecs-2-8/  (shows what's changed since 2.7)
 * http://www.sebaslab.com/svelto-2-7-whats-new-and-best-practices/ (shows what's changed since 2.5)
 * http://www.sebaslab.com/svelto-ecs-2-5-and-allocation-0-code/ (shows what's changed since 2.0)
 * http://www.sebaslab.com/svelto-ecs-2-0-almost-production-ready/ (shows what's changed since 1.0)
 * http://www.sebaslab.com/ecs-1-0/
 * http://www.sebaslab.com/learning-svelto-ecs-by-example-the-unity-survival-example/
 * http://www.sebaslab.com/learning-svelto-ecs-by-example-the-vanilla-example/
 * http://www.sebaslab.com/svelto-ecs-svelto-tasks-to-write-data-oriented-cache-friendly-multi-threaded-code-in-unity/

 **Theory related articles (in order of publishing date):**

 * http://www.sebaslab.com/ioc-container-for-unity3d-part-1/
 * http://www.sebaslab.com/ioc-container-for-unity3d-part-2/
 * http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-i-dependency-injection/
 * http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-ii-inversion-of-control/
 * http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-iii-entity-component-systems/
 * http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-iv-dependency-inversion-principle/
 * http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-v-drifting-away-from-ioc-containers/
 * http://www.sebaslab.com/the-quest-for-maintainable-code-and-the-path-to-ecs/
 * [http://www.sebaslab.com/introducing-svelto-ecs-2-8/](http://www.sebaslab.com/introducing-svelto-ecs-2-8/)  \(shows what's changed since 2.7\)
 * [http://www.sebaslab.com/svelto-2-7-whats-new-and-best-practices/](http://www.sebaslab.com/svelto-2-7-whats-new-and-best-practices/) \(shows what's changed since 2.5\)
 * [http://www.sebaslab.com/svelto-ecs-2-5-and-allocation-0-code/](http://www.sebaslab.com/svelto-ecs-2-5-and-allocation-0-code/) \(shows what's changed since 2.0\)
 * [http://www.sebaslab.com/svelto-ecs-2-0-almost-production-ready/](http://www.sebaslab.com/svelto-ecs-2-0-almost-production-ready/) \(shows what's changed since 1.0\)
 * [http://www.sebaslab.com/ecs-1-0/](http://www.sebaslab.com/ecs-1-0/)
 * [http://www.sebaslab.com/learning-svelto-ecs-by-example-the-unity-survival-example/](http://www.sebaslab.com/learning-svelto-ecs-by-example-the-unity-survival-example/)
 * [http://www.sebaslab.com/learning-svelto-ecs-by-example-the-vanilla-example/](http://www.sebaslab.com/learning-svelto-ecs-by-example-the-vanilla-example/)
 * [http://www.sebaslab.com/svelto-ecs-svelto-tasks-to-write-data-oriented-cache-friendly-multi-threaded-code-in-unity/](http://www.sebaslab.com/svelto-ecs-svelto-tasks-to-write-data-oriented-cache-friendly-multi-threaded-code-in-unity/)

 **Theory related articles \(in order of publishing date\):**

 * [http://www.sebaslab.com/ioc-container-for-unity3d-part-1/](http://www.sebaslab.com/ioc-container-for-unity3d-part-1/)
 * [http://www.sebaslab.com/ioc-container-for-unity3d-part-2/](http://www.sebaslab.com/ioc-container-for-unity3d-part-2/)
 * [http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-i-dependency-injection/](http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-i-dependency-injection/)
 * [http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-ii-inversion-of-control/](http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-ii-inversion-of-control/)
 * [http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-iii-entity-component-systems/](http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-iii-entity-component-systems/)
 * [http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-iv-dependency-inversion-principle/](http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-iv-dependency-inversion-principle/)
 * [http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-v-drifting-away-from-ioc-containers/](http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-v-drifting-away-from-ioc-containers/)
 * [http://www.sebaslab.com/the-quest-for-maintainable-code-and-the-path-to-ecs/](http://www.sebaslab.com/the-quest-for-maintainable-code-and-the-path-to-ecs/)

 Note: I included the IoC articles just to show how I shifted over the years from using an IoC container to use an ECS framework and the rationale behind its adoption.

 **The perfect companion for Svelto.ECS is Svelto.Tasks to run the logic of the Systems even on other threads!**

 * https://github.com/sebas77/Svelto.Tasks
 * [https://github.com/sebas77/Svelto.Tasks](https://github.com/sebas77/Svelto.Tasks)

 ## Users Generated Content

 **User experiments (may use old versions of Svelto)**
 **User experiments \(may use old versions of Svelto\)**

 * https://github.com/grovemaster/Unity3D-Game-App
 * https://github.com/colonelsalt/ZombieDeathBoomECS
 * [https://github.com/grovemaster/Unity3D-Game-App](https://github.com/grovemaster/Unity3D-Game-App)
 * [https://github.com/colonelsalt/ZombieDeathBoomECS](https://github.com/colonelsalt/ZombieDeathBoomECS)

 _Please share your Svelto projects with me!_

 **Users articles (may use old versions of Svelto)**
 **Users articles \(may use old versions of Svelto\)**

 * https://eagergames.wordpress.com/category/ecs/ (Dario Oliveri)
 * https://blogs.msdn.microsoft.com/uk_faculty_connection/2018/05/08/entity-component-system-in-unity-a-tutorial/ (Lee Stott)
 * [https://eagergames.wordpress.com/category/ecs/](https://eagergames.wordpress.com/category/ecs/) \(Dario Oliveri\)
 * [https://blogs.msdn.microsoft.com/uk\_faculty\_connection/2018/05/08/entity-component-system-in-unity-a-tutorial/](https://blogs.msdn.microsoft.com/uk_faculty_connection/2018/05/08/entity-component-system-in-unity-a-tutorial/) \(Lee Stott\)

 _If you write an article about Svelto, please let me know, I will add it here!_

 **User made inspectors (may use old versions of Svelto)**
 **User made inspectors \(may use old versions of Svelto\)**

 * https://github.com/sebas77/Svelto.ECS.Debugger (work just started)
 * https://github.com/NED-Studio/LGK.Inspector (probably not working anymore)
 * [https://github.com/sebas77/Svelto.ECS.Debugger](https://github.com/sebas77/Svelto.ECS.Debugger) \(work just started\)
 * [https://github.com/NED-Studio/LGK.Inspector](https://github.com/NED-Studio/LGK.Inspector) \(probably not working anymore\)

 **Official Chat**

 * https://discord.gg/3qAdjDb 
 * [https://discord.gg/3qAdjDb](https://discord.gg/3qAdjDb) 

 **Unity official forum thread (I don't update it anymore):**
 **Unity official forum thread \(I don't update it anymore\):**

 * https://forum.unity.com/threads/open-source-svelto-ecs-lightweight-entity-component-system-for-c-and-unity.502163/
 * [https://forum.unity.com/threads/open-source-svelto-ecs-lightweight-entity-component-system-for-c-and-unity.502163/](https://forum.unity.com/threads/open-source-svelto-ecs-lightweight-entity-component-system-for-c-and-unity.502163/)

 **Note: don't beat yourself up if you find Svelto.ECS hard to use at first. The framework is very light in features, but it forces the use of a new coding paradigm and shifting code paradigm is hard! I will try to clarify all the concepts writing more and more articles**

 ## In case of bugs

 Best option is to fork and clone https://github.com/sebas77/Svelto.ECS.Tests, add a new test to reproduce the problem and request a pull. Then open a github, I come here pretty often :). Also feel free to contact me on twitter or leave comments on the blog!
 Best option is to fork and clone [https://github.com/sebas77/Svelto.ECS.Tests](https://github.com/sebas77/Svelto.ECS.Tests), add a new test to reproduce the problem and request a pull. Then open a github, I come here pretty often :\). Also feel free to contact me on twitter or leave comments on the blog!

 ## [The Github wiki page](https://github.com/sebas77/Svelto.ECS/wiki)

@@ -83,14 +84,13 @@ It needs love and as far as I understood, anyone can edit it. Feel free to do so

 ## I like the project, how can I help?

 Hey thanks a lot for considering this. You can help in several ways. The simplest is to talk about Svelto.ECS and spread the word, more we are, better it is for the community. Then you can help with the documentation, updating the wiki or writing your own articles. 
 Svelto.ECS has all the features needed to make a game with the ECS pattern, but many tools are still missed: visual debugger and generic serialization to name a few. Other platforms other than Unity need a lot of love too, like Xenko, Godot and monogame. Porting to other languages, expecially c++, would be awesome! 
 Hey thanks a lot for considering this. You can help in several ways. The simplest is to talk about Svelto.ECS and spread the word, more we are, better it is for the community. Then you can help with the documentation, updating the wiki or writing your own articles. Svelto.ECS has all the features needed to make a game with the ECS pattern, but many tools are still missed: visual debugger and generic serialization to name a few. Other platforms other than Unity need a lot of love too, like Xenko, Godot and monogame. Porting to other languages, expecially c++, would be awesome!

 ## Svelto Framework is used to develop the following products\(\*\):

 ## Svelto Framework is used to develop the following products(*):
 ![Robocraft Infinity](https://news.xbox.com/en-us/wp-content/uploads/Robocraft_Hero-hero.jpg) ![Cardlife](https://i.ytimg.com/vi/q2jaUZjnNyg/maxresdefault.jpg)

 ![Robocraft Infinity](https://news.xbox.com/en-us/wp-content/uploads/Robocraft_Hero-hero.jpg)
 ![Cardlife](https://i.ytimg.com/vi/q2jaUZjnNyg/maxresdefault.jpg)
 \*if you want your products made with Svelto here, just send me an email or whatever, I'll be super happy to add them.

 *if you want your products made with Svelto here, just send me an email or whatever, I'll be super happy to add them.
 _**Note: Dear Svelto Users : Although I am committed to help you and write articles as much as I can, I will never be able to keep all the documentation up to date. If you are a happy svelto user and you want to contribute, please feel free to update the github wiki! 🙏👊**_

 **_Note: Dear Svelto Users : Although I am committed to help you and write articles as much as I can, I will never be able to keep all the documentation up to date. If you are a happy svelto user and you want to contribute, please feel free to update the github wiki! 🙏👊_**
--- a/SUMMARY.md
+++ b/SUMMARY.md
@@ -0,0 +1,4 @@
 # Table of contents

 * [Svelto Entity Component System 2.8](README.md)

--- a/Svelto.ECS.Components/Svelto.ECS.Components.asmdef
+++ b/Svelto.ECS.Components/Svelto.ECS.Components.asmdef
@@ -1,23 +0,0 @@
 {
    "name": "Svelto.ECS.Components.Unity",
    "references": [
        "Unity.Mathematics",
        "Svelto.ECS",
        "Svelto.Common"
    ],
    "optionalUnityReferences": [],
    "includePlatforms": [],
    "excludePlatforms": [],
    "allowUnsafeCode": false,
    "overrideReferences": false,
    "precompiledReferences": [],
    "autoReferenced": true,
    "defineConstraints": [],
    "versionDefines": [
        {
            "name": "com.unity.mathematics",
            "expression": "0.0.9",
            "define": "UNITY_MATHEMATICS"
        }
    ]
 }
--- a/Svelto.ECS/README.md
+++ b/Svelto.ECS/README.md
@@ -1,50 +0,0 @@
 Svelto Entity Component System for Unity
 =====================================

 **Note: The alpha stage of Svelto 2.0 is almost completed, so if you are here to experiment with it, please use the current alpha branch**

 Real Entity-Component-System for c# and Unity (it can be adapted for other c# platforms too). Enables to write encapsulated, uncoupled, highly efficient, data oriented, cache friendly, multi-threaded, code without pain.

 you can find working examples to learn how to use the framework here:

 https://github.com/sebas77/Svelto-ECS-Example (unity)

 https://github.com/sebas77/Svelto.ECS.Vanilla.Example (.net core and standard)

 I advise to clone the example repositories separately from the framework one, both under the same Unity project Assets folder.

 relative article:

 http://www.sebaslab.com/svelto-ecs-2-0-almost-production-ready/

 http://www.sebaslab.com/ecs-1-0/

 If you want to know more about the theory and rationale behind this framework:

 http://www.sebaslab.com/ioc-container-for-unity3d-part-1/

 http://www.sebaslab.com/ioc-container-for-unity3d-part-2/

 http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-i-dependency-injection/

 http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-ii-inversion-of-control/

 http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-iii-entity-component-systems/

 http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-iv-dependency-inversion-principle/

 http://www.sebaslab.com/the-truth-behind-inversion-of-control-part-v-drifting-away-from-ioc-containers/

 new article on optimizations:

 http://www.sebaslab.com/svelto-ecs-svelto-tasks-to-write-data-oriented-cache-friendly-multi-threaded-code-in-unity/

 Note: if you ever build something with Svelto.ECS that you can share with the community, please do and let me know. Other coders need more examples.

 Copyright (c) Sebastiano Mandalà

 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

 The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
--- a/Svelto.ECS/Svelto.ECS.asmdef
+++ b/Svelto.ECS/Svelto.ECS.asmdef
@@ -1,15 +0,0 @@
 {
    "name": "Svelto.ECS",
    "references": [
        "Svelto.Common"
    ],
    "optionalUnityReferences": [],
    "includePlatforms": [],
    "excludePlatforms": [],
    "allowUnsafeCode": false,
    "overrideReferences": false,
    "precompiledReferences": [],
    "autoReferenced": true,
    "defineConstraints": [],
    "versionDefines": []
 }