Hello, I know that the recommended way to use and organize our projects using studio is to take the DataTemplate approach to mount our UI.
However, the current UI of Noesis studio makes it quite unintuitive to iterate using this instead of simple pages, based system.
For example, let's say I have a default template for MyMenuViewModel, this template is put on a xaml resource dictionary that is merged inside the Global dictionary.

To edit it I need to :

• Click on Assets Icon (Ctrl+1)

• Open a Sample page (or a MainPage I could use on the project)

• Click on Data Icon and find my Viewmodel type.

• if not already created, create a sample data set

• assign it to the currently opened page

• Right click in the viewport and Template>Content>Edit Current

Once arriving on that edit, I lost the data set context as the property window appeared so iterating takes a lot of back and forward between set/structure and property panel.

I understand why it works like this because this is how WPF works. But if there was a way to offer a path that requires less clicks for the most common user story.

For example:
- Have a menu list all the Viewmodels and the template attached to them (where they actually are stored can be displayed but is secondary).
- Double click one to open it, ready to edit with a DataSet already attached (changeable but prevents a step)
Once there I am technically ready to go to do my edits.

In addition I was thinking if there's some way we could reorganize the panels so we can both edit the property panel and the data set without constantly lose context while iterating.

Hello!

Thanks for the great feedback.

In the latest versions of Studio, we've added small Back and Forward buttons to the Properties panel. For example, you can now navigate from a property with an assigned resource to the resource itself, edit it, and then use these buttons to return to the original property.

We also plan to extend this functionality further. For example, you'll be able to navigate from bound properties directly to the ViewModel (and back), or from a DataSet to its Structure, and so on.

Would this address your use case?

Hi Jesus,

It does sound like a step in the correct direction but a back and forward system still require to click in and out of contexts while being able to modify the data set while also changing the DataTemplate would be good for a smooth iterating environment.

Any step to make it more integrated for designer to not have to setup their testing scenario every time they want to do a small edit would be nice as well.

If we compare to UMG in Unreal for example double clicking a Widget in the content browser most likely bring you immediately to the correct view ready to be edited.
Due to the DataTemplate nature of WPF, I understand how it can feel different but if I try to put myself in the shoes of someone who just want to put a textbox or a bar in a HealthBarViewModel and bind it to a Value, it still requires to:
- Find where this DataTemplate is stored.
- Open it by navigating either in resources
- Click on edit
OR
- insert it in a page using a data set that would have an instance of HealthBarViewModel already attached
- And bind it to a ContentControl.
- then rightclick>templates>Content>edit current.

Which are a lot of clicks for Gameplay designers who would want to quickly prototype an idea for example and don't use Noesis studio on a regular basis.

Here are some ideas that I think could help without dramatically changing the existing UI:
- a way to find any resources available at the application resource level and navigate / go to edit it immediately in place
- a way to modify an on the fly dataset for DataTemplate who have a DataType (we already know which type it is expecting so not having to navigate to Data>Create a DataSet>Attach is that many step we could maybe avoid.

There are many interesting points raised in your comments. After discussing the different alternatives with the team, we'd love to schedule a call with you to talk them through. I'll send you a PM to arrange it.