Just to confirm we’re aligned:

Our assumption is that you'll have multiple Studio projects (one per Unreal plugin). Each of these projects will be referenced by the main project, which can then access data from the referenced projects using their namespaces.

Is that correct?

Hi,
We only have one Noesis studio project.
Having several project would allow us to set a different namespace but for now we prefer to stick to 1.

For example I have a Framework plugin that just define the base scaffolding of the UI (a Main view class, a few basic viewmodel that are meant to be inherited) but I do not want to provide any content in this plugin. So I just want to be able to tell Noesis studio in the structure folder :

• "Here is MyFramework.BaseMenuViewModel, it has those properties".
  That would allow me to then set properly the children of this viewmodel for specific implementation.

Another use of this would be to rely on scripted Viewmodel where we would like to create for example a blueprint based Viewmodel with a specific.

As I said. It currently work if I create the .xml myself and use the Namespace property in the outer tag. Once that done, noesis studio shows it properly and I can create my children viewmodel as usual.

After today's discussion with the team, we agreed on implementing the following:

• When a new type is created, it will be assigned by default to the project's namespace. This default value can be changed in the Properties panel by entering a different namespace. A namespace can contain multiple dot-separated levels.
• The namespace will be used to visually organize types into virtual folders. This hierarchy will make it easier to manage projects with a large number of types. Additionally, each folder will include a (+) button to create new types directly within that namespace.
• Namespaces must always be written to the XML files. Currently, the default namespace is omitted, but this behavior will be changed.

Please, share your feedback.