mattkleiny / surreal Goto Github PK

Implementing a basic UI framework using a solid declarative technology like Xaml or a reactive approach like Flutter.

For telemetry with the application, profiling, etc, without the need to use other tools

The 2D graphics engine is a great place to start, and offers a good way to get all of the basics sketched out and working.

Key features:

• Texture manipulation and upload
• Mesh manipulation and upload
• Shader programs, linking and parsing
• Material management
  • Pipeline state management
  • Uniform value configuration
• Per-object shader effects
• Screen-wide post effects
• Basic camera system
• Sprite batch rendering

Nice to have extras:

• Sprite sheets
• Animated sprites
• Aseprite importer
• Tiled importer

• Single File
• Single File Trimmed
• Ready to Run
• Native AoT

More information is available here https://learn.microsoft.com/en-us/dotnet/core/deploying/

Silk.NET seems to offer a more robust and modern implementation of the bindings required for high-perf low level graphics and audio.

Consider migrating the core desktop platform (and perhaps other platforms) to be based on Silk.

Open in IDE · Open on GitHub

^{Created from JetBrains using CodeStream}

To offer the most flexibility, implement a fast but lightweight virtual machine that is capable of executing programs in various languages.

A basic 2d physics engine would enable some basic prototypes and example games:

• 2D collision resolution
• Varying collision shapes
  • Circles
  • Rectangles
• 2D rigidbody simulation
  • Gravity and friction
  • Collision response and restitution

The asset pipeline should result in artifacts that are optimal for each target platform.

An MSBuild task could simplify the act of building assets as part of the normal project compilation process.

An extensible basic editor story would enable future enhancements and get the basics in place.

• Asset database
• Asset importer
• Asset baking
• Game viewport hosting
• Game commands and events
• Support for extensible 'workloads' for different projects
• A basic property/metadata editor workload
• A basic graph editor workload
• A basic scene graph editor workload

An SDK-style project resolution strategy would make it trivial for users for Surreal to get all of the MSBuild configuration in order.

There are example SDKs here: https://github.com/microsoft/MSBuildSdks/tree/main.

Implement a similar SDK for Surreal, such that all platform dependencies and usings will be included as required.