Mirror of Svelto.ECS because we're a fan of it
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
sebas77 550c21851c add Exists<T>(egid), Fetch<T> and Has<T> 6 years ago
..
DataStructures moving toward EntityViewStruct 6 years ago
Dispatcher DispatchOnChange and DispatchOnSet must hold only value types 7 years ago
Extensions/Unity working on use just one data structure, still WIP and a lot of work to do 6 years ago
Profiler working on use just one data structure, still WIP and a lot of work to do 6 years ago
.gitignore working on a better folder structure 7 years ago
EGID.cs mega refactoring, now EntityView and EntityStructs use almost exactly the same code 6 years ago
EnginesRoot.DoubleBufferedEntityViews.cs move files in the right folder 6 years ago
EnginesRoot.GenericEntityFactory.cs working on use just one data structure, still WIP and a lot of work to do 6 years ago
EnginesRoot.GenericEntityFunctions.cs mega refactoring, now EntityView and EntityStructs use almost exactly the same code 6 years ago
EnginesRootEngines.cs moving toward EntityViewStruct 6 years ago
EnginesRootEntities.cs moving toward EntityViewStruct 6 years ago
EnginesRootSubmission.cs moving toward EntityViewStruct 6 years ago
EntityDescriptor.cs working on use just one data structure, still WIP and a lot of work to do 6 years ago
EntityFactory.cs moving toward EntityViewStruct 6 years ago
EntitySubmissionScheduler.cs clean up and fix more bugs 7 years ago
EntityViewBuilder.cs moving toward EntityViewStruct 6 years ago
EntityViewStructBuilder.cs moving toward EntityViewStruct 6 years ago
EntityViewUtility.cs moving toward EntityViewStruct 6 years ago
EntityViewsDB.cs add Exists<T>(egid), Fetch<T> and Has<T> 6 years ago
ExclusiveGroups.cs mega refactoring, now EntityView and EntityStructs use almost exactly the same code 6 years ago
GenericEntityDescriptor.cs Merge remote-tracking branch 'remotes/origin/entitystructrework' into EntityViewAsStruct 6 years ago
IEngine.cs working on use just one data structure, still WIP and a lot of work to do 6 years ago
IEntityDescriptorHolder.cs refactoring in progress 7 years ago
IEntityFactory.cs working on use just one data structure, still WIP and a lot of work to do 6 years ago
IEntityFunctions.cs refactoring complete (minus some improvements) 7 years ago
IEntityView.cs moving toward EntityViewStruct 6 years ago
IEntityViewBuilder.cs moving toward EntityViewStruct 6 years ago
IEntityViewsDB.cs add Exists<T>(egid), Fetch<T> and Has<T> 6 years ago
IQueryingEntityViewEngine.cs rename RemoveEntitiesGroup into DeleteEntityGroup 7 years ago
LICENSE working on a better folder structure 7 years ago
MixedEntityDescriptor.cs working on use just one data structure, still WIP and a lot of work to do 6 years ago
MultiEntitiesEngine.cs add Exists<T>(egid), Fetch<T> and Has<T> 6 years ago
MultiEntityViewsEngine.cs moving toward EntityViewStruct 6 years ago
README.md Merge remote-tracking branch 'remotes/origin/alpha' 7 years ago
Sequencer.cs fixed a serious bug that sneaked in because I trust too much the refactoring tools that this time failed miserably 7 years ago
SimpleSubmissionEntityViewScheduler.cs rename RemoveEntitiesGroup into DeleteEntityGroup 7 years ago
SingleEntityEngine.cs add Exists<T>(egid), Fetch<T> and Has<T> 6 years ago
SingleEntityViewEngine.cs moving toward EntityViewStruct 6 years ago

README.md

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.