View Issue Details

IDProjectCategoryView StatusLast Update
0003821NoesisGUIC# SDKpublic2024-11-26 12:51
Reporterjhimes144 Assigned Tosfernandez  
PrioritynormalSeverityfeatureReproducibilityN/A
Status resolvedResolutionno change required 
Product Version3.2.6 
Summary0003821: Bad SDK Onboarding Experience
DescriptionAs a professional evaluating Noesis for a standalone app, I've had a difficult time onboarding.

Samples:

The state of the samples is not great. Some samples, such as integration, have a Data folder containing C# files, and a Src folder containing sparse c++ files. Meanwhile, project files are stored elsewhere, and are unbuildable. All projects, c++ and C# target old language versions. The .net samples for example, target .Net framework. I would recommend that the c++ samples use cmake and are buildable as-is. All C# samples should be using a .Net version from this decade (currently .Net 9)

The .net samples use a non-standard project structure, which requires manual update of project files and other issues. Please see how Avalonia's xplat template is structured. https://github.com/AvaloniaUI/avalonia-dotnet-templates/tree/main/templates/csharp/xplat

Ambiguity of a Stand-Alone solution:

In my opinion, Noesis has vast potential in the stand-alone application space, I came to Noesis because Avalonia and WPF do not meet my performance requirements. After evaluating Noesis' performance, I plan to move forward, but I've had issues.

The documentation defines an Application Framework, which is said to be open-source and contain a solution to build a stand-alone application with Noesis. I am unable to find a github repo for said framework. I was only able to find it in the sdk files, mashed together with the samples. The documentation states that the framework is not production ready. It does not say why, but says it should be adopted for each client's scenario. I find this confusing. I would think many clients have the simple issue of simply needing to create a single window stand-alone application. So why is the application framework not production ready? Is it simply because its strewn around in the samples? Is it not tested? Is it not complete? Can I find a roadmap for the application framework?
Steps To ReproduceN/A
TagsC#, C++, WPF
PlatformAny

Relationships

related to 0003825 assignedsfernandez C# Samples do not follow standard project structure 

Activities

jsantos

jsantos

2024-11-22 21:57

manager   ~0010153

What SDK is this about? C++ or C#?

Thanks for your time!
jhimes144

jhimes144

2024-11-22 22:01

reporter   ~0010154

jsantos,

I'm evaluating both! I'm more interested in the c++ sdk however.
jsantos

jsantos

2024-11-23 12:09

manager   ~0010155

Last edited: 2024-11-23 12:12

In C++, everything is automatically generated by our build scripts.

In the $(ROOT_SDK)/Build directory, you will find a solution file for every supported compiler. Is your compiler not supported? Our approach avoids the need for tools like CMake, which we believe introduces unnecessary dependencies and adds friction for new users.

We intentionally target C++11 for compatibility and simplicity.

Each sample’s Data folder (with a few exceptions, such as IntegrationGLUT) includes a Blend project. However, as we transition from Microsoft Blend to Noesis Studio in Noesis 4.0, this approach will be updated.

More information about Noesis Studio here: https://www.youtube.com/watch?v=B3q1f2E56Lw
jsantos

jsantos

2024-11-23 12:10

manager   ~0010156

I will clarify more about the state of Noesis App framework in the forums.

Thanks for your time!
jhimes144

jhimes144

2024-11-23 16:29

reporter   ~0010157

Last edited: 2024-11-23 18:24

Thank you for all the clarification! And dealing with me. Apparently I had some how nuked my sdk, but after extracting it again and opening everything up in visual studio everything built successfully the first time. I'm using MSVC compiler. I will be testing clang on mac here shortly.

I understand now the decision to not use cmake and a lower c++ version. Also, thank you for explaining the data folder structure.

Noesis studio looks awesome! Noesis isn't talked about enough from my world of application development, and I think you folks have something special here that can easily compete with crumbling MUI and the slowness of the other xaml frameworks out there in the .Net space. I hope you guys can work to improve the c# project samples.
jsantos

jsantos

2024-11-25 17:19

manager   ~0010161

Could you please create another ticket for the layout of the C# samples? Thanks

Issue History

Date Modified Username Field Change
2024-11-22 21:35 jhimes144 New Issue
2024-11-22 21:35 jhimes144 Tag Attached: C#
2024-11-22 21:35 jhimes144 Tag Attached: C++
2024-11-22 21:35 jhimes144 Tag Attached: WPF
2024-11-22 21:47 jhimes144 Description Updated
2024-11-22 21:57 jsantos Assigned To => jsantos
2024-11-22 21:57 jsantos Status new => assigned
2024-11-22 21:57 jsantos Note Added: 0010153
2024-11-22 21:57 jsantos Status assigned => feedback
2024-11-22 22:01 jhimes144 Note Added: 0010154
2024-11-22 22:01 jhimes144 Status feedback => assigned
2024-11-23 12:09 jsantos Note Added: 0010155
2024-11-23 12:10 jsantos Note Added: 0010156
2024-11-23 12:10 jsantos Status assigned => feedback
2024-11-23 12:10 jsantos Product Version 3.2.7 => 3.2.6
2024-11-23 12:12 jsantos Note Edited: 0010155
2024-11-23 16:29 jhimes144 Note Added: 0010157
2024-11-23 16:29 jhimes144 Status feedback => assigned
2024-11-23 18:24 jhimes144 Note Edited: 0010157
2024-11-25 17:18 jsantos Assigned To jsantos => sfernandez
2024-11-25 17:18 jsantos Category Documentation => C# SDK
2024-11-25 17:18 jsantos Summary Bad SDK Onboarding Experience => Improve layout samples of C# SDK
2024-11-25 17:19 jsantos Summary Improve layout samples of C# SDK => Bad SDK Onboarding Experience
2024-11-25 17:19 jsantos Status assigned => resolved
2024-11-25 17:19 jsantos Resolution open => no change required
2024-11-25 17:19 jsantos Note Added: 0010161
2024-11-26 12:51 jsantos Relationship added related to 0003825