Hello,

I'm evaluating Noesis for a stand alone application. This is in regards to the native api. Earlier I made a post of the .net api but I'm going back and forth on deciding between the native solution and C# solution. This a stand alone application that will run on Windows, Mac, and Linux. The documentation says you should not use the application framework as-is as its not production ready, with a mention saying you must tweak to your requirements. Looking at the source code, I do not see any areas that stick out that would deviate from my desire to "create a standalone exe app that creates a window" requirement. At least yet. The entry points are simple pass thrus of main() for my platform targets. My question is then, other than the concern of not meeting requirements, does the Noesis team have a different reason to why the Application Framework is not production ready? Such as, lack of reliability, outstanding issues, not battle tested? The application framework seems to directly exist to solve a ubiquitous requirement that is "I want to create a desktop app with Noesis", which I can imagine many people not just myself need to solve.

EDIT:
I see there is the integration sample which states "this uses nothing from the application framework except for display and render context classes". This is perfect because those two things are exactly what I don't want to create. Also, the code shows areas where I could implement animation callbacks on the UI thread (WPF equivelent of CompositionTarget.Rendering), I did not see another area where I could do this in the application framework examples.

Opened this issue: https://www.noesisengine.com/bugs/view.php?id=3821

Hello,

Noesis is a bit different to other products you probably have used before like Avalonia. Noesis is not a framework that gives you all kind of helpers (threads, windows, mutexes) to create multi-plaform applications. Noesis is just a minimalistic UI library where you are supposed to bring your own engine or application framework. Noesis has been designed in a very minimalist and non intrusive way, meaning that we are not creating threads or allocating memory or even interacting with the GPU behind your backs. You are supposed to implement these things on top of Noesis.

That said, our SDK includes sample projects, which require a basic application framework built on top of Noesis. This framework is specifically designed to meet the needs of these samples and nothing more. It is not production-ready in the sense that it hasn't been as rigorously tested as the Noesis core, nor is it widely used by our clients.

If additional functionality is required—such as support for multiple windows—it will not be added unless necessary for our samples. This is intentional, as we aim to keep the framework small, simple, and focused solely on demonstrating how to use Noesis effectively.

I hope this helps :)