Samples updated for 1.0.0-pre.15

Author: BrianWill-Unity

.gitignore

@@ -0,0 +1,67 @@
+# This .gitignore file should be placed at the root of your Unity project directory
+#
+# Get latest from https://github.com/github/gitignore/blob/master/Unity.gitignore
+#
+[Ll]ibrary/
+[Tt]emp/
+[Oo]bj/
+[Bb]uild/
+[Bb]uilds/
+[Ll]ogs/
+[Mm]emoryCaptures/
+[Uu]ser[Ss]ettings/
+
+
+# Asset meta data should only be ignored when the corresponding asset is also ignored
+!/[Aa]ssets/**/*.meta
+
+# Uncomment this line if you wish to ignore the asset store tools plugin
+# /[Aa]ssets/AssetStoreTools*
+
+# Autogenerated Jetbrains Rider plugin
+[Aa]ssets/Plugins/Editor/JetBrains*
+
+# Visual Studio cache directory
+.vs/
+
+# Gradle cache directory
+.gradle/
+
+# Autogenerated VS/MD/Consulo solution and project files
+ExportedObj/
+.consulo/
+*.csproj
+*.unityproj
+*.sln
+*.suo
+*.tmp
+*.user
+*.userprefs
+*.pidb
+*.booproj
+*.svd
+*.pdb
+*.mdb
+*.opendb
+*.VC.db
+
+# Unity3D generated meta files
+*.pidb.meta
+*.pdb.meta
+*.mdb.meta
+
+# Unity3D generated file on crash reports
+sysinfo.txt
+
+# Builds
+*.apk
+
+# Crashlytics generated file
+crashlytics-build.properties
+
+# Custom
+Assets/SceneDependencyCache*
+Assets/NetCodeGenerated*
+.idea/
+.DS_Store
+RiderScriptEditorPersistedState.asset

Docs/additional-entities-features.md

@@ -39,7 +39,7 @@ For instance, the `EntityManager` has these key methods:
 | :- |
 | For the sake of the job safety checks, read or write access of a component's enabled state requires read or write access of the component type itself. |
 
