Forums | NoesisGUI

Hey all, first time posting and admittedly new to both Noesis and the WPF space. The first Studio release is looking awesome and there's a lot that we're excited about! Thanks for the great work and really cool stuff so far :^)

One thing I haven't been able to find is how to set the backing C++ Class (I'm working on a native integration) for a given component within Studio via something like the x:Class property. When trying to manually add this to the XAML, Studio will display an error due to the unknown class and will often remove this property when next saving changes.

Is there another method I'm missing to tie the screens to C++ classes? Would we have to compile the Studio source with the class definitions similar to how I'm assuming it would function with custom Element types?

Apologies if I'm missing something obvious and thanks for any help.

Thanks for posting here!

At Studio, we prioritize pure MVVM (Model-View-ViewModel) approaches to enhance workflows for designers. A great example of this is our use of Components, which allow designers to create UserControls independently, without requiring programmer intervention. Currently, in the alpha version, properties can be dynamically added to components, and we plan to extend this functionality to events in the future.

However, it's important to note that Studio aims to be compatible with any externally written XAML. We shouldn't remove any x:Class entry and we should offer a way in the UX to assign this x:Class, likely under the Name box. I have created a ticket (#3372) for this.

For classes to be available, right now you need to compile Studio from source code and register all your extensions in the factory. Looking ahead, we are considering implementing a plugin mechanism to extend Studio using dynamic libraries.

Makes sense, thanks for the info and the ticket!