View Issue Details

IDProjectCategoryView StatusLast Update
0004351NoesisGUIStudiopublic2025-08-25 13:53
Reporterdstewart Assigned Tosfernandez  
PrioritynormalSeverityfeature 
Status assignedResolutionopen 
Product VersionStudio_Beta 
Target VersionStudio_Beta 
Summary0004351: Elements Containing Large Amounts of Applicable Styles/Templates Can Be Difficult to Organise, Find, and Apply
Description

This ticket comes from the feedback of a client who has a large amount of Templates for a specific Element type, and who had difficulty finding and applying them from the Context Menu in particular, and who specifically requested a method in which they could be organised into "Filters" or "SubFolders" in the Context Menu.

Attached, can be found a rough sketch serving as a potential conversation starter about how we could resolve this with the concept of Studio-only 'Metadata' "Resource Groups". It is modelled after Steam's 'Collections' feature which was picked because in particular, it excels at allowing a single item to be stored in multiple Collections at once, and makes Creating, Adding To a Collection, and Removing From a Collection very easy.

Attached Files
ResourceCollections.jpg (1,594,024 bytes)
PlatformAny

Activities

sfernandez

sfernandez

2025-08-25 13:35

manager   ~0010999

For me this should be solved by using different ResourceDictionaries, as it is the standard way of organizing resources.

Anything else that can't be expressed in XAML will be hard to translate to the UI of Studio.

dstewart

dstewart

2025-08-25 13:53

developer   ~0011000

I agree that Resource Dictionaries solves this as the Resources Panel level, but it doesn't really assist at the level of Applying a Resource.
Even if you have 100 Button Templates, each nicely organised across many ResourceDictionaries, when you enter the Templates Context Menu to apply them, you will still see a single giant list of 100 Button Templates.
Would a solution to this perhaps to be to use the same Context Menu structure proposed in the image, but instead of them being custom Resource Groups, we organise them by the Dictionary they are a part of? (With the big cost that it will universally add at least one extra step to navigating the Context Menu to apply it)

Issue History

Date Modified Username Field Change
2025-08-25 13:26 dstewart New Issue
2025-08-25 13:26 dstewart File Added: ResourceCollections.jpg
2025-08-25 13:30 dstewart Severity minor => feature
2025-08-25 13:33 sfernandez Assigned To => sfernandez
2025-08-25 13:33 sfernandez Status new => assigned
2025-08-25 13:33 sfernandez Target Version => Studio_Beta
2025-08-25 13:35 sfernandez Note Added: 0010999
2025-08-25 13:53 dstewart Note Added: 0011000