Sugested feature ... tree browsing.

[simoncn]

(16-04-2015 10:15)audio_elf Wrote:  I'm writing this thinking aloud slightly but here goes.

Currently as far as I'm aware there is no way to have tags in the browse tree appear only within certain other tags... for example "Movement" really has no meaning unless you have already browsed for "Composition".

Is there any possibility you could implement so that (for example) the top level / second level tree would look something like (in my own tree)

Code:

[n] albums; [n] items; [n] playlists
Artist
All Artists
Decade
   |-- Year
Genre
Composer
   |-- Conductor
   |-- Orchestra
Composition
   |-- Movement
Collection
   |-- Collection Album Name
AudioQuality
AudioData

So in my example the tags Year, Conductor, Orchestra, Movement and Collection Album would only appear within the higher selection. I would imagine that on the properties you could have an entry something like

Code:

Composer, {Composer}Conductor, {Composer}Orchestra

(exact syntax doesn't really matter).

Thanks for this suggestion.

A key feature of MinimServer is that you can browse by any tags in any order at any time. This differs from other servers that provide a "browse tree" in which some tag choices need to be made before other tag choices become visible. This is an intentional difference of philosophy and design and I would need to think very carefully before making this change to MinimServer.

Quote:As I say I'm just thinking out loud and its a minor inconvenience. It would also be good if there is flexibility in the ordering of the tags so when (for example) I choose Collection* in the tree then Collection Album Name would be towards the top - so ideally: [n] albums; [n] items; Artists; Collection Album Name; et al. I'm imagining the indexTags would look (for me) something like

Code:

{Composition}Movement, Artist, {Collection}CollectionAlbum:Collection Album Name, All Artists, Composer, {Composer}Conductor, {Composer}Orchestra, Decade, {Decade}Date:Year, Genre, Collection, #AudioQuality, #AudioData

Thanks for reading my ramblings...
Eloise

Note *: Collection is an additional tag I added for certain albums which form a collection - for example all the Society of Sound recordings have a Collection tag and then the CollectionAlbum tag is used as like an alternative sorting order with (in the Society of Sound case) the release number first so Album:"Undercurrents [Society of Sound:82]" becomes CollectionAlbum:"82: Undercurrents"

I don't think revealing a "hidden" tag should change the position of this tag within the list. If you want the prevously hidden tag to appear near the top of the list when it is revealed, you could give it this position in the full indexTags list.

As well as the simple case you have described, there are other related cases that aren't quite so simple, such as:

• revealing a tag only after one of a specified list of tags has been selected: {A or B}C
• revealing a tag only after all of a specified list of tags have been selected: {A and B}C
• some combination of the above: {A or {B and C}}D, {{A or B} and C}D, etc.
  

Supporting these cases would require a more complex syntax that probably wouldn't be appropriate for indexTags.