Forums | NoesisGUI

For context, I'm messing with the XAML UI, and am a C++ programmer.

I've looked at https://www.noesisengine.com/docs/Gui.C ... orial.html, and wanted to make sure I understand - is it suggested to develop the UI in Blend using C# classes and then port those classes to C++? (adding reflection etc) Is that the tightest iteration loop possible?

I imagined that I would have a blend project in my C++ solution alongside the native projects - much like the sample solution in the C++ SDK - but not sure how one would work with the XAML in Blend while still getting the real-time design feedback in its visual/design editor window without C# classes. So then I'd have to maintain two copies of the code-behind for everything; one in C# and one in C++, manually keeping them in sync.

Am I missing anything in the native+XAML workflow?

No you're not missing anything. You might want to go talk to the Rider guys or whoever does Visual Studio extensions and get them to support Noesis
then we could edit XAML projects that are not WPF in Visual studio. Unfortunately even if you're working with a unity project you can share the code, but you still cennot edit the XAML without opening a special WPF project.
It's a bit of a pain.

So then I'd have to maintain two copies of the code-behind for everything; one in C# and one in C++, manually keeping them in sync.

Yes, that's correct right now. Long-term we are working on a solution to improve this. Meanwhile we recommend the following:

• Minimize code-behind by using MVVM
• Minizime inheriting from Noesis classes by using Interactity
• The implementation in C# doesn't need to be complete, in fact just an empty class is probably enough for the designer. A few studios are auto-generating this stubs using Noesis reflection. That's something we can implement too in the short-term.