02b45cc4

Guide
- Move sets
- Pose constraints
- The variation harness
- Getting content into a running game
- Components
- Entity queries
- Booleans and handoff
- The editing pipeline
- Element selection
- Face materials
- Foliage mode
- Icons
- The editor shell
- Editable meshes in a scene
- Editor modes
- Building to a number
- Scene menus
- The shape tool
- Snapping
- Sub-object picking
- Sculpt and paint mode
- Writing an editor plugin
- Block-out shapes
- Booting an application
- Character movement
- Editable meshes
- Growing a forest
- Foliage instances
- Grass
- Mesh booleans
- Mesh operations
- Mesh surfaces
- Networked players
- Players and possession
- Splines
- Terrain brushes
- The terrain heightfield
- Painting a terrain
- Sculpting a heightfield
- Saving and restoring a world
- Admission, health and the control plane
- Durable state and the ledger
- Placing players
- Placing realms
- Shards, keys and specs
- The cluster
- The service plane
- Transfer tickets
- Transferring players
- Upgrading a fleet
- Writing a realm
- Drawing foliage
- Drawing grass
- Impostors
- Culling and streaming instances
- Turning on dynamic global illumination
- Meshes and materials, type by type
- Drawing particles
- Lighting a scene in lux and lumens
- Making a room look different
- The post-processing node kinds
- Making everything cast a shadow
- Drawing a terrain
By kind
- Components39
- Systems48
- Controls165
- Shaders48
- Graph nodes64
- Importers22
- Annotations45
- Diagnostics8
- Log events64
All namespaces275
Releases1

IPlatformFactory

interface

Core/Vixen.App.Hosting/AppBackends.cs:27

csharp

public interface IPlatformFactory

Where an application's platform comes from.

Read the guide page for this →

Remarks

The seam that lets the host live below the backends it boots on. Choosing between the desktop platform and the headless one means referencing both, and both are in Platform/ — which CheckArchitecture forbids a Core/ assembly from doing, because a reference upward makes the lower layer unusable without the higher one. So the choice is asked for rather than made, and PlatformHost in the Vixen.App package is the one implementation that ships.

⚠ One method, and no registry. There are two platforms that can run in a desktop process and the choice between them is one question. Android, iOS and Web are separate app heads with separate entry points — a phone cannot fall back to the desktop platform — so there is nothing for a registry to select between there either.

Methods (1)

IPlatform Create(AppConfig config)
Builds the platform an application asked for.

Used by (3)

AppBuilderVixen.App.Hosting
FactoryVixen.App
PlatformHostVixen.App