Questions about tag formatting limitations

[simoncn]

(29-04-2025 14:55)eseb63 Wrote:  Editing the displayName property doesn't solve the problem : you have to remember to edit the displayName property each time you change the profile, which you might forget to do.

As the displayName property is stored in the profile, it would only need to be edited once when the profile is created. After doing this, the displayName for that profile would automatically be shown on the server status web page every time the profile is selected.

[eseb63]

Thanks for the hint.

I had another question : does exist a special reason to use only a small part of the screen area with the property web page ? some properties are not entirely visible when using several settings (tagIndex, tagValue , tagFormat... ) while the space could be used?

[simoncn]

The properties pages are formatted as HTML tables containing HTML input fields. I haven't found a way to make an indivdual table row expand to fit its contents without making all other table rows expand as well.

[eseb63]

maybe i misunderstand something, but what would be a problem to expand all properties page rows or allow the user to resize the table itself ?

[simoncn]

The layout of the server configuration web pages has been designed to provide a good browsing experience with a range of browser window sizes. Expanding all entry fields on the properties pages to the full width of the browser window would also expand text paragraphs on other configuration pages, making these pages visually unattractive and hard to read.

Instead, you can use the Properties option from the taskbar minim icon to display a Properties window that can be resized up to the full width of your display without changing the sizes of any other windows.

In the longer term, I could imagine adding some way to show a pop-up with an editable multiline text field containing the full value of a property when this value is too long to fit into the input field on the properties page.

[eseb63]

I found a workaround for my previous problems with displayFormat (not available for the Work tag) and indexFormat with groups.

Instead of asking minimServer to format the Work tag with rating, i supply a formatted tag Work_Rated, which is Work tag suffixed with rating. Same for Overall_Work.

The work rating propagates from work to group, and from group to movement, if they don't have an explicit rating.

MinimServer settings:
indexTags : Work_Rated, Work_Rating
itemTags : Work_Set, Overall_Work, Overall_Work_Rated, Work, Group_Rating, Movement, Movement_Rating

tagValue : Group.Default={Work}, Overall_Work_Rated.Default={Overall_Work}, Work_Rated.Default={Work}, Work_Rated.merge={Work_Set, Overall_Work_Rated}, Group_Rating.Default={Work_Rating}, Movement_Rating.Default={Group_Rating}

tagFormat : Group.displayFormat={$composer_S^^ : $Overall_Work$Group^$Group_Rating^ [^]$Group_Art-Rating^ (^)}

It works fine, i can browse and see rating at different levels.

but i (again) have an issue if works are grouped.

with the same CD Bach by Angela Hewitt, which contains:
1) Fantasia in C minor (1 track)
2) Two-Part Inventions (15 tracks)
3) Three-Part Inventions (15 tracks)
4) Chromatic Fantasia and Fugue in D minor (2 tracks)

Tagging :
each Fantasia and Invention has a WORK tag
each Invention track has a GROUP tag "Inventions à deux/trois voix"
each Invention track has a WORK_SET tag "Inventions à deux voix (15)"
each Invention track has a WORK_SET tag "Inventions à trois voix (15)"
Fantasia 1 has a WORK_RATING tag ♪♪♪
Fantasia 4 has a WORK_RATING tag ♪♪♪♪
3 two-part Inventions have a different WORK_RATING tag (♪♪♪, ♪♪♪♪, ♪♪♪♪♪)
each rated work has a WORK_RATED tag = Work + Work_Rating

I browse by Work_Rating and select for example a ♪♪♪♪ rating :

if i select the Hewitt album, i see the items as expected

• Chromatic Fantasia
• the Invention à deux voix group, as it contains a ♪♪♪♪ rating track
  

but if i select the Work_Rated index, i see

• Chromatic Fantasia as expected
• Inventions à deux voix (15) workset (though not having a rating)
• the exhaustive list of "inventions à deux voix", without having the group displayed, which is confusing and not conform to the principle you gave that items within a group cannot be accessed directly from outside the group ?
  

[simoncn]

I have implemented the change described in post #10. An update containing this change will be available soon.

I will look at this new issue and post back when I have some information.

[simoncn]

I see the same results as you. When you select the Work_Rated index, MinimServer shows all available values for Work_Rated. It does not show the items or groups containing Work_Rated tags. To see these items or groups, you need to select a Work_Rated value and this produces the expected results (complete groups shown, not individual tracks).

[eseb63]

(25-05-2025 21:47)simoncn Wrote:  When you select the Work_Rated index, MinimServer shows all available values for Work_Rated. It does not show the items or groups containing Work_Rated tags. To see these items or groups, you need to select a Work_Rated value and this produces the expected results (complete groups shown, not individual tracks).

this result is not a problem for me but what i wanted to see.

I think you misunderstood my post : the problem is not with Work_Rated index but with Work_Rating index, the list of work rating values.

eseb63 Wrote:I browse by Work_Rating and select for example a ♪♪♪♪ rating :

if i select the Hewitt album, i see the items as expected

• Chromatic Fantasia
• the Invention à deux voix group, as it contains a ♪♪♪♪ rating track
  

but if i select the Work_Rated index, i see

• Chromatic Fantasia as expected
• Inventions à deux voix (15) workset (though not having a rating)
• the exhaustive list of "inventions à deux voix", without having the group displayed, which is confusing and not conform to the principle you gave that items within a group cannot be accessed directly from outside the group ?
  

[eseb63]

(25-05-2025 21:26)simoncn Wrote:  I have implemented the change described in post #10. An update containing this change will be available soon.

thanks a lot!

will this next update also include these 2 enhancements you planned to do ?

• the small treatment for suffix [xxx] in reverseName ( see https://forum.minimserver.com/showthread.php?tid=7466 post #2)
• indexArtwork : index entry picture as default picture for its values (see https://forum.minimserver.com/showthread...8#pid52178 post #3)