Dear team

Im new to Noesis, working in it for less than a week now. There's not much I know about building UIs at all, so my feedback might be negligible. First I have to say that capabilities Noesis is providing are just tremendous. So many things can be done with code only, and much of it - in Noesis Studio, this is wonderful, thank you!

Now to the things that confuse me. I understand, that every decision had reasons behind it, and probably I just don't see them, but looking at it with fresh eyes might help. Might not.

1. What is the reason for Resources separate tab existense? If I want to browse resources in a certain page - i need to click to Assets tab, select that page in the assets viewer window below, switch to Resources tab, view my resources there, and now I want to see resources of a different page - I repeat the loop.

Suggestion: display files in the actual folders, and in asset view (where files are currently displayed) - show resources


2. There's a preview for resources inside a file - cool. But when I preview a globaldictionary with merged resources into it - it appears empty. Which is mislediang, because I need to look into resources tab and see for myself that it has merged things inside.

Suggestion: show it in preview separated by merged dictionaries?


3. Again about preview of resources: currently it's impossible to group things, they are all just crammed together, thankfully sorted alphabetically.

Suggestion: add separators (which will render as comments inside xaml) to the preview


4. This I just don't understand. I opened viewtopic.php?t=3863 another topic recently mentioning that xaml shows errors while unity and noesis render fine. Yes, it happened with Noesis language server connected in VScode. Now I have the opposite problem: xaml shows everything's fine, but Noesis renders Esc_Menu_View_Styles.xaml as red (I guess it means having errors inside)

Suggestion: show what the error is about. Noesis already knows there's an eror, thats why it glows red. So show it.


5. This is probably related to the previous point, but whenever I edit styles.xaml manually - GlobalResources automatically loses merged dictionaries and I need to merge them back in.

6. Using of templates within styles is somewhat not intuitive. I created a template for a button in the page. Then I wanted to extract that template in a style, so that it would be accessible by other pages. In xaml I put it inside a style. In Noesis all I could do - is to add the template alongside style inside styles.xaml. Maybe it is not meant to be inside a style, not sure, but my intention is that when editing a button on a page - I want to style it, and template would be applied. But that's probably just me experience.


7. I would add screenshots to every point in question, but on phpBB forum I would have to save each screenshot and attach it separately as a file, which is a lot of overhead instead of just pasting from clipboard.

Suggestion: There are currently many, and out of those - two solid in my opinion forum engines: Discource (Path Of Exile uses it) and NodeBB. Both are easy to migrate to, you might want to consider that, just in case you were thinking about it as well.


And again: I am very glad your product exist, because uGUI is a nightmare, and Microsoft Blender - I don't even want to open it.
And also: you are extremely responsive both in email and here, thank you a lot!

Project attached

Hello!

First of all, thank you so much for taking the time to write this out. Feedback from users with "fresh eyes" is incredibly valuable to us, especially while Noesis Studio is in Beta. You’ve touched on several areas that are currently on our internal roadmap for improvement.

Here is some context on the points you raised:

1) You’ve hit the nail on the head. The Resources tab is one of the older sections of Studio and is currently slated for a significant redesign. It is a complex panel, and our ultimate target is offering a workflow that allows you to manage resources seamlessly without having to "tab-hop" as much.

2) 3) We agree that the current preview doesn't handle merged dictionaries or large lists elegantly. We are planning to overhaul the previewer to support nested structures and better organization (including the separators you suggested).

4) This is a known limitation of the current language server implementation. Please feel free to open a ticket about this.

5) What you’re describing, merged dictionaries disappearing during a manual edit, is definitely a bug. We’d love to fix this; please report it here so our team can investigate the specific scenario.

6) The current workflow involves moving both the template and the style to resources, and then, within your style, setting the template that exists in the dictionary. I understand this isn't immediately obvious, and we are working on making this "template-to-style" workflow much more intuitive.

7) Migrating to Discourse has been considered many times. It is a big move for our knowledge base, but I assume at some point it will happen to improve the community experience.

Thanks again for the kind words and for helping us make Noesis better!