-🕹 *[See examples of checking and setting the enabled state of components](../examples/components_systems.md#enableable-components).*
+🕹 *[See examples of checking and setting the enabled state of components](./examples/components_systems.md#enableable-components).*
 
 In an `IJobChunk`, the `Execute` method parameters signal which entities in the chunk match the query:
 
@@ -50,7 +50,7 @@ In an `IJobChunk`, the `Execute` method parameters signal which entities in the
 | :- |
 | The `chunkEnabledMask` is a *composite* of all the enabled states of the enableable components included in the query of the job. To check enabled states of individual components, use the `IsComponentEnabled()` and `SetComponentEnabled()` methods of the `ArchetypeChunk`. |
 
-🕹 *[See an example `IJobChunk` that correctly accounts for disabled components](../examples/jobs.md#ijobchunk).*
+🕹 *[See an example `IJobChunk` that correctly accounts for disabled components](./examples/jobs.md#ijobchunk).*
 
 <br>
 

Docs/baking.md

@@ -13,7 +13,7 @@ Baking a Sub Scene is done in a few main steps:
 2. The Baker of each authoring component in the Sub Scene is executed. Each Baker can read the authoring component and add components to the corresponding entity.
 2. The baking systems execute. Each system can read and modify the baked entities in any way: set components, add components, remove components, create additional entities, or destroy entities. Unlike Bakers, baking systems should not access the original GameObjects of the Sub Scene.
 
-🕹 *[See examples of authoring components, Bakers, and baking systems.](../examples/baking.md)*
+🕹 *[See examples of authoring components, Bakers, and baking systems.](./examples/baking.md)*
 
 When modified, a Sub Scene is re-baked:
 
@@ -58,7 +58,7 @@ The [`SceneSystem`](https://docs.unity3d.com/Packages/com.unity.entities@latest?
 | [`GetScenePath()`](https://docs.unity3d.com/Packages/com.unity.entities@latest?subfolder=/api/Unity.Entities.ICleanupComponent.html)  | Returns the path of a scene asset (specified by its GUID). |
 | [`GetSceneEntity()`](https://docs.unity3d.com/Packages/com.unity.entities@latest?subfolder=/api/Unity.Entities.ICleanupComponent.html)  | Returns the entity representing a scene (specified by its GUID). |
 
-🕹 *[See examples of loading and unloading entity scenes and sections.](../examples/baking.md#scene-loading)*
+🕹 *[See examples of loading and unloading entity scenes and sections.](./examples/baking.md#scene-loading)*
 
 | ⚠ IMPORTANT |
 | :- |

Docs/components.md

@@ -118,7 +118,7 @@ An [`EntityQuery`](https://docs.unity3d.com/Packages/com.unity.entities@latest?s
 
 A query can also specify component types to *exclude* from the matching archetypes. For example, if a query looks for all entities having component types *A* and *B* but *not* having component type *C*, the query would match entities with component types *A* and *B*, but the query would *not* match entities with component types *A*, *B*, and *C*.
 
-🕹 *[See examples of creating and using queries](../examples/components_systems.md#querying-for-entities).*
+🕹 *[See examples of creating and using queries](./examples/components_systems.md#querying-for-entities).*
 
 
 <br>
@@ -139,7 +139,7 @@ In order to allow entity indexes to be reused after an entity is destroyed, each
 
 The most common, basic kind of component type is defined as a struct implementing [`IComponentData`](https://docs.unity3d.com/Packages/com.unity.entities@latest?subfolder=/api/Unity.Entities.IComponentData.html).
 
-&#x1F579;  *[See examples of creating and using `IComponentData` components.](../examples/components_systems.md#icomponentdata)*
+&#x1F579;  *[See examples of creating and using `IComponentData` components.](./examples/components_systems.md#icomponentdata)*
 
 An `IComponentData` struct is expected to be unmanaged, so it cannot contain any managed field types. Specifically, the allowed field types are:
 
@@ -179,7 +179,7 @@ If a managed component type implements `ICloneable`, then any resources it conta
 
 A [`DynamicBuffer`](https://docs.unity3d.com/Packages/com.unity.entities@latest?subfolder=/api/Unity.Entities.DynamicBuffer-1.html) is a component type which is a resizable array. To define a `DynamicBuffer` component type, create a struct that implements the [`IBufferElementData`](https://docs.unity3d.com/Packages/com.unity.entities@latest?subfolder=/api/Unity.Entities.IBufferElementData.html) interface.
 
-&#x1F579;  *[See examples of creating and using `DynamicBuffer` components](../examples/components_systems.md#dynamicbuffers-ibufferelementdata).*
+&#x1F579;  *[See examples of creating and using `DynamicBuffer` components](./examples/components_systems.md#dynamicbuffers-ibufferelementdata).*
 
 The buffer of each entity stores a `Length`, a `Capacity`, and a pointer:
 
@@ -228,7 +228,7 @@ A `DynamicBuffer<T>` can be '[reinterpreted](https://docs.unity3d.com/Packages/c
 
 An aspect is an object-like wrapper over a subset of an entity's components. Aspects can be useful for simplifying queries and component-related code. The [`TransformAspect`](https://docs.unity3d.com/Packages/com.unity.entities@latest?subfolder=/api/Unity.Transforms.TransformAspect.html), for example, groups together the standard transform components ([`LocalTransform`](https://docs.unity3d.com/Packages/com.unity.entities@latest?subfolder=/api/Unity.Transforms.LocalTransform.html), [`ParentTransform`](https://docs.unity3d.com/Packages/com.unity.entities@latest?subfolder=/api/Unity.Transforms.ParentTransform.html), and [`WorldTransform`](https://docs.unity3d.com/Packages/com.unity.entities@latest?subfolder=/api/Unity.Transforms.WorldTransform.html)).
 
-&#x1F579;  *[See examples of creating and using aspects](../examples/components_systems.md#aspects)*.
+&#x1F579;  *[See examples of creating and using aspects](./examples/components_systems.md#aspects)*.
 
 Including an aspect in a query is the same as including the components wrapped by the aspect, *e.g.* a query that includes `TransformAspect` includes the standard transform matrix components.
 

Docs/editor-tools.md

@@ -6,7 +6,7 @@ You can offload the processing of entity data to worker threads with the [C# Job
 - [`IJobChunk`](https://docs.unity3d.com/Packages/com.unity.entities@latest?subfolder=/api/Unity.Entities.IJobChunk.html), whose `Execute()` method is called once for each individual chunk matching the query.
 - [`IJobEntity`](https://docs.unity3d.com/Packages/com.unity.entities@latest?subfolder=/api/Unity.Entities.IJobEntity.html), whose `Execute()` method is called once for each entity entity matching the query. 
 
-🕹 *[See examples of IJobChunk](../examples/jobs.md#ijobchunk) [and IJobEntity](../examples/jobs.md#ijobentity).*
+🕹 *[See examples of IJobChunk](./examples/jobs.md#ijobchunk) [and IJobEntity](./examples/jobs.md#ijobentity).*
 
 Although `IJobEntity` is generally more convenient to write and use, `IJobChunk` provides more precise control. In most cases, their performance is identical for equivalent work.