Hello Noesis team,

We have developed a community extension for App/StudioTool in NoesisGUI 4.0 that improves image resource selection in larger XAML projects.

Main features:

• Vertical, alphabetically sorted folder navigation.
• Recursive image listing for the selected folder and all subfolders.
• A-Z filename filtering.
• Thumbnail previews.
• Automatic property update and popup closing after selection.
• Persistent state for the last folder, filter, and selected image.
• Support for Image.Source and ImageBrush.ImageSource in properties such as Background and Foreground.

The native selector remains available. Clicking the Source label or double-clicking the ImageSource label opens the custom picker.

GitHub repository:
https://github.com/obvious3460/noesis-s ... age-picker

Screenshot:


The repository contains only the independently developed extension files and installer. It does not distribute the NoesisGUI SDK or binaries. Users need their own SDK and must rebuild App.StudioTool.

We would appreciate your feedback:

1. Is there a recommended extension API for custom property editors or resource pickers?
2. Could this functionality be useful as an official option or StudioTool sample?
3. Are there any compatibility or licensing changes you would recommend before broader community use?

Thank you!

Update – 31 August 2026

The extension has been updated based on further testing. Both Image.Source and ImageBrush.ImageSource, including properties such as Background and Foreground, now open the custom image picker with a single click on the Source or ImageSource property label.

The dropdown arrow continues to use Noesis Studio's native selector, so both workflows remain available. The GitHub repository has also been updated to match this behavior.

This is such a great idea. Thank you so much for taking the time to build this and, especially, for sharing it with the community. We really appreciate it!

Is there a recommended extension API for custom property editors or resource pickers?

Right now, we still don't have an API specifically for this, but it’s definitely something we should offer in the future.

Could this functionality be useful as an official option or StudioTool sample?

Yes, absolutely! This is a great example of the kind of use case that can inspire improvements for the next version of Studio. Please keep working on it, and thank you for sharing your ideas and feedback with us, it’s genuinely valuable.

Are there any compatibility or licensing changes you would recommend before broader community use?

The Studio license is perfectly compatible with this, so you should be good to go. Thanks for asking and for being thoughtful about this! :)