Matt...
The new
Automatic List Style is quite nice. I've been using it a for an hour or so, and I can report it is working without problem. I happened to be working with some images today and was listening to music. And it really got me thinking. I wrote this "step-by-step" so you can see what evolved.
1. Earlier I posted my desire to select "Artist" rather than "Album Artist (Auto)" for thumbnail grouping.
2. Matt and I have been chatting, and he prefers to engineer things carefully to minimize the number of options. Too many options can get messy. There is a balance, and maybe if you feel you need an option, you should look at the problem in a different way.
3. I was using the Automatic List Style and found I wanted Artist / Album grouping. I was going to submit a request to provide "Automatic (Album group if logical)".
4. I noticed that the phrase "(Album group if logical)" is a bit of a misnomer. It doesn't accurately represent the style of the list - which has two levels of grouping, Artist and Album.
5. I saw I had an "Artist / Album" View Scheme and suddenly
connected this to "(Album group if logical)".
6. I considered a new way of doing the grouping, and I checked to make sure it was consistent with what's there now. If I select "Thumbnails (Album group if logical)" and view a Playlist, the entries are never grouped.
Here's the concept. The new List Styles would be:
Automatic
Automatic (View Scheme)
Details
Thumbnails
Thumbnails (View Scheme)
This does so many things for the List Style feature it makes my mouth water. First, it inherently solves the issue of whether grouping should be by "Artist" or "Album Artist (Auto)". And it goes way farther than that.
With either "(View Scheme)" List Style, if I click on the top level of a View Scheme, the contents would group based on all the View Scheme Components. I'll bet 98% of users have an "Artist / Album" View Scheme since it's a program default. You click on the top of it and you get the grouping that is now "(Album group if logical)".
But
if you click on a different View Scheme, you get the thumbnails grouped according to it's way of looking at the library. It's so cool... it brings the component ordering and tree structure into the visual world!
To make it the most useful, if I have a View Scheme expanded and select a child entry at any level, the grouping would be based on all Component entries below that level. And it should definitely have a hotkey.
Ctrl+R for "
Rotate List Style" feels right somehow.
From what I see in the List Styles behavior now, this concept seems like it would fit quite well into the List Style code you've already written. And I can't help thinking that the resulting code would be satisfyingly elegant... do you guys use consultants ever?
I want it... I want it
real bad...
Hey, team. I think it's fair to say this beta test has had its ups and downs for all of us. I really like this idea, and I think it would be of tremendous benefit to everyone. So... I have two bottles of carefully cellared 1989 Ch. La Conseillante set aside. If you do this, I'm going to ship one to you. When you get it, I want you to share it some evening. The other bottle? Then night you guys enjoy yours, hopefully with some good cheese and grapes, my wife Sandy will share this one with me. As I've networked my music for the family, she's been part of this Beta Test, too... if ya know what I mean...
Matt, on a personal note, it was a rewarding challenge to engineer "sans Options". The idea that came from it is excellent and almost transparent to today's operation. I think your design philosphy is a good practice to follow, and I'm going to push myself a little harder when decisions about Options come to my desk in the future.